The game worked yesterday and I made ten changes since, which one broke it

Undoing changes one by one takes ten rounds. There is a way to find the guilty one in about four, and a trap where the answer is wrong because the problem comes and goes. Your AI gets both the search and the safety check.

Why this works

If it worked at one point and fails at another, the cause sits somewhere between. Testing the middle throws away half the suspects each time, so the number of tests grows very slowly with the number of changes.

When not to use it

Do not use it when the problem comes and goes, or when several separate changes only break things together. Make the problem repeatable first, or undo changes in groups and look at each group alone.

In the full entry

• What to build, step by step
• Starting values and the reason for each
• 3 common mistakes and the fix
• 22 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 yesterday and I made ten changes since, which one broke it" (read_entry bisect-which-change-broke-the-story) 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