Notice a damaged or half-written save before it replaces a good one

A crash, a closed tab or a full disk can leave a save cut off in the middle, and the game then loads a hero with missing items. This entry shows how to tell a whole save from a broken one, and a trap that makes good saves look broken.

Why this works

A broken save is not wrong in a way you can see; it simply looks like a hero with missing things. A short fingerprint of the content, compared on loading, turns invisible damage into a clear answer. Taking it from the content, not the written text, keeps harmless reformatting from looking like damage.

When not to use it

Skip it when someone could gain by cheating: a fingerprint anyone can recompute guards against accidents, not against tampering. For ranked play or paid items, keep the real record on your own server and let the phone's copy be only a convenience.

In the full entry

• What to build, step by step
• Starting values and the reason for each
• 3 common mistakes and the fix
• 34 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 "Notice a damaged or half-written save before it replaces a good one" (read_entry save-checksum-detect-damage) 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