Solo D&D 5e: what you give up, and what you get for it

You can play D&D 5e on your own, and it is still the game - the same sheet, the same rolls, the same decisions. What it is not is a table, and that is worth being honest about before anything else.

Start with what you lose

A page about solo play that skips this part is not worth reading. You lose the table, and the table is most of what people mean when they say they love this game.

You lose the jokes. You lose the moment somebody does something so ill-advised it becomes the thing your group still quotes four years later. You lose being surprised by another player, which is not the same as being surprised by a Game Master: a GM's surprises are authored for you, and a player's are not authored at all. You lose shared memory too - a campaign that lives in five heads is a heavier object than one that lives in your own.

None of that is replaceable, and nothing below tries to replace it. If you have a group that meets and it works, keep it. This is not an argument for leaving a table; it is about the nights you do not have one.

What one player gets that four never do

The trade runs both ways, and a group has costs you may never have noticed.

The pace is entirely yours. A scene can take an hour or four sentences. You can spend an evening on one innkeeper without three other people going quietly out of their minds, and skip a week of travel in a line because nobody has to agree.

The character is wholly yours. No party consensus, no negotiating a concept against four other concepts, no pressure to cover the gap nobody else filled. You are not the healer because somebody had to be.

You can play the character nobody would let you bring. The coward, the liar whose lies matter, the paladin who is wrong about something important, the build that is mediocre in a party and interesting alone. At a table those impose on somebody else's evening. Alone they are just the game.

There is nothing to schedule, which matters because most campaigns die on a calendar rather than on a story. And it is there at seven in the morning on a Tuesday: fifteen minutes is a real session when the game waits for you.

Encounter math assumes four characters

You know this already, and it is the first thing that actually breaks. The XP budgets, the difficulty bands and the multiplier for the number of monsters all assume a party of roughly four. A medium encounter for four is not a medium encounter for one; it is a coin flip, and the coin is weighted, because what kills you is the number of attack rolls arriving each round rather than the size of any one of them.

Two honest fixes exist and both are authorship rather than arithmetic. Cut the number of bodies on the other side instead of only shaving their hit points. And put something on your side with a turn of its own. The Reclamation, the campaign most people start, was written for this product, and this product has never had more than one player in a game - it is not a party module with the numbers filed down.

An ally is first-class here rather than a narrative flourish: every participant in the initiative order is typed as a player, an NPC or a monster, so a hireling or a bound companion holds a real slot and acts on its own turn.

Nobody is going to stabilize you

At a table, zero hit points is a setback: somebody spends an action, somebody drags you out. Alone it is the whole question, because there is no cleric, no Medicine check from the person standing over you, and nothing between you and three failed saves but the dice.

That is not softened here, and not fudged either. Death saves belong to Keystone Engine: successes and failures are stored on your character between turns rather than remembered, three failures is death, a natural 20 puts you back up at 1 hit point. At 0 you stay in the initiative order, because a dying creature still takes its turn to roll, and what stops you acting is the unconscious condition rather than removal from the fight. ROWAN finds out how the save went at the same moment you do.

What follows is a different way of playing, and experienced players arrive at it fast. Survivability beats damage when nobody is standing in front of you, a healing potion is standard equipment rather than a luxury, and retreat stops being an admission and becomes a tactic.

The action economy is the actual difficulty

Four goblins against four characters is a fight. Four goblins against one character is four attacks a round into one, and one action back. Nothing in the rules fixes that, because it is not a rules problem - it is who is in the room.

Keystone enforces the per-turn economy strictly, for you and for everything else: one action, one bonus action, one reaction, with spell components, concentration, resistance and immunity applied where they fall. But enforcing the economy honestly is not the same as fixing the ratio, and two things fix the ratio. The first is the party: on the paid plan a run holds several characters - you play the ones you want and ROWAN runs the rest as companions, each with its own slot in the initiative. The second is encounter design - fewer and larger threats, hazards that are not creatures, terrain that costs the other side something.

You cannot referee yourself, and solo is where that bites

At a table this is invisible, because it is somebody else's job. Alone, the person deciding whether that door is DC 15 or DC 12 is the person who wants to get through it. Nothing stops you rerolling, or deciding after seeing the number that the guard was distracted anyway. It ends more solo campaigns than lethality does, and it never feels like cheating while it happens - it feels like good judgement.

Which is why a separate rules engine matters more alone than it ever does at a table. At a table the Game Master is the separation. Alone it has to be built, and here it is two systems that do not share a job. Keystone Engine enforces the rules: it rolls every die on the server, applies the modifiers off your sheet, and owns hit points, conditions, spell slots, currency and inventory. ROWAN narrates the world: it is handed the result afterwards, gets no say in it, and cannot roll again. The number exists before any narration exists, so there is nothing left to lean on.

What is enforced, and what is not

71 sections of D&D 5e are enforced in code today. Conditions are stored and applied by the dice code itself: auto-failed saves, attacker advantage, the cannot-act block.

Position - the place text-based play has always failed - now splits down one line: the battle map. At locations the campaign author mapped, the fight runs on a grid and the engine enforces it: movement is spent from real speed, difficult terrain costs double, cover adjusts the AC every attack is checked against, a wall stops a fireball, a bow has a real range, flanking earns its advantage, and opportunity attacks are detected from the path your token actually took. At unmapped locations combat stays narrated, and fog of war is not modeled anywhere. Which is which is published rule by rule, with what actually happens today, at /rules-coverage.

If the tactical layer is your favorite part of fifth edition - the battle map, the five-foot step, the fight as a positioning puzzle - you get it wherever the campaign author drew a map, and prose everywhere else. The other limits, plainly: solo only, with no way to invite anybody; and async play-by-post - you take a turn, the world answers, and it waits.

So, does it count? You are making the same decisions under the same rules, against dice you do not control, with a character who is entirely your own. What you are not doing is sitting at a table, and nothing here is going to pretend otherwise.