Finish crafting jobs while the player was away, but not forever

A forge that works for ten minutes needs to know what is finished when the player comes back. Counting with a running timer fails when the game is closed, the clock jumps or the player waited a week. This entry works from timestamps and limits the reward.

Why this works

Time keeps passing while the game is closed, so the only reliable thing to keep is when the work began. Everything else follows from the clock, and a cap on the reward stops a long absence from emptying the whole queue.

When not to use it

Do not trust the device clock when jobs are worth real money or compete with other players. Anyone can wind it forward. Check the time on a server you control, or let the work run only while the game is open.

In the full entry

• What to build, step by step
• Starting values and the reason for each
• 4 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 "Finish crafting jobs while the player was away, but not forever" (read_entry crafting-timer-with-offline-progress) 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