Keep old saves working after you rename or remove scenes

You fix a typo in a scene name, or cut a scene, and every save made before the update points at nothing. This entry shows how to carry old saves forward step by step, where to send a player whose scene is gone, and what to refuse.

Why this works

A save is a promise made to a player, and every release can break it. Writing each change as a small, never edited step lets a save from any past version walk forward through the same steps and arrive in the current story.

When not to use it

Wrong before release, or for a story so short that nobody keeps a save across versions. Then just change the names and tell testers to start over; keep this for when real players hold progress.

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
• 25 lines of example code with 4 checks that pass
• How your AI shows you that it works

Say this to your AI

Use the Spielerando entry "Keep old saves working after you rename or remove scenes" (read_entry old-saves-after-a-story-update) 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