Overview
Narrative state tracking fails when it's invisible. The game knows what the player has done, but the player doesn't know what the game knows. The player expects the game to remember that they saved the village, but the game only tracks a binary "village_quest_completed" flag — it doesn't track how the player completed it (saved by negotiation vs. saved by combat), so the village militia that should arrive at the siege doesn't arrive because the flag doesn't specify the method. The tracking is too coarse to produce the expected reactivity.
The Narrative State Tracking prompt builds state management systems with three properties: (1) granular tracking — every narrative-relevant action is recorded with sufficient detail to produce correct reactivity (not just "quest completed" but "quest completed via negotiation, NPC A survived, NPC B died, village militia available"), (2) state query interface — every game system (dialogue, quests, encounters, economy) can query the narrative state and receive a complete answer about any tracked variable, and (3) state change propagation — when a narrative variable changes, all systems that depend on that variable are notified and can update their behavior, preventing stale state (where a system still behaves as if the state hasn't changed).
What you get: - Narrative variable catalog with granularity specification - State query interface design - State change propagation system with dependency tracking - State persistence specification (save/load compatibility) - State consistency validation (detecting contradictory states) - State debugging tools (inspecting and modifying narrative state during development)
Built for: technical narrative designers, gameplay programmers, and systems architects who need the game to remember what happened — not just that something happened.