After the AI edits your item list, see what it removed, renamed or changed

Ask for one new sword and the AI may rewrite the whole list, dropping a few items on the way without saying so. This entry shows how to compare the list before and after, tell a rename from a deletion, and raise an alarm when too much is gone.

Why this works

An AI asked for a small change often rewrites the whole thing, and losses hide in what it was not asked to touch. Keeping a copy from before and comparing afterwards turns a silent loss into a short list, and telling a rename from a deletion shows which fix is needed.

When not to use it

It is the wrong tool when the list is meant to change a lot at once, such as a planned big rework, because every line will be flagged. There, review the change in small steps, or keep the list under version history and read that.

In the full entry

• What to build, step by step
• Starting values and the reason for each
• 3 common mistakes and the fix
• 30 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 "After the AI edits your item list, see what it removed, renamed or changed" (read_entry check-what-the-ai-deleted) 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