1 scene trigger authority and reconciliation
forgejo-actions edited this page 2026-07-11 12:38:13 +00:00

Scene Trigger Authority And Reconciliation

Scene trigger authority reconciles local trigger visits with server-owned trigger decisions. Authoring defines the trigger, but runtime authority decides whether a predicted activation is canonical for the current actor, sequence, and server state.

Purpose

Use this page when a trigger fires in preview but is rejected online, when a client needs compensation after a stale trigger intent, or when adding a new authoritative trigger action.

Client Visit Pipeline

The client detects overlap, eligibility, actor matching, local conditions, and pending trigger visits. It can predict feedback for responsive play, but the prediction must stay tied to a sequence or request id so reconciliation can accept or compensate it later.

Authority Request Lifecycle

Authoritative trigger requests are sent to the game server with actor, trigger, sequence, and authored action context. The server validates the request against its runtime trigger catalog, current player state, and allowed action family before returning acceptance or rejection.

Canonical Authored Actions

Runtime trigger authority should consume baked trigger action projections. Do not hand-code server actions that cannot be traced back to authored trigger records and validation reports.

Rejection And Compensation

Rejections can come from stale sequence ids, missing trigger ids, out-of-range actors, unmet conditions, unavailable transitions, anti-cheat checks, or server state that changed after prediction. The client should undo predicted state only through the reconciliation path.

Diagnostics And Metrics

Use trigger diagnostics, authority decision metrics, event console entries, and server logs. A mismatch report should identify the trigger id, actor id, sequence, predicted action, canonical action, and rejection reason.