Coming back after a long time away pays too much, or ignores a boost that ended

A player returns after a long trip and finds either an absurd pile of coins or a bonus that quietly counted for the whole time. Both come from treating the time away as one block. This entry splits it, so the cap and the bonus each apply only where they should.

Why this works

The cap decides how much time counts at all, and the bonus applies only to the early part of that counted time. Doing it in this order makes the answer the same however long the player was gone.

When not to use it

Skip a cap if your game promises full progress for any absence; then keep the bonus split but remove the limit.

In the full entry

• What to build, step by step
• Starting values and the reason for each
• 3 common mistakes and the fix
• A diagram of every state
• 17 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 "Coming back after a long time away pays too much, or ignores a boost that ended" (read_entry offline-earnings-ignore-cap-and-boost-end) 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