Validation
The Validator tab in the Tools panel flags structural and expression problems the moment you type. It is the always-on companion to the simulator (drive one path by hand) and the path tester (many random walks). For deliberate scenario-based testing of individual expressions, see tests.
- Errors header: items that will keep the runtime from working.
- Warnings header: items worth fixing but not blockers.
- Anchor and message. Click the row to jump to the field.
The panel autoloads when you open it. No Run button, no wait. The results reflect the current project state.
Fresh vs. stale findings
Some findings refresh on every keystroke (the same inline validation that draws the red underline under an expression field). Others run on a debounced pass after each structural edit and again whenever the panel opens. When you’ve edited the project since the last debounced pass, the debounced rows dim to signal they may be stale until the next pass fires.
Jumping from a finding to the offender
Click a row to navigate to the exact field. Node-scoped findings open the Node Graph with the node selected. Scene-scoped findings open the Data View with the scene selected. Entity findings (unused variables, unused audio cues) open the relevant Data View table.
When to reach for which
Open the Validator when the red underlines pile up and you want the list. Open the simulator with Debug on when you want to click through a single playthrough and watch every event fire. Open the path tester when you want coverage numbers or a list of structural problems across many random walks. Open tests when you want to prove one expression behaves a specific way under specific inputs.
See also
- simulator: drive one path by hand.
- path tester: many random walks against the runtime.
- tests: scenario-based unit tests on individual expressions.
- expressions: the four types, boolean coercion, and the test-harness functions callout.