Let the player search a container item by item, even if interrupted

Searching is tense when the contents appear one at a time, and annoying when stepping away makes you start over or when closing and reopening gives a different chest. The progress and the contents each have to live in the right place, and the speed bonus must not lose time.

Why this works

Tension comes from not knowing, and fairness from not being able to redo it. Deciding the contents once and revealing them bit by bit lets danger interrupt the search without a reroll, and pausing instead of restarting respects what the player has already paid.

When not to use it

Skip it in a fast action game where every second of waiting at a chest breaks the flow, or where loot is meant to be a quick reward. Open the container at once and show everything instead.

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
• 36 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 "Let the player search a container item by item, even if interrupted" (read_entry search-a-container-slot-by-slot) 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