AI roleplaying guides
Why an AI Game Master Forgets a Clue
Understand why an AI narrator can contradict a discovered clue, how players can repair a scene, and how saved state and character knowledge support continuity.
The clue was found, so why did it vanish?
At a desert watchtower, you recover an ink-stained map fragment. A cartographer identifies its markings as the east pass. Two scenes later, a caravan scout claims no route east exists, and the narration treats the fragment as blank. The inconsistency can pull you out of an engaging mystery. It may look like the AI game master simply forgot, but several different failures can create the same visible result.
This desert-caravan sequence is an illustrative example, not a recorded Playworlds session. An AI narrator can make mistakes. A continuing game must decide which details became accepted facts and which were suggestions, guesses, or dialogue. Clarifying that boundary helps players correct a scene and designers prevent the error from recurring.
Separate saved state, supplied context, and character knowledge
Saved state records what happened: the map was found, the cartographer spoke, a roll succeeded or failed, and the party reached camp. Supplied context is the selection sent to the narrator for this turn. Character knowledge is narrower: the cartographer recognizes the marking, while the scout may know only the current road conditions. A saved fact can be omitted from context or shown to the wrong character.
These are different design questions. An increasingly long conversation transcript does not by itself say which statements are true. A witness might lie; a player might speculate; an earlier AI response might have been corrected. The game needs a way to mark accepted events, retrieve the relevant ones, and keep each character's view of them separate. Asking the model to “remember everything” does not define those rules.
Follow the map fragment through a complete turn
Suppose the player tells the scout, “The cartographer identified the east pass on this fragment. I found it at the watchtower.” A useful current-turn brief would say that the map exists, where it was found, what the cartographer said, and whether the scout has heard that claim. It would also include the player's exact attempt and any resolved check. The scout can doubt the marking without erasing the discovery itself.
The narrator could answer: “The scout studies the faded ink. ‘That mark points east,’ she says. ‘The pass may be buried now.’” This invented reply preserves the clue and leaves a choice. By contrast, “You have no map” contradicts the saved item, while “She knows the rival caravan's secret tunnel” gives her information the scene has not earned. Continuity depends on both the recorded facts and the limits of each speaker.
What a player can do when a scene contradicts itself
Pause at the first material contradiction. State one correction in plain language: “Continuity note: I found the map fragment at the watchtower, and the cartographer identified the east pass. Please continue with that established fact; the scout can still be skeptical.” Then return to the decision you were making. A narrow correction is easier to apply than requesting a complete rewrite of the campaign.
For a disputed rule, item, or roll, check the sheet and visible outcome. If a detail may have been proposed rather than accepted, ask directly. Playworlds links saved adventures to your account across devices, but generated narration may still make mistakes. For a persistent issue, send support the page, expected result, and steps; remove private story details and access links from screenshots.
A proposed design for more reliable continuity
A game team can record each accepted event with an actor, place, time or sequence, and source. It can store the actual roll result separately from the sentence that describes it. Before the next response, it can select the few events that matter to the current action, plus unresolved promises and the visible inventory. The narrator then describes an outcome that the game can check against that record before saving any new facts.
For the scout scene, check that the map, cartographer's statement, and current road conditions reach the narrator; that the scout reveals only what she knows; and that the caravan's route changes only after a permitted action. These are proposed checks, not Playworlds benchmark results or a claim about every live scene.
Do not confuse disagreement with forgetting
A credible character can be mistaken, evasive, or hostile. The scout's denial might be part of the plot if the game makes clear that it is her claim, not the narrator's correction of world history. Look for attribution: who says the east pass is gone, and what evidence do they have? That question often turns an apparent error into a playable disagreement.
A continuity failure changes a settled fact without an in-world cause or player choice. Clues are the player's basis for planning; rewriting evidence makes investigation arbitrary. Preserve established facts while letting characters interpret them differently.
A quick continuity checklist
For players: identify the precise fact that changed, check the current sheet or scene, give one short correction, and resume with a specific action. For game teams: record accepted events, distinguish narrator facts from character claims, retrieve relevant evidence for each turn, limit NPC knowledge, and test whether new narration respects the stored result. The checklist is useful even when the model writes beautiful prose; style cannot repair a missing clue.
Bring that approach into your next adventure by starting with a clear first goal and tracking one or two important facts as the story develops. The Playworlds world library offers settings to explore, while the guide to writing roleplaying actions shows how to ask a focused question when a scene is unclear. The player should always have enough consistent information to make the next choice.