Codex
Open Codex

How to

How do you play a tabletop RPG by yourself?

To play a tabletop RPG alone, you replace the game master's surprise with a repeatable loop: set a scene, ask a yes-or-no question, roll on an oracle or random table to get an answer, interpret the result in context, write down what is now true, and let the consequences shape the next scene. You need a character, a place to start, one set of rules (or none), dice, and somewhere to keep notes. No game master, group or prepared adventure is required.

A lone player at a worn oak table at night with a hand-drawn dungeon map, dice and an open journal lit by a single candle

What changes when there is no game master

In a group game, the GM does three jobs at once: they decide what the world contains, they answer questions the players cannot answer themselves, and they surprise everyone. Playing alone, you still make decisions as your character, but the other two jobs have to come from somewhere other than your own head, because you cannot be surprised by something you chose.

That is the whole reason solo play uses oracles and random tables. They are not there to make the game random for its own sake. They give you an answer you did not pick, which is the thing a GM normally provides. Your own interpretation then turns that answer into something that fits the scene.

Solo play does not require a dedicated solo game. Many players use a published solo system, but you can also play a favourite group RPG alone by adding an oracle, or run a dungeon crawl from random tables with no story at all. The loop below stays the same across all of them.

What you need to start

Most solo sessions begin with a short list, and none of it needs to be bought new:

  • A character One protagonist is simpler than a party. Write down a name, a goal, and one reason they would leave home today. The goal is what makes your later choices feel like choices.
  • A ruleset, or a deliberate absence of one Use a solo-friendly system, a group system you already know, or plain fiction-first play where you decide outcomes with a die and common sense. Pick one and stay with it for the first few sessions.
  • An oracle Any method that answers yes-or-no questions with a probability you chose, for example rolling a six-sided die where a 4 or higher means yes. A published oracle adds structure, but a simple one is enough to begin.
  • A way to generate surprises Random tables, prompt cards or generators for names, rumours, complications and places. This is what stops a scene from only containing what you already expected.
  • A place to write things down A notebook, a document or a vault. Solo play produces facts quickly, and a fact you cannot find again is a fact you will eventually contradict.

The basic solo loop

A single scene runs through the same six steps:

  1. Set the scene State where your character is, what they want right now, and what you expect to find. Write one or two sentences.
  2. Ask a question When you reach something you do not know, such as whether the door is locked or whether anyone is home, put it as a yes-or-no question.
  3. Roll for the answer Use your oracle. If the result seems to demand a twist, roll on a table for a complication or a new detail.
  4. Interpret Decide what the result means in this specific scene. This step is where your judgement does the work a GM would do.
  5. Record what is now true Note the new person, place, threat or promise. Keep it short, but write it down.
  6. Let consequences carry forward End the scene on a change, then open the next one from it. A scene that changes nothing is a scene you can skip.

Example

One scene, start to finish

A solo player runs a wandering archivist called Maren who has come to a flooded chapel looking for a missing ledger.

Set the scene
Maren wades into the chapel at dusk. She wants the ledger, and she expects the place to be abandoned.
Ask and roll
The player asks, "Is anyone else here?" and rolls on a likely-yes oracle. The answer is yes, with a twist result on the same roll.
Interpret
A twist could mean anything, so the player rolls on a short complication table and gets "an old debt". The visitor becomes a ferryman who once carried Maren's late mentor, and who now wants payment.
Record and carry forward
The player writes down the ferryman, the debt, and the fact that he knows where the ledger went. The next scene begins with Maren deciding whether to pay him.
Why it works
The player chose none of the surprising facts alone. The oracle supplied the yes and the twist, the table supplied the debt, and the player's interpretation tied them to Maren's history, so the scene reads as if a GM had prepared it.

Before your first solo session

A short setup is enough, and it saves a lot of stalling later:

  • Write one sentence describing your character and one concrete goal for them.
  • Choose a single ruleset, or decide to play without one, and keep it for at least three sessions.
  • Pick an oracle and write down its answer odds so you do not redesign it mid-scene.
  • Prepare a handful of random tables or a generator for names, rumours and complications.
  • Decide where notes will live and write the first entry before you roll anything.
  • Plan a short first session, such as a single location with one question driving it, so you finish with a complete scene.

Was this useful?

Keep the facts your oracle hands you

Solo play generates new facts faster than a normal campaign, because every question can add a person, a place or a debt. Codex Cryptica lets you store each of them as a connected entry the moment it appears, so a ferryman you invented in session one is still findable in session ten. The generators for names, rumours, factions and settlements also supply the random detail that a solo loop depends on.

See Codex Cryptica for solo worldbuilding

Related

Topic Hubs

Tools

Guides

Other answers