How to Retcon a Mistake in Your Campaign (Without Losing Your Players)

Every GM eventually hears it: “Wait, didn’t we kill her?” A player has caught a contradiction, the table has gone quiet, and everyone is looking at you. The good news is that a continuity mistake in a campaign is far more fixable than one in a novel, because your story is still being told. You have four options, and picking the right one depends on how big the mistake is and how much the table has already built on top of it.

First, decide how big it is

Not every contradiction deserves a fix. Ask two questions:

• Does anyone care? A shopkeeper’s beard changing color is trivia. An NPC the party mourned coming back without explanation is a betrayal of the table’s choices.
• Has play built on it? If the players already made decisions based on the wrong version, the fix has to respect those decisions, not erase them.

Small and ignorable: let it go, or fix it with a word. Big and load-bearing: pick one of the options below.

Option 1: Own it and fix it

The simplest and often the best. “You’re right, she died in the boat. My mistake. Let’s say it’s her niece at the dock instead.” Then keep playing.

This works because players don’t want a perfect GM. They want a GM who respects what happened at the table. Owning a mistake in five seconds respects it. Arguing about it for five minutes doesn’t.

Use it when: the mistake is clearly yours, and the fix is a small substitution. Most mistakes fall here.

Option 2: Make it diegetic

Turn the contradiction into something true in the world. The dead ferrywoman greeting the party becomes her ghost, or a shapeshifter wearing her face, or a twin sister nobody mentioned. Suddenly your mistake is a hook.

This is the most fun option and the most dangerous one. Done well, it creates one of those moments players talk about for years. Done too often, players learn that every inconsistency is secretly a plot point, and they stop trusting anything.

Use it when: the contradiction is interesting, you can see where the new thread leads, and you haven’t used this trick recently. Make sure the explanation actually pays off later, or it’s just a dodge with extra steps.

Option 3: Retcon between sessions

Some fixes are too big for the table. Pause, say “let me think about that,” and handle it before the next session. Then open with a short, honest note: “Quick retcon from last week. The bridge was already burned, so the patrol came by boat. Nothing you did changes.”

The key phrase is the last one. A good retcon changes the setup, never the players’ choices or their consequences. If the party spent a session planning around the wrong version, give them the benefit of that plan wherever you can.

Use it when: the mistake touches several NPCs or sessions, and a rushed fix at the table would make things worse.

Option 4: Leave it, and let the players decide

Occasionally the best move is to ask. “I contradicted myself. Which version do you want to be true?” Players often pick the more interesting version, and you get to see what they care about. This works especially well in collaborative, story-focused games, and less well in tables that prefer a firm, GM-owned world.

Use it when: both versions are workable and the table is the kind that enjoys shaping the story.

What not to do

• Don’t deny it. If the players are right and you insist they’re wrong, you’ve traded a small mistake for a trust problem.
• Don’t punish the catch. The player who noticed is your most attentive player. Thank them.
• Don’t over-explain. A long lecture on why it technically makes sense draws more attention to the mistake than the mistake did.

Write the fix down

Whatever you choose, record it. A retcon you forget about is the seed of the next contradiction. If the dock scene now belongs to Wren’s niece, she needs an entry, and Wren’s entry still needs to say she died in session 2. Otherwise you’ll make the same mistake twice, and the second time the players will notice faster.

Stopping the next one

Retcons are a recovery tool. The better plan is catching contradictions before the table does. Most of them fall into five predictable types, and almost all of them come from notes that describe the world as you planned it instead of as it is after play. The fix is a habit: update your notes from what happened after each session, and check tonight’s prep against them before you play. (Here’s the full routine.)

That’s the habit StoryGuard automates. After a session, it reads your notes and proposes what changed, and before the next one, it flags prep that contradicts what you’ve established, like an NPC who died in session 2 standing on the dock in session 3. It even suggests a fix, though “or was it her ghost?” is still your call to make.