Stop a collection chest from handing out items the player already owns

A chest with twenty cosmetics keeps giving the same hat, and the player feels cheated. Cutting out owned items sounds easy, but the odds change and the end of the collection needs a plan. This entry handles both without making the player feel the seams.

Why this works

Players judge fairness by what they see, and a repeat feels like a wasted opening. Choosing only from what is still missing makes every chest count, but the collection also ends sooner, so the last step needs its own reward instead of a silent repeat.

When not to use it

Skip it when copies are part of the fun, for example when players trade them, merge them to upgrade, or when the chest advertises fixed odds. Keep the full pool there and give each copy a real use.

In the full entry

• What to build, step by step
• Starting values and the reason for each
• 4 common mistakes and the fix
• 32 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 "Stop a collection chest from handing out items the player already owns" (read_entry no-duplicates-until-collection-complete) 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