Hide an item's stats until identified without letting players reroll them

Mystery items are fun because you do not know what you got. But if the stats are decided at the moment of revealing, quitting and reloading becomes a slot machine. This entry settles the stats at the drop and only controls what the player may see.

Why this works

Mystery should live in what the player sees, not in what the game decides. If the result is settled when the item drops, then saving and reloading cannot change it, so only the reveal is a surprise and no one can gamble on it.

When not to use it

Don't hide stats when players must plan a build or compare gear quickly, as in a fast game with many drops. Hiding adds chores there. Show everything at once and keep the mystery for a few special items.

In the full entry

• What to build, step by step
• Starting values and the reason for each
• 4 common mistakes and the fix
• A diagram of every state
• 19 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 "Hide an item's stats until identified without letting players reroll them" (read_entry unidentified-items-keep-their-stats-from-the-drop) 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