Pay collection-book rewards once, even when you add new items to the book later

A book of everything the player has crafted gives rewards at quarter, half and full. Then an update adds new items: either everyone loses rewards they already got, or they collect them again, or a milestone that was just crossed is skipped. This entry keeps the claims straight when the book changes size.

Why this works

A reward is a promise already kept, so what was claimed must stay claimed whatever the book later becomes. Remembering only what was found and what was claimed, and working out the rest on demand, means a growing book can neither pay twice nor take anything back.

When not to use it

It does not suit a book that never grows or whose rewards depend on order, such as a story that unlocks chapter by chapter. There, a plain fixed list of numbered rewards is simpler and just as fair.

In the full entry

• What to build, step by step
• Starting values and the reason for each
• 3 common mistakes and the fix
• 35 lines of example code with 5 checks that pass
• How your AI shows you that it works

Say this to your AI

Use the Spielerando entry "Pay collection-book rewards once, even when you add new items to the book later" (read_entry casual-collection-book-milestones) 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