Your Player's Character Just Died. Nobody Planned For What Happens Next.

Your Player's Character Just Died. Nobody Planned For What Happens Next.

A character dies mid-campaign and the table stalls on two fronts: how the new one shows up, and everything the old one was quietly tracking. Here's the two-part fix, decided ahead of time instead of improvised at the table.

The rogue fails a death save for the third time and that's it, she's gone. The table goes quiet, somebody says "oh no," and then everyone looks at you. Not because they're sad — well, also because they're sad — but because now there's a logistics problem sitting in the middle of the table and nobody planned for it.

Here's what actually happens next, unplanned: the session grinds to a halt while you improvise how a new character shows up. Does she stumble in from the road, conveniently nearby? Does the party find a hireling in the next town who's suspiciously well-armed for a farmhand? Everyone's staring at you while you make this up in real time, and whatever you land on rarely feels earned.

That's problem one, and it's the one everybody talks about. Problem two is quieter and it's the one that actually costs you story: the dead character was tracking things. She owed the blacksmith a favor. The Ashguild trusted her and nobody else. She was the one who promised the orphaned kid in chapter two that she'd come back. All of that either gets awkwardly reassigned to whoever's left, or — more often — it just evaporates, because nobody wrote it down anywhere except in her player's head, and her player just rolled up a new character.

The fix for problem one is embarrassingly simple and belongs in session zero, not in the moment: agree on a re-entry method before anyone needs it. Pick one of the standard three — new character enters from the wings (already in town, already has a reason to be there), the party recruits someone in-world at the next natural stop, or you timeskip a scene forward and narrate the join. Doesn't matter which. What matters is that the table already agreed on it, so when it happens you're executing a plan instead of inventing one under pressure while five people watch.

The fix for problem two takes about ninety seconds and it's the part people actually skip: before you resolve the death narratively, write a two-line thread-transfer note. Line one — what did this character owe, and to whom. Line two — who inherits it, or who explicitly lets it drop, and why. The blacksmith favor goes to the new character, or the blacksmith just quietly stops expecting anyone to collect on it. The Ashguild's trust doesn't transfer automatically — maybe that's the point, maybe the new character has to earn it from scratch, and that's a better story than pretending nothing changed. Either way it's a decision, not a gap.

This is exactly the kind of thing that's easy to lose track of because it happens once, at a moment when you're also managing everyone's feelings about a character dying. If you're already keeping faction and NPC notes in GameMasterCraft, the thread-transfer note is just one more entry tied to the NPCs and factions that character was connected to — which means six sessions later, when someone asks "wait, did anyone ever pay back that blacksmith," the answer's sitting right there instead of living in a dead character's player's memory.

None of this makes character death less sad, and it shouldn't — that's not the goal. The goal is that when it happens, the table loses a character, not a night of momentum and three sessions of buried plot threads along with her.

Comments (0)

More from the Blog

Ready to create something?

Subscribe to an individual app or get the full GameMaster Studio.