Play-by-Post D&D (2026): How Asynchronous Campaigns Actually Work

Play-by-post is a roleplaying campaign played in writing, in turns, with nobody required to be anywhere at a particular time. The game master posts a scene. You write what your character does, whenever you next get ten minutes. Everyone else does the same. The game master resolves it and posts the next scene.

It is D&D with the calendar removed, and it is the oldest solution to the oldest problem in the hobby: the night nobody could make it.

It also has a failure mode of its own, and it is the thing this page is really about. Play-by-post removes the schedule, and then discovers that the schedule was the only thing making people take their turn. Almost every campaign in this format dies the same way — not in an argument, not in a total-party kill, but in a thread where one person has not posted in nine days and nobody wants to be the one to say so.

Everything else — where you play, which system, how combat works — is downstream of how you answer that.

How a Round Actually Works

A round of play-by-post has three beats, and they repeat forever.

The game master posts a scene that ends on a decision. Not a description that ends in a full stop — a situation that ends in a question. The single most common cause of a stalled thread is a post nobody knows how to answer.

Each player writes one post. What your character says, does, and tries. Conventionally you write your character’s intent and actions, not their outcomes: you swing, you do not hit. The outcome belongs to the game master and the dice.

The game master resolves everything into the next scene. All the player posts land at once in the fiction, even though they arrived across two days in real life.

Two conventions make this readable. Separate in-character from out-of-character — a second channel, a spoiler block, or a simple OOC: prefix — so that rules questions and scheduling chat do not break the story thread. And keep posts shorter than you want to. New play-by-post writers routinely produce 800-word posts, which is lovely for them and slow for everyone waiting. A tight paragraph or two per round sustains a campaign; an essay per round quietly ends one.

Dice are rolled by a bot in Discord, a roller built into the platform, or the game master on everyone’s behalf. Any of the three works. What matters is that it is decided before session one, along with the thing in the next section.

The Quiet Player Is the Whole Design Problem

Here is the honest framing that most guides to this format skip: in play-by-post, the scarce resource is not time, creativity or rules knowledge. It is the guarantee that the story will move tomorrow.

A weekly session solves this by brute force. Everyone shows up at eight, the game happens, and a person who misses a week misses a week. Remove the appointment and you remove the enforcement, and the game now depends on six people independently choosing to write something, indefinitely, with no cue.

Groups that last have all made an explicit decision about what happens when somebody does not post. The options are well-worn:

A posting deadline with automatic resolution. One post per player per day, or three a week, and the game master resolves the round when the clock runs out regardless of who has replied.
The game master plays the missing character cautiously. They hold position, defend, take the obvious safe action. The story moves; nobody’s character does anything they would object to.
A written expectation at recruitment. “Two posts a week, tell us if life happens” in the recruitment post filters for people who want that pace, which is more effective than any enforcement later.
Small tables. Three players stall far less often than six, because the odds that all of them are busy are lower and the social cost of going quiet is higher.

The number you pick matters far less than picking one. An unstated cadence becomes an open-ended wait, and an open-ended wait is how threads die.

Combat, Which Is Where Most Campaigns Break

Strict initiative order is the enemy. In a six-player fight, sequential turns mean waiting through five other people before you act — so a single combat round can take most of a week, and a three-round fight can take a month. Groups abandon campaigns during combat more than anywhere else.

The fixes are all versions of “stop waiting”:

Resolve simultaneously. Everyone posts their action for the round; the game master resolves all of them together. You lose the tactical precision of reacting to what the fighter just did, and you gain a combat that finishes.

Let the game master roll for absentees. Agreed in advance, this removes the main source of delay at a stroke.

Batch the enemies. All monster turns in one post, rather than a post per creature.

Declare intent, let the game master resolve. “I try to knock the lantern into the oil” rather than a precise sequence of attacks and bonus actions. One exchange instead of four.

