Chests that open one after another start the next one late if the player was away

A row of timed chests where only one can open at a time seems simple, until the player returns after a night. Do the others start when the first finished, or when the player came back? Here is the timeline that answers it, with the exact moments.

Why this works

A waiting line should run on its own, because the player's absence is not a pause. Storing only when the first one began and deriving the rest means there is nothing to fall out of step, and the player sees that the game kept its word.

When not to use it

Skip it if the wait itself is the monetised hook and chests are meant to start only when the player taps. Then automatic chaining gives away the point of the wait; start each chest on an explicit tap.

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
• 24 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 "Chests that open one after another start the next one late if the player was away" (read_entry idle-chest-queue-chains-offline) 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