A new run keeps a secret the player has not met again, and the story breaks

Games where the second run remembers things from the first are great, until one remembered fact depends on another that was wiped. This entry checks a keep-list against the dependencies between facts and repairs it in the direction you choose.

Why this works

A fact often makes sense only because of other facts. Carrying one into a new run without the things it rests on creates a world no road could have built, so what you keep must be closed under what it depends on.

When not to use it

If you want strange starts on purpose, such as a game that begins with a ghost who knows too much, a half-kept memory is the point. In that case keep the list as it is and write the story to explain the gap.

In the full entry

• What to build, step by step
• Starting values and the reason for each
• 4 common mistakes and the fix
• 37 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 "A new run keeps a secret the player has not met again, and the story breaks" (read_entry new-game-plus-keeps-half-a-story) 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