Protect only the characters a running quest still needs

A stray arrow kills the one person who holds the key to the story, and the game cannot go on. But making everyone unkillable robs the world of danger. Here is a rule that knocks someone out instead, only while a quest needs them, and gets them back on their feet.

Why this works

Safety should last as long as the reason for it. Tying protection to what the open quests still need means a person is spared only while the story depends on them, and danger returns the moment it no longer does.

When not to use it

Skip it in a harsh game where losing a key person is meant to change the story. There let the death happen and write a path onward; protection that cannot be lost takes the weight out of every fight.

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
• 23 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 "Protect only the characters a running quest still needs" (read_entry essential-characters-who-fall-but-do-not-die) 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