Search a drawer or body bit by bit, keeping what was found when interrupted

Searching a cupboard in a scary place should take a moment, reveal things one at a time, and be something the player can abandon when a noise comes. What was found should stay found, and the half-finished look should start again. This entry tracks that progress.

Why this works

Searching is a small decision between greed and fear, and it only works if stopping costs something but not everything. Keeping what was found rewards the risk already taken, while dropping the half-finished look keeps a quick peek from being free.

When not to use it

Skip it in a calm game where searching is just routine, or where players will do it hundreds of times: the waiting turns into a nuisance. Show everything at once there, and keep the slow search for rare, tense places.

In the full entry

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

Say this to your AI

Use the Spielerando entry "Search a drawer or body bit by bit, keeping what was found when interrupted" (read_entry search-a-drawer-item-by-item) 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