Ryuu/AetherOnline
Watch
1
0
Fork
You've already forked AetherOnline
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
Page: content dependency graph and scenario playtests
Pages
Authoring Debugging Home Operations Protocol Reference Runtime Systems abilities loadouts and progression ability rotation and combo planner active realtime session actor directory admin actions and internal auth animation workbench operator guide aoi snapshot replication app mode bootstrap and lifecycle architecture guardrails and module tree tests asset loading routing and vfs authored ui surface renderer authoring command bus and transaction history authoring reference registry contributor extension contract authoring reference registry authoritative audit event schema and projections authoritative world time calendar and environmental scheduler bake product registry build strategy and loadout optimizer campaign journey and progression simulator catalog source map and record routing character gameplay state json store character paperdoll assets character stats and equipment modifiers chat presence and social client local offline save and bootstrap cache client local user preferences and account sync client multiplayer connection flow and session cleanup client realtime authority store and frame projection client scene presentation and player preview client snapshot staging and repair receipts client ui focus and text input planning combat action resolution and mob ai semantics combat presentation cues and transient effects combat rewards and progression persistence content dependency graph and scenario playtests content migration and catalog refactors control agent api and remote service runner control panel config and secret persistence control panel service build invalidation and log normalization control panel service lifecycle and quality gates control plane allocation and zone transfer routing control plane and service ops control plane route policy and coordination api control service supervisor manifest and stale process recovery crafting recipes and service integration dependency aware content health deterministic combat balance lab developer workspace doctor and readiness report diagnostics provider input lanes and failure isolation dialogue quest localization handoff dialogue runtime state and choice authority duplicate realtime claim takeover durable retry and session cleanup durable work queue consumer contract dynamic world state and scene phasing editor authored content workspace manifest and cache editor event console and asset debug dashboards editor extension and contribution registries editor scene snapshot lane demand editor settings registry and workspace presets editor viewport and world tools editor workbench and dock encounter difficulty mutators and reward scaling encounter instance and wave director encounter lobby ready check and entry encounter mechanics and boss timelines encounter memory persistence encounter reward eligibility lockouts and pity enemy archetypes combat kits and encounters engine report log and recovery routing environment configuration reference external engine patterns and boundaries farming footstep surface audio materials forgejo wiki publishing and docs check game data catalog game data generated item family adapters game database schema readiness game server catalog load health and fallback policy game server reconciliation and transfer marker cleanup game server startup readiness and registration game transport endpoints and quic exposure gameplay action authority and command audit gameplay action replay ledger and idempotency gameplay authority replay fixtures and drift gates gameplay conditions effects and events gameplay system slice scaffold gameplay ui runtime and bevy sync generated artifact drift and repair generated artifact registry and quality gate integration glossary hotbar hud runtime projection and input in process zone transfer phase journal input profiles and keybinds interactive world map minimap and cartography internal auth and admin delegation chain inventory items and stack limit safety item authoring lifecycle and reference repairs json catalog hot reload batch and candidate revalidation legacy compatibility and migration register local player input control and reconciliation local playtest and standalone preview localization extraction and runtime catalog login account admin repository and cascades login database migrations and schema contracts login server auth sessions and character entry login session cache throttle and revocation loot table authoring and drop audits mob animation presentation events and projectile cues mob encounters and scene combat movement authority networking tick health and zone pressure npc ai schedules and deterministic behavior npc definition catalog npc schedules routines and contextual behavior npc services npc state memory and interactions pack export content gate party composition roles and synergy simulator passive traits and procs persistent interactive world objects placed light runtime budget and preview heatmap player appearance equipment persistence player economy authority player homesteads housing and property auctions player journal and codex player navigation tracking and world guidance player notification inbox authority and delivery player preview animation profile player preview debug gizmos and collision overlays player preview render cache and keyed entity lifecycle player preview weather masks and effect budget player snapshot assembly and durable row normalization post process volume blending and preview overlays project files import profiles and asset change impact public endpoint detection and upnp exposure quality gate jsonl events and panel failure summaries quest runtime projection and turn in authority quic reliable stream topology and negotiation realtime admission throttling and load shedding realtime bootstrap manifest and snapshot service realtime bootstrap wire sections and compression realtime client reconnect journal and command replay realtime datagram codecs and ingress policy realtime egress mailboxes and lane scheduling realtime ingress validation and failure policy realtime packet debug capture and triage realtime protocol registry realtime registry and wire contract realtime resume ledger record format realtime rollout policy and compatibility negotiation realtime runtime profile and transport adaptation realtime session activation hydration boundary realtime timebases tick ordering and clock ownership redis keyspace ttls and cleanup targets regions points of interest and exploration discovery relationship reputation gates and service deltas remote avatar replica binding and interpolation render surface guard and window safety runtime actor identity and authority contract runtime camera arrival and cutscene overrides runtime debug overlays and developer options runtime environment registry and startup config validation runtime path roots and packaged asset resolution runtime profiling tracy captures and budget gates runtime scene manifests and zone authoring runtime ui fonts and localized text presentation scenario sandbox and timeline inspector scene audio runtime routing scene command center and visual graph tools scene cutscene authoring scene documents scene layer schema depth and bands scene lighting post process and placed lights scene navigation and collision scene preview scenario replay cli scene runtime media weather and camera phases scene runtime schedule and frame budget scene trigger authority and reconciliation scene triggers scene validation and repairs service json rpc contracts service observability and metrics contract service registry heartbeats drain and shutdown session handoff and transfer shared content workspace shared test fixtures and fixture workspaces shared validation report schema source inventory and engine health standalone account realm and character flow standalone asset pack and preflight standalone loading pause death and recovery screens standalone shell flow and ui lifecycle standalone ui preview root and transient lifecycle starter character economy bootstrap status effects and combat modifiers story content loop text asset migration journals and atomic rollback tiled prefab import and placement tilemap asset import contracts tileset atlas preview surfaces trigger permissions targeting and action pipelines typed disconnect codes and transport advisories ui layout binding graph and editor workflow ui layout ui skins validation and bake validation errors validation provider registry and strict preflight vendor stock and shop economy authoring viewport spatial planning overlays vscode dev tasks and generated launch profiles workspace package roles and scoped quality profiles world entry smoke harness and soak telemetry world events and scenario director world gameplay assemblies world interactions and activity boards world mechanism and puzzle graphs world overlay gizmos and culling world travel waypoints and zone transitions xtask content gates and plans
3 content dependency graph and scenario playtests
forgejo-actions edited this page 2026-07-14 17:23:30 +00:00
Table of contents

