Show real odds for a skill check and let failure move the story on

A failed persuasion roll that dead-ends the quest feels terrible, and a displayed 75 percent that is really 60 feels like a lie. Here is the exact chance of a d20 check, how to show it, and how a failure can cost something without stopping the story.

Why this works

A player decides well only if the number on the screen is the number that decides. Keeping the shown chance and the real roll the same, and giving failure a way forward with a cost, keeps risk readable and the story moving.

When not to use it

Wrong for a story where skill is meant to be a hidden judgement, or where a failure really should end things, like a tense heist. There, drop the shown odds, or let the cost of failing be severe but clearly signalled.

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 "Show real odds for a skill check and let failure move the story on" (read_entry skill-check-odds-and-failing-forward) 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