A bug only happened in one long play session and I cannot repeat it

A tester died to something odd after two hours and sent you a recording with thousands of actions. Nobody can read that. This entry gives your AI a method to cut the recording down until only the few actions that matter are left.

Why this works

Most actions in a long session have nothing to do with the bug. Removing blocks of them and checking whether the bug still happens finds the small core far faster than reading or trying one by one.

When not to use it

It does not work when the bug depends on the exact running time or on random numbers that were not recorded. Record those too, or you shrink toward a different bug.

In the full entry

• What to build, step by step
• Starting values and the reason for each
• 2 common mistakes and the fix
• 23 lines of example code with 3 checks that pass
• How your AI shows you that it works

Say this to your AI

Use the Spielerando entry "A bug only happened in one long play session and I cannot repeat it" (read_entry survival-shrink-bug-recording-to-minimum) 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