This is also why system choice matters more here than at a table. A game with few rolls per turn, few reaction-triggered interrupts, and little grid positioning moves quickly in text. A heavily tactical build-focused game does not. Plenty of groups run 5e in play-by-post successfully, but the ones that enjoy it have almost always loosened positioning and reactions, because those are the rules that assume everyone is in the room.

Where People Actually Play

Four kinds of venue, with genuinely different textures.

Dedicated forums and hosting sites. The traditional home, and still the best for long campaigns: threaded, searchable, and archived in a way chat is not. A campaign you can still read three years later is a real thing that forums give you and chat apps mostly do not.

Discord. Where most recruitment now happens, and where most new games start. Channels per scene, dice bots, and looking-for-group traffic in volume. The trade-off is that chat is a poor archive — scrollback is not a thread — so long-running Discord games usually end up keeping a summary document somewhere else. If this is your route, we have a separate guide to running D&D on Discord with an AI game master.

Virtual tabletops. For groups that want maps, sheets and tokens, most support asynchronous play well enough, and the character-sheet automation removes a lot of the bookkeeping that slows text games down.

AI game masters. The newest option, and the one that changes the format’s economics rather than its interface. More on this below.

Across all four, the binding constraint is the same and it is not technical: finding a game master who will still be there in two months. Running play-by-post is harder than running a table — it is the same prep, spread thinner, with no session to look forward to and a constant low-level obligation to reply. Game masters burn out, and when they do the campaign ends immediately and completely, which is the format’s other characteristic death.

What an AI Game Master Changes

This is where the format meets what we spend most of our time measuring, so it is worth being precise about what is genuinely different and what is marketing.

What it solves, unambiguously: the game master is always available and never quits. There is no recruitment, no waiting for a reply from someone at work, and no campaign-ending burnout. For a format whose two failure modes are “a player went quiet” and “the game master disappeared”, removing one of them outright is not a small thing.

What it solves partially: the quiet-player problem becomes a rules problem instead of a social one. Tabled, which is built specifically for asynchronous 5e-compatible play, publishes the sharpest version of this we have seen: its table pact “nudges quiet heroes after twelve hours and the round resolves itself after twenty-four”, with a stated cadence of “one thoughtful move a day, or five rounds in a lively evening”. That is the hobby’s oldest etiquette problem restated as a timer. One invite code seats up to six, and by the studio’s own published terms everyone who joins plays free.

Other platforms approach the same problem from different directions, and our multiplayer guide compares them properly rather than in passing here.

What it does not solve, and this is the part to take seriously: an AI game master is measurably weaker at exactly the thing a long asynchronous campaign is made of. A play-by-post game is long by construction — months, sometimes years — and long-range memory and narrative coherence over dozens of turns are the two qualities the field handles worst. We have written about why campaigns come apart around turn fifty, and it is the single most important thing to know before committing a group to one.

There is also a quieter trade. Part of the appeal of play-by-post has always been the other players — the person who writes a better scene than you expected, the rival character whose motives you cannot predict because a human is deciding them. An AI game master does not replace that. Filling the empty chairs with AI companions is a different game from playing with five friends, and it is worth knowing which one you actually want before you pick a platform that only does one.

Disclosure: Tabled provided comped access for our review. Arcanum is independent and unpaid; no platform mentioned here has any say in our coverage.

Which Rules System Suits It

Short answer: whichever one your group already knows, loosened.

Longer answer: the format rewards systems with fewer decision points per turn. Every roll is a round trip, every reaction is an interrupt that stalls the thread, and every rule that requires knowing exactly where everyone is standing needs a map somebody has to maintain. Narrative-leaning systems tend to run beautifully in text because a whole conflict can resolve in one exchange. Crunchy tactical systems run slowly unless you house-rule the tactical layer.

5e is played this way constantly, and works — with positioning handled loosely, reactions handled by the game master, and combat resolved simultaneously. If you are running with an AI game master, note that mechanical depth is the weakest axis across the entire field we measure, so the systems layer is the part most likely to disappoint. Why AI RPGs can’t do mechanics covers what to expect and which architectures do better.

