Let thieves steal from a monster's pockets without the item dropping again at death

A guard with a ring on his finger should drop that ring when killed, and let a thief lift it first. Two sloppy designs duplicate the ring or remove it from the sprite but not from the loot. This entry keeps what a monster wears, what a thief can take and what it drops in one place.

Why this works

Whatever can be seen, taken and dropped should come from one record of what the creature has. With a single source of truth, the picture, the theft and the loot can never disagree, so no item is cloned or left as a ghost.

When not to use it

Don't add stealing to a game whose fights are quick and constant, where stopping to pick pockets would stall the pace, or where players have no sneaking skills. Give extra loot for a clean kill or a special move instead.

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
• 21 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 thieves steal from a monster's pockets without the item dropping again at death" (read_entry stolen-from-a-monster-or-dropped-by-it-never-both) 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