A phone call or crash while saving ruined the whole save file

If the app is killed at the exact moment it writes, the player may come back to an empty or broken save and lose everything. A simple habit of how the game writes and reads its save makes this survivable. Here is the small piece of logic to hand to your AI.

Why this works

A write that is cut off leaves something half done, and you cannot know when that will happen. So you never touch the only good copy: you always write beside it and treat a copy as real only when its check number matches.

When not to use it

Skip it for tiny, unimportant data such as a sound setting, where losing it costs nothing, and for games that save to a server which already keeps its own safe copies. Two slots is extra work only worth it when progress took the player real time.

In the full entry

• What to build, step by step
• Starting values and the reason for each
• 3 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 "A phone call or crash while saving ruined the whole save file" (read_entry save-file-half-written-two-slots-and-checksum) 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