Saves from an older version crash my story game after an update

You add a feature, publish, and the players who were halfway through your story get a blank screen. Here is how your AI should treat old save files so every earlier version still loads, and what it must do with a save that comes from a newer game than the one installed.

Why this works

You cannot know every shape an old save once had, but you do know the single change between neighbouring versions. Small upgrade steps, run in order, turn any old file into the current one, and each step stays easy to check and never needs rewriting.

When not to use it

Skip it for a short game that nobody saves across updates, such as a jam game played in one sitting. The chain is extra work there. Simply tell players that old saves will not carry over, and clear them.

In the full entry

• What to build, step by step
• Starting values and the reason for each
• 4 common mistakes and the fix
• 39 lines of example code with 5 checks that pass
• How your AI shows you that it works

Say this to your AI

Use the Spielerando entry "Saves from an older version crash my story game after an update" (read_entry old-save-files-break-after-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