Definition
What is a solo RPG oracle, and how do you ask it good questions?
A solo RPG oracle is a random method, usually a die roll or a table, that answers questions the game master would normally answer: is the guard awake, who is behind the door, what goes wrong next. Good oracle questions are specific, can be answered yes or no, and are asked about something you genuinely do not know. You set the odds for the answer first, roll, and then interpret the result to fit the scene.
What an oracle does at the table
In a group game the GM holds the hidden information. Playing alone, nobody does, so an oracle stands in for that hidden knowledge. You ask a question, the dice answer it, and you treat the result as true. The point is that you did not decide it, so it can still surprise you.
An oracle does not narrate. It returns a small signal, such as yes, no, yes with a complication, or a pair of words, and you supply the story. This is why oracle play depends on interpretation, and why two players given the same roll can reach different, equally valid scenes.
Common kinds of oracle
| Type | What it returns | Use it when |
|---|---|---|
| Yes-or-no oracle | Yes, no, or either with a twist | You need a fact settled, such as whether a door is locked or a rival is nearby. |
| Meaning or prompt table | Two words, an image or a short phrase | A result needs a flavour, a motive or a surprise you could not have asked for directly. |
| Scene-interruption table | A change to the scene you planned | You expected one thing and want the game to be able to disagree with you. |
| Random generator | A fully formed name, rumour, person or place | You need new material rather than an answer, such as an unnamed innkeeper. |
How to ask a good question
Most weak oracle results come from weak questions. These habits help:
- Ask about something you do not know If you already have a strong idea, you will ignore an answer that contradicts it. Ask only where you would honestly accept either result.
- Make it answerable with yes or no "Who is in the room?" is a prompt for a table. "Is anyone in the room?" is an oracle question. Ask the second, then use a table or generator for the detail.
- Be specific "Does this go badly?" is too broad to interpret. "Does the guard recognise Maren?" gives the answer something to attach to.
- Set the odds before you roll Decide how likely the answer is from what you know. One common approach uses a few steps from unlikely to likely, with a fixed chance for each. Setting them first stops you shifting the odds to chase an outcome.
- Ask one thing at a time A question with an "and" in it produces an answer you cannot read. Split it into two questions and roll twice.
- Treat the answer as settled If you re-ask until you like the result, the oracle stops being a source of surprise. Write the answer down and play from it.
Example
A weak question and a strong one
Maren, a wandering archivist, reaches a locked cellar door beneath a quiet inn.
- The weak question
- "What happens when I open the door?" This cannot be answered with yes or no, so the player rolls on a vague table, gets two unrelated words, and spends several minutes reconciling them.
- The stronger questions
- "Is the door locked?" is likely, so the player sets the odds high and rolls: yes. "Is the innkeeper aware Maren is here?" is uncertain, so the odds are even: yes, with a twist. A short complication table adds that the innkeeper is already carrying the key.
- Why it works
- Each question settled one small fact, and the single twist was kept for the moment that mattered. The scene gained a character with a motive instead of a pile of abstract prompts.
Using an oracle without losing control of the story
A few checks keep oracle play readable:
- Write the question, the odds and the result in your notes before you interpret anything.
- Keep a yes-or-no oracle for facts and a separate table for flavour, and do not ask one to do the other's job.
- Reserve twists for results that would otherwise be boring, rather than treating every roll as a plot point.
- If an answer contradicts something already established, choose the interpretation that keeps both true.
- Stop asking questions once the scene has what it needs, and move on to a decision for your character.
Was this useful?
Systems built for this
- Ironsworn
Its Ask the Oracle move sets a likelihood for a yes-or-no question and resolves it with a single percentile roll, alongside tables for names, places and complications.
- Mythic Game Master Emulator Second Edition
A standalone oracle that answers fate questions on a chart and uses a chaos factor to make scene changes more or less likely as a story grows tense.
Feed the oracle and keep what it says
An oracle answers quickly, so the risk is losing track of what it told you. Codex Cryptica lets you record each answer next to the person, place or faction it changes, and its generators supply the names, rumours and personalities that a yes-or-no oracle cannot. Your own interpretation stays in charge; the tools simply keep the results connected.
See Codex Cryptica for solo worldbuildingRelated
Topic Hubs
Tools
- Plot Twist Generator Roll a complication when an oracle returns "yes, but" and you need something specific.
- Rumour Generator Generate leads and gossip to answer a question a yes-or-no oracle cannot.
- Personality Generator Turn an unexpected arrival into a person with a motive and a flaw.