Starting One This Week

A short checklist that prevents most early deaths:

Pick the pace and write it down. “One post per player per day” or “three a week”. Put it in the recruitment post.
Decide what happens when somebody misses. Game master resolves the round anyway, or plays the character cautiously. Say which.
Start smaller than you want. Three or four players. You can add more; you cannot un-stall a six-person thread.
Separate in-character and out-of-character from post one. A second channel or a prefix.
Open on a decision, not a description. Your first post should end with something to answer.
Agree the dice method. Bot, platform roller, or game master.
Keep a running summary. One document, updated weekly. This is what lets somebody return after three weeks away, and with an AI game master it is also what keeps the plot coherent past turn fifty — how to summarise a long campaign covers the technique.

None of that is about writing quality, and that is deliberate. Play-by-post campaigns rarely fail because the prose was not good enough. They fail because a round could not resolve, and nobody had decided in advance what to do about it.

Answer that question first, and the format does what it promises: a campaign that survives everyone’s calendar.

Frequently Asked Questions

What is play-by-post D&D? Play-by-post is a roleplaying campaign played in writing, in turns, without everyone being present at the same time. Instead of a three-hour session on a Tuesday, the game master describes a scene, each player writes what their character does whenever they next sit down, and the game master resolves all of it into the next scene. A round can take a day or a week. It is the same game as tabletop D&D with the clock removed, and it is played on forums, in Discord servers, in dedicated apps, and increasingly with an AI game master.

How does play-by-post work? The game master posts a scene that ends on a decision. Players reply in character with what they do, usually one post each per round, and the game master writes the outcome and the next scene. Most groups separate in-character writing from out-of-character discussion, either with formatting or with a second channel, so questions and rules arguments do not clutter the story. Dice are rolled by a bot, a roller built into the platform, or the game master. The critical rule is whatever the group has agreed happens when somebody does not post, because that is what decides whether the campaign survives.

How long should a play-by-post turn take? Set an explicit deadline rather than a hope. Common healthy cadences are one post per player per day for fast games and two or three posts a week for slower ones, with the game master resolving the round on a fixed schedule whether or not everyone has posted. The number matters much less than having one, because the alternative is an open-ended wait that stalls everyone. Groups that thrive publish the cadence up front and treat a missed post as a character acting cautiously rather than as a reason to pause the campaign.

How does combat work in play-by-post? Strict turn order is the thing that kills it, because a six-person initiative order means waiting five times per round. The usual fixes are to resolve all player actions simultaneously within a round rather than in initiative sequence, to let the game master roll on behalf of anyone who has not posted by the deadline, and to batch enemy turns into a single post. Some groups declare intent and let the game master resolve the mechanics, which converts a whole round into one exchange. Systems with fewer rolls per turn and fewer reaction-triggered interrupts run faster in this format than heavily tactical ones.

Where can I play play-by-post D&D? Four kinds of place, each with a different feel. Dedicated forums and hosting sites keep long threaded archives and remain the traditional home. Discord servers are where most current recruitment happens, and looking-for-group channels are the fastest way to find a table. Virtual tabletops support asynchronous play for groups that want maps and character sheets. And AI game masters run the format solo or with friends without needing a human to volunteer for the hardest job at the table. The practical constraint is not the platform but finding a game master who will still be there in two months.

Is play-by-post better than playing with an AI? They fail in opposite directions, so it depends on which failure you can tolerate. A human-run play-by-post game gives you a game master who genuinely surprises you and other players who are genuinely creative, at the cost of pace and a real risk that the campaign dies when a person drifts away. An AI game master always posts back within seconds and never cancels, at the cost of a narrator that is measurably weaker at long-range memory and at holding a plot together across fifty turns. Many people run both, for different itches.

Platform details checked on 18 September 2026. Dungeons & Dragons is a trademark of Wizards of the Coast; Arcanum is an independent publication with no affiliation to it, and references here are nominative.