Make sure a betrayal has been set up before it happens

When the trusted ally turns on the hero out of nowhere, the player feels cheated instead of shocked. Here is a way to count the signs that came before, spread over different scenes, and to fail any betrayal that stands on too few.

Why this works

A twist lands as fair when the player can look back and find the clues, and as cheap when they cannot. Several clues spread over different moments, plus a reason for the act, are what turn a surprise into a shock that makes sense in hindsight.

When not to use it

Skip it when the betrayal is meant to be seen coming from the start, as in a tragedy where the player knows and dreads it, or when the traitor is shown to the player openly. Plan that suspense differently, with dread rather than hidden clues.

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
• 21 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 "Make sure a betrayal has been set up before it happens" (read_entry betrayal-needs-earlier-suspicion) 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