A 2x boost that ran out while the player was away is paid for the wrong time

Boosts have a start and an end, and the player's absence has a start and an end, and they rarely line up. Here is how to count only the overlap, and what to do when two boosts run at once.

Why this works

A boost is a promise about a stretch of time, and only the part that overlaps the time away matters for the payout. Clipping each boost to the absence first, then paying every slice at its own factor, keeps the label on the boost true.

When not to use it

Skip it if boosts only run while the player is watching, such as a short bonus that stops when the app closes. Then there is nothing to overlap; apply the factor in play and leave the away payout alone.

In the full entry

• What to build, step by step
• Starting values and the reason for each
• 3 common mistakes and the fix
• 20 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 "A 2x boost that ran out while the player was away is paid for the wrong time" (read_entry idle-boost-overlap-with-away-time) 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