The server crashed in the middle of a big change and half of it was saved

Some changes, like a castle being built or a shop restocked, touch many records, and a crash in the middle leaves a world that never existed. Here is how to write the intent first so that after a restart it is all or nothing.

Why this works

A big change is only safe if it counts as done or not done, never half. Writing down the plan first and a seal at the end lets you tell, after any crash, which changes were finished and which can be dropped as if they never began.

When not to use it

Overkill for a small single-player game that saves only at calm moments, or where losing the last minute does not matter. A copy of the file written next to the old one and then swapped in is simpler.

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
• 47 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 "The server crashed in the middle of a big change and half of it was saved" (read_entry journal-for-a-server-crash) 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