Solo RPG Oracle Dialogue: Ask, Interpret, and Move

Use oracle answers as dialogue with the fiction: ask specific questions, interpret in context, and move the scene forward.

A solo RPG oracle dialogue setup with question cards, dice, a blank notebook, tokens, and a scene marker.
Oracle dialogue is a three-part loop: ask, interpret, and move.
On this page

An oracle helps you answer an uncertainty or find a prompt while playing without a game master. Think of it as a conversation between your question, the current fiction, a random result, and your interpretation. The loop is simple enough to write on an index card: ask, interpret, move.

Ask From the Scene

Good oracle questions come from what is already happening. “Does the gate guard know my name?” is easier to answer than “What is the plot?” “What does the abandoned room still contain?” is better than “What should happen now?”

Ask one question at a time. If you ask three at once, the answer will tangle. If you need more detail, ask a follow-up after the first result changes the scene.

First check what the fiction already establishes. If the guard saw you yesterday, you can decide they recognize you; a roll is optional. If the answer is uncertain and either outcome would be interesting, ask the oracle. A yes/no question suits a coin or yes/no table; an open question such as “What complicates the crossing?” needs a prompt table or a choice between possibilities. The beginner oracle guide offers examples of both.

An oracle usually answers a question about the world. If your game has a rule for the character’s attempt, use that rule to resolve the action; do not automatically turn an oracle answer into a success or failure roll. Follow your game’s instructions when they handle the two differently.

Interpret Generously

A result should pass through context. If the table says “cost,” look at what the character values. If it says “delay,” look at time, weather, travel, and relationships. If it says “help,” decide who can help without breaking tone.

Do not force the most dramatic interpretation. Choose the interpretation that creates a playable next move. Keep established facts in view: a “cost” might be a favor owed to the guard, not a sudden attack by someone already established as friendly. If a prompt has several possible meanings, pick one that fits or list two and choose between them.

Try One Loop

A courier needs to enter a town before the gates close. The guard is cautious, and the courier carries an old pass. The player asks: “Will the guard accept the pass tonight?” Both answers would leave something to do, so the player uses this simple, equal-odds d6 oracle:

d6Answer
1No, and: add a complication
2No
3No, but: add an opening
4Yes, but: add a cost or limit
5Yes
6Yes, and: add an advantage

The roll is 4: yes, but. The guard accepts the pass, but asks the courier to deliver a message inside. That fits the guard’s cautious nature and gives the courier a choice: accept the errand or find another way in. The player decides to accept, notes the promise, and moves the character through the gate. If the game calls for a separate check to complete the delivery, that happens when the character attempts it.

This table is one option, not a universal rule. Each row has a one-in-six chance; use a different table if you want to weight a likely answer, or follow the oracle in your game. For an example of a published approach, Mythic Game Master Emulator describes using yes/no questions and random events to guide solo adventures.

Move Before Asking Again

The common solo trap is endless consultation: roll, interpret, ask again, roll again, ask again. After an answer, move a piece, write a sentence, change a resource, reveal a clue, or choose an action. The table should create play, not replace it.

If an answer feels wrong, reroll or revise it before treating it as established. If it feels flat, add sensory detail or let a simple answer stand. If it feels too intense, soften it to fit your content boundary. Once an answer has changed the scene, record the change; revisit it deliberately rather than rolling the same question until you get a preferred answer.

Keep a Question Log

Write unresolved questions in one place. Cross them out when answered. This gives the campaign continuity without requiring a long recap. It also helps avoid asking the same question because you forgot what was already established.

A short log for the courier might read:

Established: The guard accepted the old pass.
Promise: Deliver the guard's message inside town.
Open: Who is the message for?
Next action: Find the recipient before the market closes.

The open question can wait until it matters. The relationship web guide offers another way to track a promise if the guard becomes a recurring character.

Oracle dialogue is a practice. It gets better when you ask smaller questions and trust yourself to interpret.

Written By

JJ Ben-Joseph

Founder and CEO · TensorSpace

Founder and CEO of TensorSpace and the editor of Fondsites: an engineer working across software, AI, cybersecurity, and biosecurity who builds the site's games and tools.

Keep reading