Check your list of buildings and costs for typos before they break the game

When the AI edits your numbers, a misspelled resource or an upgrade that points at a building that does not exist turns into a game that quietly gives away things for free or crashes at the third level. Here is a check to run after every change of the list.

Why this works

The game trusts the list of costs and never questions it, so one misspelled word becomes a silent bug far from its cause. Checking the whole list after every edit catches the mistake at the spot where it was made, while it is still cheap to fix.

When not to use it

It only shows that the list agrees with itself, not that the game is fun or fair; a perfect table can still make a dull game. For that, play it or run the numbers over a whole game. Not worth it for a short list you read yourself.

In the full entry

• What to build, step by step
• Starting values and the reason for each
• 3 common mistakes and the fix
• 41 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 "Check your list of buildings and costs for typos before they break the game" (read_entry balance-table-validator) 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