How to Play Both the Hero and Game Master in a Solo RPG Without Knowing Every Answer
When you play a solo role-playing game, you make choices as the hero and also decide what the world does in response. You do not need to plan every scene or invent a definitive answer to every question. Give your character a clear objective, use the game’s rules for actions, and consult a simple oracle when the outcome is genuinely uncertain. Then interpret the result in the context of what has already happened. This approach lets you discover a story through play while keeping the hero’s decisions meaningful.
What does it mean to play both roles?
As the hero, you decide what your character wants and what they try. As the game master, you frame scenes, portray other characters, establish obstacles and interpret consequences. In solo play those roles sit with one person, but they do not have to happen at the same time. You can first state the hero’s intention, then use rules or chance to determine what the world returns.
A solo oracle is a procedure for resolving questions that a game’s ordinary rules do not answer. It may return a yes or no, a complication, or a prompt such as an action or theme. The result is input for your judgment rather than a complete scene written on your behalf. Ironsworn, for example, is designed for solo, cooperative or guided play and includes oracle tables for narrative inspiration. Mythic Game Master Emulator describes a yes/no oracle, random events and a Chaos Factor for changing the pace of a developing adventure. Ironsworn official game page, Mythic Game Master Emulator
Start with a playable objective and a few established facts
Choose an objective that can generate several decisions, but is narrow enough to guide the next scene. “Find out who took the bell from the village watchtower” gives you a reason to investigate, question people and explore. “Have an adventure” does not tell you what to do next. You can make the objective more open-ended if discovery is part of the appeal, but give your character a near-term lead: find the tower keeper, reach the market before dusk, or inspect the empty bell frame.
Write down only the facts that will help you make decisions: the setting’s basic logic, what the hero wants, what they know, and perhaps one or two important characters or locations. Treat these as established until play gives you a reason to revise them. A guide to solo D&D from Oracle RPG likewise recommends grounding decisions in the setting’s story logic and tracking a clear objective. That source describes one particular system; you can use the general planning idea without adopting its specific progress or setback rules. Planning and Playing Solo DnD Adventures
Use the game’s rules for actions and an oracle for open questions
Separate two questions that can easily get tangled: “Can my character do this?” and “What is true about the world?” Use the RPG’s action rules when the character attempts something risky and the game has a relevant mechanic. If the character tries to climb a slick wall while pursued, a skill check or move may determine whether they succeed and what the cost is. Do not replace that roll with an oracle unless the game’s rules tell you to.
Use an oracle for facts that no existing rule or established detail settles. Is the side gate unlocked? Does the shopkeeper recognize the stolen emblem? Is the road watched tonight? Before rolling, decide what the likely answers mean for the scene. If the question is trivial, already answered, or entirely under your control as narrator, choose the answer that best follows the fiction and continue. Randomness is most helpful where either result could lead to play.
Ask questions that create a usable answer
A vague question such as “What happens now?” asks a small tool to do too much. Narrow it to one uncertain fact: “Is the stable door barred?” or “Does the courier know the bridge keeper?” Decide whether a yes seems likely, unlikely or evenly balanced if your oracle uses odds. Then roll once and interpret the result. Different oracle systems use different procedures, so follow the specific rules of the tool you have chosen.
For richer prompts, ask about a detail rather than the entire plot. “What stands out in the abandoned station?” can be answered with a location, object or mood prompt and then connected to the current objective. If a table gives you a surprising word or pairing, make it concrete: a “hidden” “warning” might become a scratched message under the station map. Keep the part that fits the established scene and adapt the rest. Oracle tables in Ironsworn, for example, offer action, theme and other prompts; Mythic includes random events as well as yes/no questions. Ironsworn official rulebook, Mythic Game Master Emulator
A worked example: investigate the missing bell
Suppose the hero reaches the tower and sees that the bell is gone. You already know the bell was removed; asking an oracle whether it is missing would add nothing. The hero searches the ground for tracks. Resolve the search with the game’s skill rules, since this is an action the character undertakes. If the rules produce a partial result or failure, let that outcome add a cost or complication according to the game’s procedures.
The hero then asks whether the keeper’s door is locked. This is a world-state question. If your oracle says yes, the hero must find another way in, ask around or return later. If it says no, that still does not decide what the keeper will say. The hero knocks and asks about the bell. If the keeper’s reaction is uncertain, make a separate, focused question or use a relevant social mechanic. Avoid asking several oracle questions in a row just to force a preferred outcome; let each answer change what the hero can reasonably do next.
For an unexpected result, connect it to the objective. Perhaps the keeper is absent, but a wet footprint leads to the bell rope. That detail gives the hero a choice: follow it, search the keeper’s room, or take the clue to someone who knows the grounds. This is an illustrative example, not a recorded playtest result. Its procedure is to establish what is known, resolve the character’s action with the game’s mechanics, and use the oracle only for the remaining uncertainty.
Interpret results without taking control away from the hero
An oracle can suggest what the world contains, but the hero still chooses how to respond. If a result introduces a witness, it does not require the character to trust them. If a clue appears, it does not dictate which lead to follow. Keep a clear line between new information and the character’s decision, and the two roles remain easier to manage.
When a result seems strange, first look for a plausible connection to the setting and immediate situation. If several interpretations work, choose one that opens a decision or adds a manageable obstacle. If none fit, rerolling may seem tempting, but first ask whether the odd result could be a twist. If it would break a firmly established fact, discard or adjust it. The oracle is there to support the fiction, not erase what you have already agreed is true.
Track continuity and keep scenes moving
Use a short journal rather than a transcript unless detailed prose is part of the fun. Record the objective, names, locations, clues, unresolved questions and any important changes. After a scene, write a sentence or two about what happened and what the hero is likely to try next. This reduces the need to re-create facts from memory and makes it easier to resume after a break.
When play stalls, identify the next concrete decision. Is there a lead the hero can follow? Is a known character likely to help or obstruct? Does a resource, deadline or location create pressure? If no question matters yet, frame a new scene that follows from the objective and let the character act. The Oracle RPG guide similarly uses an adventure worksheet to record objectives, progress and important story events, though its specific mechanics belong to its own system. Planning and Playing Solo DnD Adventures
A simple turn procedure for your next session
Use this sequence whenever you are unsure how to run the next beat:
The main discipline is restraint: do not roll for every detail, and do not decide every important outcome in advance. Use rules for character actions, an oracle for uncertain world details, and your own judgment to connect their results. When you finish a session, the hero should have made choices, the world should have answered in some way, and you should know what question or decision could start the next scene.