Spielerando

Record a run so you can show the AI exactly how the bug happened

"I fell through the floor somewhere in level three" is hard for an AI to fix, because it cannot press the keys. A tiny recording of which buttons were held in each step replays the same run again and again. This entry stores it compactly and refuses broken recordings.

Why this works

A bug is easy to fix once it can be made to happen again. If the game only depends on its starting number and the buttons pressed, those two things are the whole run. Saving them compactly lets anyone replay the exact moment.

When not to use it

Skip it when the game depends on things outside its control, such as live data from the internet, the real clock or a physics engine that rolls its own dice. A recording will not repeat there. Describe the steps in words, or fix the source of the difference first.

In the full entry

  • What to build, step by step
  • Starting values and the reason for each
  • 4 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 "Record a run so you can show the AI exactly how the bug happened" (read_entry action-bug-replay-input-recording) 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