Spielerando

I said only touch the dialogue, and the AI changed my saving code as well

A request to stay in one corner of the project is only a wish until something checks it. This entry gives your AI a check of the changed files against a list of allowed and forbidden places, with a rule that the forbidden list always wins.

Why this works

A request in words is a wish; a rule that is checked is a fence. Listing what may change and what must never change, and letting the forbidden list win, catches the quiet slip into the saving code before it reaches your players.

When not to use it

It gets in the way when the job really spans several parts, such as renaming something used everywhere. A tight fence then blocks honest work. Widen the allowed places on purpose for that one job, and review the changes closely.

In the full entry

  • What to build, step by step
  • Starting values and the reason for each
  • 4 common mistakes and the fix
  • 30 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 said only touch the dialogue, and the AI changed my saving code as well" (read_entry keep-the-ai-inside-the-files-you-allowed) 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