Keep each hero's knowledge separate when you switch viewpoint

When the story switches between two or three playable people, one of them can suddenly mention what only the other one saw. Here is how to track who knows what, who learned it together with whom, and flag a line that tells more than that person could know.

Why this works

A reader trusts a viewpoint character only as far as that person could have known. Keeping a separate list of what each hero has learned turns a slip of the pen into a plain mismatch you can find, instead of a feeling someone senses later.

When not to use it

Unneeded when the narrator is meant to know everything, or when you want the player to know more than the hero on purpose. Dramatic irony depends on that gap. Mark those parts as narration, or leave the check out of them.

In the full entry

• What to build, step by step
• Starting values and the reason for each
• 3 common mistakes and the fix
• A diagram of every state
• 28 lines of example code with 3 checks that pass
• How your AI shows you that it works

Say this to your AI

Use the Spielerando entry "Keep each hero's knowledge separate when you switch viewpoint" (read_entry each-hero-only-knows-what-they-saw) in my game. Build it step by step, and show me how you checked that it works.

Or skip this and connect the MCP: your AI then finds all of this by itself.Connect the MCP