Show the player where this turn's gold came from and went to

A player sees the treasury rise by thirty and wants to know why. This entry gathers every gain and loss of the turn by its cause, lists the biggest first, folds the small ones into a single line, and warns when the books do not add up, which means a mistake in the game.

Why this works

People trust a number once they can see what made it. Grouping every change by its cause and listing the big ones first tells the story at a glance, and a check against the real total exposes any gold the game lost track of.

When not to use it

Skip it in a quick action game where numbers change many times a second and nobody reads a report, or when you want to keep the cause of income a mystery. Show a simple plus or minus popup at the moment it happens instead.

In the full entry

• What to build, step by step
• Starting values and the reason for each
• 4 common mistakes and the fix
• 31 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 "Show the player where this turn's gold came from and went to" (read_entry turn-report-sources-and-sinks) 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