The monster finds the hiding player although it never saw them go in

Hide-and-seek against a monster feels unfair when it walks straight to your locker, or when it ignores you although it watched you climb in. This entry decides fairly, based on what the monster could actually see at the moment you hid.

Why this works

Hiding is fair only if what the monster knew when you slipped in is what counts. Judging it once, at the moment of entry, and then letting that memory fade is something a player can understand and plan around.

When not to use it

Wrong for games where the monster is meant to feel all-knowing, or where hiding is only a short pause between chases. There, a simple always-found or never-found rule is clearer than a hidden check the player cannot read.

In the full entry

• What to build, step by step
• Starting values and the reason for each
• 2 common mistakes and the fix
• A diagram of every state
• 35 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 "The monster finds the hiding player although it never saw them go in" (read_entry hiding-spot-seen-entering-check) 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