I published the game with test settings still switched on

Cheat keys, test ad codes, a development server address: things that help while building are embarrassing or costly once players have them. Here is a last check before publishing that walks through the whole settings file and refuses to continue if anything of that kind is left.

Why this works

People forget what they cannot see, and a late tired hour is when test settings slip through. A check that runs automatically right before publishing does not rely on memory: it looks at the same kinds of traces every time and stops the release when it finds one.

When not to use it

Skip it for a game you only play with friends on a private link, where test settings do no harm. Also remember it only finds the traces you named: a new kind of leftover slips past, so add a rule whenever one gets through.

In the full entry

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

Say this to your AI

Use the Spielerando entry "I published the game with test settings still switched on" (read_entry debug-settings-left-on-in-the-published-game) 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