Spielerando

I told my AI that a scene is broken and it guessed wrong three times

A short complaint gives the AI nothing to hold on to, so it changes things at random. This entry checks a bug description for the parts that matter and tells you which question to answer before you ask again, including a note when the scene name does not exist.

Why this works

An AI can only fix what it can see. Where to start, what you expected, what happened and where it happened remove the guessing, and a report that names the real place in your files beats one that uses the title on screen.

When not to use it

A full report is wasted when the problem is a crash with a message: paste that message and a few lines before it instead. And do not bother when you can fix it yourself in a minute.

In the full entry

  • What to build, step by step
  • Starting values and the reason for each
  • 3 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 "I told my AI that a scene is broken and it guessed wrong three times" (read_entry bug-report-the-ai-can-act-on) 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