Here’s how a campaign dies. Nobody storms off. Nobody hates the story. It’s the second week of November, somebody’s got a work party, so you skip a week. The next week two people are traveling. The week after that is Thanksgiving itself, obviously out. By the time you look up it’s December 19th, you haven’t rolled dice in five weeks, and the group chat has gone from “when are we back?” to a muted channel with a Wordle score in it.

If you searched “how to keep a D&D campaign alive through the holidays,” you already feel this coming. Good. Feeling it coming in October is the whole advantage, because every move that saves a campaign from the holidays has to be made before the holidays start. Here’s the playbook I run, and the one mistake that kills more campaigns than any villain I’ve ever written.

The mistake: limping

The worst thing you can do from mid-November to early January is try to keep the weekly slot alive on hope. You know the pattern. Every Tuesday a scheduling poll goes out. Every Wednesday it comes back three yes, two maybe, one silence. You cancel “just this week” six weeks in a row, and each cancellation teaches everyone’s calendar the same lesson: this slot is negotiable now. Other things move into it. By January the slot doesn’t belong to the game anymore, and restarting means fighting for territory you used to own.

I call this limping, and it feels responsible while you’re doing it. You’re “staying flexible.” You’re “seeing who can make it.” What you’re actually doing is converting a scheduled campaign into an unscheduled one, one apologetic cancellation at a time. A campaign that goes formally dark for six weeks and comes back on a booked date is in far better shape than one that technically never stopped but also never happened.

So don’t limp. Declare.

Declare the dark season out loud

Sometime in the next few weeks, at the top of a session, say a version of this:

“We’re playing through December 9th. Then we’re dark for the holidays. We’re back January 6th, same time. It’s already in the calendar. Between now and the 9th, I want to land this arc somewhere satisfying.”

That’s it. That one speech does four things at once. It protects the remaining November sessions, because they’re now the last ones before the break and people show up for finales. It kills the weekly poll-and-cancel death spiral before it starts. It gives you, the DM, a real target to pace toward instead of a story idling in neutral. And it books the restart while everyone is still warm, which matters more than anything else on this page.

If you ran a session zero, this is the scheduling contract from that conversation getting exercised, and it should surprise nobody. If you didn’t, the holidays are a fine excuse to have the scheduling talk you skipped. Our session zero guide covers why most campaign deaths are calendar deaths, and the holidays are that thesis wearing a Santa hat.

One rule inside the rule: book the January date before the December session ends. At the table, out loud, phones out, invites sent. A restart date agreed in person in December survives. A restart date left to “we’ll figure it out in the group chat” gets figured out in February, if ever.

Play whoever shows up

Between your declared last session and the dark date, attendance will still wobble. People travel early. Somebody’s in-laws arrive on a Wednesday for reasons known only to them. You have two options for those wobbly weeks, and both beat cancelling.

Run the main story at quorum. Pick a number, I use three, and announce that the campaign runs if that many players can make it. The absent character fades into the background, no explanation needed, exactly like weather. I wrote about this design-for-absence rule in the time zones post, and holiday season is where it earns its keep. The one adjustment: don’t spend big personal arcs while their player is away. Advance the shared plot, bank the personal beats.

Or go self-contained. If the table’s down to two or three and the main plot would feel thin, run a one-shot or a side story instead. The party’s hirelings botch a job. The characters’ younger selves, ten years ago, in the tavern where it all started. A completely unrelated crew of pregens robbing a winter carnival. Side stories have a magic property in December: they produce a great night with zero continuity cost, so nobody who missed it has homework. If you ran a Halloween one-shot in October, you already know the format, and the same pregen folder works all winter.

What you’re protecting with both moves is the habit, the ritual of these people showing up for each other, which is the actual load-bearing structure of a campaign. The plot can idle for a month. The habit can’t.

Land the last session on a comma

Pace your remaining sessions so the final one before the break ends on a resolved beat with one live question. Close the dungeon, win the fight, get paid. Then, in the last five minutes, open exactly one door: a letter arrives with a seal nobody recognizes, the patron asks for a meeting in the new year, the artifact hums once and goes quiet.

Resolved-plus-one-question is the comma that makes January easy. End on a full cliffhanger and six weeks will sand the urgency off it, and worse, nobody will remember the tactical situation they were allegedly desperate to resume. End on a full stop and January has no hook at all. One warm thread is enough to pull a table back through.

Make the break survivable for future you

Now the part everybody skips, because in December it feels optional. In January, the first twenty minutes of your restart will be six people reconstructing the campaign from memory, and memory had a margarita in it at some point. Who had the amulet? What did we promise the duchess? Was the innkeeper the spy, or was that the theory we ruled out?

So before you go dark, spend ten minutes writing the “story so far”: a two-paragraph save file of where things stand, what’s owed, and the one open question you planted. Post it in the campaign channel the week you return. The restart post goes deep on why a January table needs re-onboarding, not a recap, and every move in it works better when a written record of the break-point exists.

This is also, honestly, where I point at the thing I build. Loracle sits in your Discord, records the session, and writes the recap, so the record of your December finale is already sitting there in January, exactly as it happened, no margarita in it. A six-week break is precisely the gap it was built to carry a table across. If you keep your record by hand instead, genuinely fine, just keep one. The campaigns that die over the holidays are almost always the ones that went dark with no save file and came back to a blank screen.

The whole playbook, on one index card

  • Declare the dark season in November. Last session, dark dates, return date, said out loud.
  • Book the January session before the December one ends. Invites sent at the table.
  • Until the break: quorum of three, or self-contained side stories. Never the weekly poll-and-cancel.
  • Land the finale on a resolved beat plus one open question.
  • Write the two-paragraph story-so-far before you go dark. Post it the week you return.

Campaigns survive the holidays on purpose. The DMs whose games are rolling again by mid-January are the ones who scheduled the break with the same seriousness they schedule the sessions. Make the speech. Book the date. Go enjoy the carnival; your table will still be there in January, because you left it somewhere worth coming back to.