Find out what happened¶
When the wrong line plays, resist the urge to add more conditions immediately. First look at what Story Engine saw.
Read a Rule Trace¶
- Open Window > Game Creator > Story Engine > Rule Trace.
- Set Debug to Record trace silently.
- Enter Play Mode and perform the interaction you want to check.
- Select the Director run in the list. Use Freeze to keep it visible while the game continues.
- Find the chosen Rule, then compare it with the Rule you expected.
The trace shows which conditions passed, which required conditions failed, each Rule's score and priority, and how ties or busy Rules affected the result.
The list keeps the 25 most recent Director runs. Resume follows new evaluations again. Clear removes traces but leaves story history alone.
Start with these questions¶
| What you see | What to check |
|---|---|
| No new Director run | Did the Trigger or instruction sequence run? Is that Trigger still waiting for an earlier sequence? |
| No matching Rule | Check category, active GameObjects, enabled Rules and required conditions |
| A Rule is missing | It may belong to another category, be inactive, or not have been checked because a stronger match already won |
| The expected Rule lost | Compare priority first, then score, then passing mandatory criteria |
| A response keeps repeating | A sole or best match can repeat. Add a history condition if repetition must be prevented |
| Rejected (busy) | The Rule is still running and this request is configured to reject |
| Rejected (loop) | The response chain tried to enter the same Rule again |
| A Rule could not be checked | Read the relevant Console error and inspect its conditions |
Open the explanation from a Rule¶
Use Explain Last Evaluation below the Optional Criteria list. This opens Rule Trace on the most recent recorded evaluation for that Rule.
If it has no explanation yet, make another Director request with trace recording enabled. The editor cannot reconstruct a run that was never recorded.
Look for gaps with Story Insights¶
Open Window > Game Creator > Story Engine > Story Insights.
History answers what has played and how often. Coverage summarizes the recorded trace runs: selected and never-selected matches, ties, frequently failed required conditions and other patterns worth reviewing.
A Rule that has never won is a question to investigate. It might need a missing situation in your test, or it might be overshadowed by a broader Rule.
Test a small set of situations¶
For a greeting, try the first meeting, a return visit and the special case you added. Also try the case where that special condition is false.
For a puzzle response, test the action before it is allowed, when it becomes allowed, after it succeeds, and when the player tries it again. Check the player can still continue.
When testing a first-time moment again, reset its history in Story Insights. When testing a complete new game, use your game's normal reset flow.
Trace colors help you scan, but the labels and condition results carry the explanation. Tracing is an editor tool and is not included in your player build.