Ryuu/AetherOnline
Watch
1
0
Fork
You've already forked AetherOnline
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
Page: gameplay conditions effects and events
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
1 gameplay conditions effects and events
forgejo-actions edited this page 2026-07-06 16:45:10 +00:00
Table of contents

Gameplay Conditions, Effects, And Events

What This Reference Covers

Gameplay conditions, effects, and runtime event ids are the shared vocabulary used by quests, dialogue, NPC state, NPC services, scene triggers, preview tools, bake validation, and server authority. The shared semantic kernel lives in crates/world-domain/src/gameplay_semantics.rs; the app adapter in src/gameplay_semantics.rs maps authored surfaces onto that kernel; src/runtime_events.rs turns authored string event ids into typed runtime contracts.

Use this page when a content change needs multiple systems to agree on the same gate, reward, unlock, or event id.

Shared Condition Grammar

Shared authored condition tokens use compact strings:

  • quest_flag:<flag_id>
  • inventory:<item_id>>=<count>, inventory_item:<item_id>>=<count>, or inventory_count:<item_id>>=<count>
  • party_tag:<tag>
  • faction_rep:<faction_id>>=<value> or faction_reputation:<faction_id>>=<value>
  • scene_var:<key>=<value> or scene_variable:<key>=<value>
  • unlock_seen:<unlock_id> or unlock:<unlock_id>
  • runtime_event_seen:<event_id>, runtime_event:<event_id>, or event_seen:<event_id>
  • all(...), any(...), and not(...) for grouping; grouped children may be separated by commas or semicolons.

These map to the shared condition kinds: quest flag, inventory count, party tag, faction reputation, scene variable, unlock seen, runtime event seen, all, any, and not.

Some authoring surfaces also accept runtime-local condition tokens. Scene triggers support the broadest set, including time, weather, dwell, actor/context/scene tags, synchronized interaction, and presets. Dialogue branches, NPC state variants, quest objectives, and NPC service gates should prefer shared conditions when preview and authoritative behavior must match.

Effect Families

Shared gameplay effects mutate the same state model that shared conditions read. Canonical effect families are:

  • Set scene variable.
  • Add or remove quest flag.
  • Add or remove party tag.
  • Apply inventory delta.
  • Apply faction reputation delta.
  • Mark unlock seen.
  • Mark runtime event seen.

Dialogue choices, quest rewards, NPC services, and trigger actions adapt their authored reward/effect payloads into these shared operations when possible. Legacy trigger reward tokens such as grant_item: and consume_item: lower into inventory deltas; currency-style legacy tokens are decoded for authoring compatibility but are not the core shared condition-state contract.

Effect application is deterministic: inventory counts saturate at zero and zero entries are removed; faction reputation deltas use saturating arithmetic and remove zero entries. Author content should not depend on negative inventory counts or transient zero-valued records.

Runtime Event IDs

Runtime event ids are string-authored but typed at validation time. Reserved typed prefixes must parse as their owning contract:

  • Dialogue and subtitles: dialogue:, subtitle:, dialogue_ref:, subtitle_ref:, queued/sequence/branch dialogue reference prefixes, dialogue_npc:, dialogue.stop, subtitle.stop, dialogue_state_profile:, and dialogue_state_reset:.
  • NPC service: npc_service:<npc_id>|<service_id>.
  • Scene trigger and quest hooks: trigger:<trigger_id> and quest_hook:<quest_id>|<hook_id>|<phase>.
  • Sound: sound.<playback>.<category>.<cue>.
  • Cutscene: cutscene:<cutscene_id>|....
  • Scripted namespaces: event., quest., combat., system., or a raw id for legacy/scripted integrations.

Malformed ids using reserved typed prefixes are errors, not scripted fallbacks. Empty ids are errors. Placeholder ids such as event.placeholder and cutscene.start are blocked before export/playtest. Unregistered scripted events warn unless they intentionally use the development escape hatch dev.* or dev:.

Validation Ownership

The shared kernel owns the meaning of shared condition and effect families. The app adapter owns which authored surfaces are allowed to use which tokens, and whether a token is represented by the shared kernel or by a scene-runtime fallback. Runtime event validation owns event-id syntax, typed target parsing, dialogue/NPC-service/cutscene resolution when catalogs are supplied, and placeholder blocking.

Scene trigger action validation prepares trigger actions into runtime command contracts before validating event ids. Scene document validation supplies the available dialogue, NPC service, cutscene, and scripted runtime event catalogs so diagnostics can point at missing targets rather than only malformed strings.

Preview Vs Authoritative Behavior

Preview can evaluate shared conditions and apply shared effect projections from local condition state. That makes it reliable for quest flags, inventory counts, party tags, faction reputation, scene variables, unlocks, and runtime-event-seen gates.

Authority-only commands still need authoritative runtime testing. Transitions, NPC dialogue starts, service application, encounter spawns, and durable server-owned rewards may be preview-visible, but the server decides final acceptance and persistence. When preview and online behavior disagree, first check whether the authored gate/effect is shared-kernel or runtime-local, then check whether the command family is preview, shared, or authority-owned.

Examples

Use all(quest_flag:quests.guide.completed; inventory:items.mill_token>=1) when a gate should require both a quest completion flag and an item count. Use event_seen:quest.guide_shortcut.complete when content should wait for a known runtime event to be recorded.

For an NPC dialogue trigger, prefer a typed event/action such as dialogue_npc:guide|interact over a raw scripted event. Validation can then prove that the dialogue route and NPC topic exist.

Related Systems