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

Scene Triggers

What This System Is

Scene triggers are authored volumes that turn tile visits and interactions into gameplay outputs: music changes, unlocks, runtime events, NPC dialogue, scene transitions, encounter spawns, and authority requests. The scene document owns the authored trigger records; the client runtime decides which authored triggers are eligible; the game server owns the final decision for server-authoritative actions.

The trigger runtime starts with a SceneTriggerTileVisitRequested input, resolves matching authored triggers and NPC interactions, arbitrates overlap, checks trigger state memory, then either commits locally, predicts locally while requesting authority, or waits for authority before applying the result.

How Authors Use It

Triggers are authored under the scene trigger records: TRIGGER_LAYER, TRIGGER_CONDITION_PRESET, and TRIGGER. A TRIGGER record carries these author-facing groups:

  • Identity and ownership: id, name, group_id, state_profile_id, archetype_id, trigger_class, permission_policy, and transition_pair_id.
  • Spatial shape: x, y, width, height, and shape. Shapes support rectangle, polygon, line, and facing cone contracts.
  • Activation and memory: enabled, activation, once, once_scope, and cooldown_ms. Activation modes are enter, exit, stay, and interact.
  • Authority and arbitration: authority, priority, overlap_group, blocks_lower_priority, and overlap_policy.
  • Actor filters: actor_ownership, actor tags, context tags, and other condition inputs.
  • Behavior: conditions, sequence_next_trigger_ids, action_target, action_pipeline, and action.

Start from built-in archetypes when possible. door is an authority-only interaction transition. ambience_zone is a stay trigger for music. unlock_gate applies an unlock once. checkpoint emits an event. npc_dialogue starts NPC dialogue. cutscene_gate emits a one-shot cutscene-style event. scripted_event is the generic authored event trigger.

Conditions And Actions

Trigger conditions include actor tags, context tags, scene tags, weather, time ranges, dwell time, facing-interact ticks, presence counts, synchronized interaction, consumed-trigger checks, quest flags, inventory counts, party tags, faction reputation, scene variables, presets, and all/any/not groups.

Use shared-kernel conditions when the same rule must work in editor preview, offline runtime, and server authority: quest_flag, inventory, party_tag, faction_rep, and scene_var. Scene-runtime-only conditions such as dwell time, weather, synchronized interaction, and presets are useful for local authoring behavior but need extra care when paired with authority-only actions.

Trigger actions are tokenized by family:

  • music:<cue> for preview/runtime music behavior.
  • unlock:<unlock_id> for shared gameplay unlock state.
  • transition:<scene_path>-><entry_point> for server-authoritative scene transitions.
  • dialogue_npc:<npc_id>|<topic_id> for server-authoritative NPC dialogue starts.
  • event:<event_id> for shared gameplay events.
  • spawn_encounter:<spawner_id>*<count> for server-authoritative encounter spawns.

Action pipelines can add delay, guard, and target steps before the final action. Keep pipelines small and readable; if a behavior needs many branches, prefer explicit triggers with named condition presets.

Rules And Invariants

Trigger ids, state profile ids, group ids, and referenced runtime event ids must stay stable once other content or save data refers to them.

once and cooldown_ms are remembered through a scope key. Pick once_scope intentionally: per-actor, party, account, session, and scene-reset scopes produce different replay behavior. Use state_profile_id when a set of triggers should share consumed/cooldown memory.

Overlap arbitration only makes sense inside an overlap_group. priority_stack can allow multiple triggers to fire, but blocks_lower_priority stops lower-priority members. first, highest_priority, nearest_center, interaction_target, and exclusive_group each encode a different authoring promise; do not mix unrelated trigger purposes in the same group.

Permission policy and actor ownership are both meaningful. trigger_class provides defaults such as doors being player-only and admin triggers being admin-only, while permission_policy and actor_ownership make an individual trigger stricter or broader.

For authority-only actions, the client request is not trusted as source of truth. The server projects a trigger authority catalog from the runtime scene manifest, verifies the source zone and spatial request, rejects disabled or unknown triggers, rejects non-interaction use of interaction-only triggers, and replaces mismatched requested actions with the canonical authored action before resolving.

Validation And Debugging

Use scene validation after changing trigger fields, condition tokens, action tokens, transition targets, dialogue targets, or runtime event ids. Use trigger preview to inspect local eligibility, overlap, cooldown, once state, authority mode, pending requests, and selected action.

If preview works but online play does not, compare these layers:

  • Authoring: the scene TRIGGER record and any condition preset it references.
  • Runtime projection: the trigger entry in the baked/runtime scene manifest.
  • Client delivery: whether the local runtime predicted, waited for authority, or held a pending request.
  • Server authority: rejection reasons such as unknown_trigger, trigger_disabled, trigger_requires_interaction, trigger_spatial_mismatch, unavailable source zone, or pending session transfer.
  • Reconciliation: accepted authority resolutions are replayed on the client and can report stale or mismatched local predictions.

Transitions, NPC dialogue, and encounter spawns need online/server testing. Music, unlocks, and shared events can be meaningfully previewed locally, but still need an authority pass when they sit inside an authority-only trigger.

Examples

A door trigger usually uses the door archetype, activation=interact, authority=authority_only, permission_policy=player_only, a small rectangle around the doorway, and a transition:<scene_path>-><entry_point> action. Verify it in preview for interaction targeting and overlap, then verify it online so the server accepts the trigger and applies the canonical transition.

An NPC dialogue trigger usually uses npc_dialogue, activation=interact, overlap_policy=interaction_target, a high priority, and dialogue_npc:<npc_id>|<topic_id>. The NPC id and topic must resolve through the dialogue/NPC authoring loop, not just the trigger token.

Related Systems