Show exactly what changed between two saves so a bug report is useful
When a player says a chest emptied itself or a door opened too early, the AI needs to see what really changed, not two huge files. This entry shows how to produce a short list of differences, and which noisy fields to leave out so the real cause is visible.
Why this works
A bug is a change nobody meant, so the useful question is what differs, not what the files contain. Comparing the meaning of the data, and leaving out fields that always change, shrinks thousands of lines to the few that point at the cause.
When not to use it
Skip it when the bug sits in what the screen shows, not in the saved data, or when it only happens in the middle of play and never reaches a save. Then record a short screen video or the steps taken, and check the display.
In the full entry
- What to build, step by step
- Starting values and the reason for each
- 3 common mistakes and the fix
- 18 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 "Show exactly what changed between two saves so a bug report is useful" (read_entry save-diff-for-bug-reports) 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