Content Dependency Graph And Scenario Playtests

What This System Is

The semantic content dependency graph lets a designer validate a quest, world event, dialogue sequence, or named encounter as one reachable chain. It complements the asset dependency graph: the asset graph answers which files invalidate each other, while this graph answers which authored gameplay IDs and runtime facts cause the next piece of content to run.

The viewport Simulation surface exposes a Validate Scenario Chain action. Enter a quest, world-event, dialogue-sequence, or encounter ID as the content-chain root and run the action. Leaving the field empty selects the first authored world event, falling back to the first quest. The result banner and Event Console report reachable node and edge counts plus the first actionable failures.

Indexed Content

The graph indexes all loaded scenes and the current quest, dialogue, NPC, mob, enemy-content, and world-event catalogs. Nodes include:

  • quests, quest steps, follow-ups, offer/turn-in NPCs, and map-marker scenes;
  • dialogue sequences, dialogue lines, choices, branches, and state effects;
  • world events, phases, transitions, markers, dialogue actions, and encounter actions;
  • encounters, waves, enemy archetypes, mobs, and tagged scene spawners;
  • causal runtime facts such as quest flags, events, unlocks, party tags, scene variables, and inventory items.

Producer-to-consumer edges connect otherwise separate catalogs. For example, a quest reward that adds a world-event start flag connects that quest to the event; a final encounter wave produces its completion event, which connects back to the waiting event phase.

Runner Semantics

The runner resolves the root ID, traverses the reachable graph deterministically, and evaluates every reachable node. It does not mutate editor or gameplay state and does not need a running server.

Hard missing references are errors, including missing follow-up quests, dialogue targets, NPCs, scenes, encounters, archetypes, mobs, or per-wave spawners. A required runtime fact with no producer is a warning because it may be an intentional external scenario seed. Warnings do not fail the chain; errors do.

Encounter wave validation requires one scene spawner tagged with:

  • encounter:<encounter id>
  • wave:<zero-based wave index>

The report is intentionally bounded in the result banner. The full in-memory report retains every visited step and issue. Dependency-Aware Content Health consumes that report to select scenario, combat, and journey fixtures and export a unified CI report.

How Authors Use It

  1. Open the viewport Simulation controls.
  2. Enter the root content ID, such as world_event.slime_infestation.
  3. Select Validate Scenario Chain.
  4. Fix any reported missing edge and run the same action again.

The runner refreshes the authored-content workspace before building the graph, so it validates the complete saved workspace rather than only the currently open scene.

Rules And Invariants

  • Node IDs and lookups are normalized case-insensitively.
  • Graph output and traversal order are deterministic.
  • The runner never writes gameplay state or content assets.
  • Only issues reachable from the chosen root affect its report.
  • External seed facts remain warnings; missing concrete content IDs are errors.
  • Scene encounter bindings are validated for every authored wave.

Validation And Debugging

Run the same root after every fix until the reachable graph has no errors. Missing concrete IDs are authoring errors; missing producers for external seed facts are warnings that should be either documented in the fixture seed or connected through authored content.

Examples

Validating world_event.slime_infestation should reach the event phases, warning dialogue, road defense encounter, core encounter, spawner tags, and completion facts. A missing wave:1 spawner tag should be fixed in the scene, not suppressed in the graph.

Related Systems