How to Run a Solo RPG With More Handholding and Fewer Rules to Look Up

Start with a game that supports the kind of guidance you want

There are two useful starting points. A solo-first game builds prompts and procedures into its rules; an RPG designed for group play can be paired with a game-master emulator, which supplies answers and surprises when no GM is present. The choice changes how much you need to assemble yourself.

For a ready-made structure, Ironsworn is designed for guided, co-op, and solo play, and its materials include story hooks, prompts, oracles, and reference resources. Its free digital edition includes the rulebook, character sheet, asset cards, and additional references. Those resources can make it easier to begin without constructing a solo toolkit from scratch. Ironsworn by Shawn Tomkin

If you already have a preferred RPG, an emulator such as Mythic Game Master Emulator can sit beside it. Its publisher describes tools for yes-or-no questions, random events, meaning tables, lists of important goals and characters, scene structure, and a Chaos Factor that affects the adventure’s pace. That breadth can offer more explicit guidance, but it also means learning another procedure. Mythic Game Master Emulator Second Edition

A useful rule of thumb: choose the smallest system that can answer the questions your session is likely to raise. If the RPG already gives you procedures for travel, danger, and discovery, an extra oracle may be unnecessary. If you keep pausing because you do not know what happens next, a game-master emulator or a dedicated solo game can fill that gap.

Make a compact play sheet before the first scene

The most effective way to reduce lookups is to decide what information deserves to stay visible. Before play, gather the character’s key statistics, the most-used resolution rule, the rules for harm or setbacks, and any special ability that is likely to affect the opening situation. Use a bookmark, a short handwritten note, or the game’s own quick reference if one exists. Do not copy the whole rulebook.

Then write a short premise in ordinary language: who the character is, what they want right now, what stands in the way, and what would count as a satisfying session ending. Keep it specific enough to guide choices but open enough that a roll can change events. For example: “A courier wants to deliver a sealed map before the mountain pass closes; the bridge keeper has not appeared.” This is an illustrative setup, not a published scenario.

Make a small “lookup boundary” note too: resolve character actions with the RPG’s rules; use the oracle for uncertain world facts, NPC intentions, or unexpected developments. That boundary prevents the oracle from replacing every game mechanic and prevents you from treating every unknown as a rules question.

Use an oracle for uncertainty, not for every choice

An oracle is a procedure for answering questions whose outcomes are uncertain. In Mythic, the core approach uses yes-or-no questions, with additional tools for random events and prompts. Ironsworn includes oracle tables that provide narrative inspiration. These tools guide play by returning material for you to interpret; they do not write a finished scene for you. Mythic GME 2e · Ironsworn official rulebook

Ask a question only when its answer could change what your character does. “Is the door locked?” matters if the character must get through it. “Is the room dusty?” may not matter unless the dust could reveal tracks or signal recent activity. For each question, state your best expectation first, use the game’s specified odds or table, then interpret the answer in the current context.

Keep questions narrow. Instead of “What is happening in the town?”, ask “Does the innkeeper recognize the crest?” If the result is surprising, add one detail and make it actionable: perhaps the innkeeper recognizes it but refuses to say where. The answer should create a next move, not trigger an endless chain of clarifications.

Run each scene through the same short loop

Use a repeatable loop to keep the session moving. It is a practical synthesis of oracle-led play and scene-based procedures, rather than a substitute for any game’s rules.

This loop provides handholding because it gives you a next step at each pause. It also sets a natural limit: one oracle answer can be enough to continue. If a result could reasonably mean several things, choose the interpretation that best fits the established situation and opens an interesting decision, rather than rolling repeatedly until you get a preferred answer.

Record only what helps you resume

A solo session does not need a transcript. Journaling games often use prompts, randomizers, and written responses, and the record can range from flowing prose to brief notes. DriveThruRPG’s guide describes that flexibility in medium, voice, and length. Use whichever format helps you remember what happened and decide what comes next. An Adventurer’s Guide to Solo RPG Journaling Games

At the end of a scene, jot down three things: what changed, what remains unresolved, and what the character will try next. A few bullet points may be enough. Record exact rules outcomes only when they affect the character sheet or future decisions. This keeps the journal useful without turning play into a transcription chore.

For a campaign, keep a separate short list of recurring NPCs, open goals, and established facts. When a new oracle answer appears to contradict a previous detail, pause and decide whether it is a genuine change, a misunderstanding, or a cue that the earlier assumption was wrong. Make the revision explicit in your notes so later scenes have a stable basis.

Handle rule gaps without losing the scene

When you cannot recall a rule, first identify what kind of decision it governs. If it controls the character’s chances or consequences, check the rule or a reference sheet. If the answer is a fictional detail, use an oracle. If neither outcome is important enough to interrupt play, make a temporary ruling, note it, and continue.

A practical lookup order is: quick reference first, bookmarked rulebook second, full search only when a rule materially affects the stakes. Avoid switching between multiple sources for the same rule unless the game text is genuinely unclear. If you make a temporary ruling, apply it consistently for the rest of the scene; revisit it after play rather than stopping to settle every edge case.

For example, if a character tries to climb a low garden wall and you cannot recall whether the system calls for a check, decide whether failure would create a meaningful cost. If not, narrate the climb. If failure could expose the character or consume needed time, consult the relevant action rule. The example illustrates a decision process; the exact mechanic depends on the RPG you are playing.

Adjust the amount of guidance between sessions

If you still stall, add structure in one place at a time. You might prepare a short list of likely scene locations, keep a few NPC names handy, or use a game with more built-in prompts. If oracle answers feel too arbitrary, ask narrower questions and anchor interpretations in details already established. If rules lookups dominate the session, simplify the character’s options or choose a game with a concise reference sheet.

The goal is not to remove every uncertainty. Some uncertainty is the source of surprise; the useful distinction is whether you are curious about what happens or stuck searching for a procedure. Keep the first kind in play. Reduce the second with a visible reference, a clear lookup boundary, and a repeatable scene loop.

A quick pre-session checklist

Before you start, check that you can answer these questions without opening several books: What is the character trying to do? Which rule resolves a risky action? What will you use to answer uncertain world questions? What notes will you keep? What would make this session feel complete?

If you can answer those in a few lines, begin with the opening scene. When a pause comes, use the loop: frame, act, ask, interpret, and update. Over time, keep only the procedures that help your particular game move forward.

For players who also enjoy collaborative story-making, Metlivi Adventure is described as an AI adventure game for private co-op story rooms, where friends create cinematic adventures together one move at a time.

Sources

Keep exploring this topic