Work out what a colony produced while the player was away

Multiplying income by the hours away is wrong when the smithy runs out of coal after twenty minutes or the storehouse fills up. This entry finds out which limit stopped the work first, so the welcome-back screen shows what really happened and why it ended.

Why this works

Time away is not income. A producer works only while it has material, room and time, so the true result is whichever of the three ends first. Telling the player which one it was turns a surprising number into an understandable story and shows what to improve.

When not to use it

Skip it when the world should stand still while the player is gone, or when what happens away from the screen would be unfair, such as a game where enemies attack in real time. Pause the clock instead of simulating.

In the full entry

• What to build, step by step
• Starting values and the reason for each
• 3 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 "Work out what a colony produced while the player was away" (read_entry offline-progress-input-runs-out) 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