Find the bug that duplicates or loses items by replaying what happened

When a player says their stack of gold doubled after a chest was closed in a certain way, guessing at the code wastes hours. This entry gives the AI a replay of a simple event log that shows the first moment items came from nowhere or went nowhere.

Why this works

Items are neither made nor lost by magic, so every change can be written as a move from one place to another. Replaying such a log against the starting contents turns a vague tale of doubled gold into one numbered line where the books stop adding up.

When not to use it

It only sees changes that were written down. If the bug lies in a path that forgets to write a line, the log looks clean, so the reliable fix is to route every change through one place. Also, it is overkill for a game with a few simple items.

In the full entry

• What to build, step by step
• Starting values and the reason for each
• 3 common mistakes and the fix
• 38 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 "Find the bug that duplicates or loses items by replaying what happened" (read_entry items-appearing-from-nowhere-in-the-log) 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