Async D&D: How a Campaign Survives Five Adult Calendars

Async D&D: How a Campaign Survives Five Adult Calendars

Here is the thing nobody says out loud when a campaign dies.

It is almost never the story. It is almost never that people got bored, or that the DM ran out of ideas, or that somebody's Bard was insufferable. It is that Priya has a work trip, Dan has a newborn, Marcus moved two time zones east, and the four hours that everyone had free in 2019 no longer exist anywhere on the calendar. The love is intact. The Thursday is gone.

Async play is the fix for the Thursday, not the love.

What is async D&D?

Async D&D means the campaign advances one message at a time instead of one evening at a time. Nobody books four hours. Each player takes their turn whenever they get a minute, the Dungeon Master replies, and the story moves. A table can run this way for weeks, and it is still a campaign, not a chat.

Why the scheduled session stopped working

A weekly session is a promise five people make to a calendar, and it fails whenever any one of them cannot keep it. That is not a character flaw, that is arithmetic. The more adults in the group, the more reliably the intersection of everyone's free evenings shrinks to nothing.

So groups do what groups do. They reschedule once. They reschedule twice. They move to fortnightly, which feels like a solution for about a month and then breaks in the same way, except now you have also forgotten what everyone was doing. Someone eventually says "let's pick it back up in the new year" and the campaign quietly enters the long sleep it never wakes from.

Async does not ask anyone for an evening. It asks for two minutes, at some point today, from wherever they are. That is a promise adults can actually keep.

What does a message a day actually buy you?

More than you would guess, because a table is several people and the beats add up.

Say five of you take one action each on a normal weekday. That is five exchanges with the Dungeon Master, plus its narration in between, and five exchanges is a scene. A tavern argument, an interrogation, a search of a burnt-out shrine. A week of that is a chapter. A month of that is the sort of arc a scheduled group would take a whole season to reach, and you never once had to find a Thursday.

There is a second, sneakier advantage. Async players write better turns. When you have thirty seconds of table time and four people waiting, you say "I attack the goblin". When you are typing on a bus with nobody tapping their foot, you say what your character actually does, and you get a better scene back for it. Nobody has ever had a good roleplay idea while five people watched them think.

Does the game wait for us properly?

Yes. Nothing advances without a player. There is no timer running the story on without you, and no version of your party that keeps adventuring while everyone is at work.

When it becomes your turn, the game tells you which of three things it wants: your action, a roll you owe, or your initiative. Your phone buzzes. If the tab is in the background you get a notification. Your hero's card at the table is outlined, and the outline moves the instant the turn does. You do not have to poll the group chat asking whether it is you yet.

Outside combat there is no fixed rotation, which turns out to matter a lot for async groups. The Dungeon Master stays with whoever is mid-exchange, turns to whoever the scene now addresses, and otherwise hands the moment to whoever has spoken least. That last rule is the one that quietly protects the person who only gets ten minutes a day. Nobody can hold the spotlight for more than three consecutive beats, so the fast typers cannot run away with the campaign while the rest of you are in meetings. The full explanation of turn order goes through all of it.

How does combat work if we are not in the room together?

Better than you would expect, because combat is the one part of D&D that was always turn-based anyway.

A fight starts, everyone rolls their own initiative, and nothing advances for anyone until every player who is present has rolled. Then the order stands and each person acts when it reaches them. A fight can absolutely take three days of real time to resolve, and it reads fine afterwards, because the transcript does not record the gaps. What you get is a battle where everyone had time to actually read their character sheet and notice they had a reaction available, which is not the worst thing that has ever happened to a combat round.

If you want to play a fight live, play it live. Nothing stops a table from getting on a call and burning through a dungeon in one sitting, then going back to a message a day for the aftermath. Most tables end up doing both.

What happens when someone goes quiet?

They will. Someone is always mid-house-move.

There are four escapes, and none of them needs the host to be awake:

• A reminder. After a few hours, the game tells the player the table is waiting on them, and names what it needs.
• Anyone can pass them by. After a day, any member of the table can skip an idle player. Not just the host. That is deliberate, because sometimes the person who vanishes is the host, and a table should not be hostage to one person's inbox.
• Mark yourself away. Going somewhere with no signal? Flag it. Your hero stays in the story and the Dungeon Master runs them, they cannot be killed while you are gone, and their saves and initiative are rolled for them.
• Or just skip. Passing your turn outside combat is free and spends nothing at all.

A campaign that can route around one missing person is a campaign that survives August.

Does playing this slowly cost more?

No, and if anything it costs less.

A turn is one message you send to the Dungeon Master, plus the opening scene when the campaign starts and the catch-up after time away in a Living World. Free gives you 20 turns a day, Adventurer 100, Legend 400, all reset at midnight UTC. Dice results, listening to the narration, party chat and skipped turns cost nothing.

Take one action a day and you are using one turn out of twenty. Async play is comfortably inside the free plan for as long as you want it to be, which is the opposite of how "play at your own pace" usually works in software.

Each player spends their own allowance, so nobody is subsidising anybody, and hosting is free on every plan. The one number to keep an eye on is campaign slots: a solo campaign, a Living World, a table you host and a seat at a friend's table each take one. Free has 1, Adventurer 5, Legend 20. There is no separate hosting cap. The pricing page lays it out.

What is async genuinely bad at?

We are not going to pretend it is strictly better than a table night, because it is not.

You lose the room. You lose four people talking over each other, the collective groan at a natural 1, the joke that only works because of the timing. Async play is a novel your group writes together; a live session is a night out. They are different pleasures and if you can get the night out, take the night out. We have written our honest position on where a real table still beats an AI DM.

Async is also worse at momentum. A scene that would take twenty minutes live can take two days, and a group that goes quiet for a fortnight has to spend a beat remembering where it was. The campaign will still be sitting there exactly as you left it, with the full transcript to scroll back through, but you will need to reread a bit.

And async is slower at big set pieces. A siege that eats a whole evening in person is genuinely more fun in one sitting.

What about Living Worlds?

Different flavour of the same medicine, and worth knowing about if your group's problem is scheduling rather than company.

A Living World is your own campaign set in a shared version of an authored adventure, with a clock that runs at real-time speed. A three-day journey takes three real days. An eight-hour rest takes eight real hours. That sounds like an obstacle and is actually a scheduling feature: you set off, you close the tab, you get on with your life, and the journey finishes while you are living it.

What it is not is a table. In a Living World you play your own story and meet other players only through what they left behind. If you want your friends in your actual party, you want a table.

Setting up a table that survives the year

A short and slightly bossy list.

1. Agree the pace out loud, once. "A turn a day when you can, no guilt if you miss one." Put it in the table expectations when you set it up. Half of all async friction is people not knowing whether they are late.
2. Turn notifications on. All of you. The single biggest cause of a stalled async game is one person who did not know it was their turn.
3. Use party chat for the arguing. The Dungeon Master cannot read it, so it is a genuinely private room for planning, and it costs no turns.
4. Do not wait for the missing person. Pass them by after a day. It is not rude, it is the feature.
5. Write more than five words when you have the time. You will get more back.

Then start. Someone in the group chat has to open a table and paste the link, and the campaign that has been dead since the spring gets to be alive again by Tuesday, without anybody having to book anything.

The Thursday is not coming back. The campaign can.