import type { ValidationResult } from '../../model/component-types.js'; import type { ScenarioModel } from '../../model/scenario-model.js'; /** * Checks event logic against how Valkyrie actually runs it (QuestData.cs, EventManager.cs): * * - `vartests` and `conditions` fill the same test list; when `vartests` is present, * `conditions` is ignored entirely. A component's tests only decide whether it runs * at all — they never route between event1 and event2. * - A hidden event (display=false) auto-follows its first *enabled* button. A button is * enabled unless it has an `eventNCondition` that fails (with an action other than * `none`). So with an unconditional button 1, event2+ can never be reached. * To branch, list several targets in event1 (`event1=EventA EventB`) with vartests on * each target — Valkyrie runs the first target whose tests pass. * - Spawns are events: they run when listed in eventN. Quest.Add ignores them, so * `add=SpawnX` silently spawns nothing. */ export declare function checkEventSemantics(model: ScenarioModel): ValidationResult[]; //# sourceMappingURL=event-semantics.d.ts.map