The game worked this morning and my AI made ten changes since then

When something breaks after a long session, guessing which change caused it wastes hours. This helper tells your AI how to narrow it down with only a few test runs, and what to do when the bug does not show up every time.

Why this works

Each change is either before or after the break, so halving the list finds the culprit in a handful of runs instead of ten. Checking both ends first proves the question even makes sense.

When not to use it

Do not use it when the changes depend on each other so that earlier ones cannot be undone alone, or when the bug needs hours of play to appear. Then read the changes instead.

In the full entry

• What to build, step by step
• Starting values and the reason for each
• 2 common mistakes and the fix
• 28 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 "The game worked this morning and my AI made ten changes since then" (read_entry work-act-find-which-ai-change-broke-it) 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