See exactly which game numbers an AI changed, and flag the risky ones

Ask for a small fix and the AI may also nudge a damage value, halve an animal's health or add a new boss with huge numbers, all inside a long reply you do not read line by line. This entry gives the AI a before-and-after report that stands out the big swings.

Why this works

Balance lives in small numbers, and a small number changed by half is a large change in play. Comparing before and after by path, and judging size relative to the old value, brings the swings to the surface that a long reply would bury.

When not to use it

A report shows what moved, not whether it is right. A big change may be exactly what you asked for, and a small one may break the game. Treat it as a pointer for where to look, then play and measure.

In the full entry

• What to build, step by step
• Starting values and the reason for each
• 3 common mistakes and the fix
• 38 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 "See exactly which game numbers an AI changed, and flag the risky ones" (read_entry what-did-the-ai-change-in-my-numbers) 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