What is an oracle, and why solo RPGs live or die by it

Every solo RPG eventually hits the same wall. You’re playing a ranger tracking a smuggler through a city you invented. You ask: does the fence know where the shipment went? And then you sit there, pen in hand, knowing that you — the same person who invented the smuggler, the city, and the fence — are about to decide the answer.

If you say yes, you feel like you’re writing a novel where you already know the ending. If you say no, it feels arbitrary. Either way, the surprise is gone, and surprise is half of why you play.

The oracle is the solution to that problem. It’s the reason solo RPGs are a distinct hobby, not just journaling with dice.

What an oracle actually is

An oracle is any mechanism that produces a meaningful answer you didn’t choose. In its simplest form, it’s a yes/no coin flip: heads the fence knows, tails she doesn’t. But a good oracle does more than randomise. It calibrates probability, introduces complications, and occasionally throws in something you never would have scripted.

The classic implementations — Ironsworn’s Action/Theme tables, Mythic GME’s Fate Chart, and their many descendants — all share the same architecture:

You ask a stakes-bearing question. Not “is the sky blue?” but “does the fence know where the shipment went, and will she tell me?”
You set the odds. Likely? Unlikely? Fifty-fifty? The oracle weights the dice accordingly.
You roll and read. The result is a yes, a no, or a yes-but / no-and that introduces a complication or twist.
You interpret. The oracle gives you a raw result; you weave it into the fiction.

That last step is where the craft lives. “No, and…” doesn’t tell you what happens next — it tells you something goes worse than expected, and it’s your job to decide how. The oracle constrains the possibility space without filling it in. That’s what keeps the story genuinely surprising to the person telling it.

Why “honest dice” matters more than it sounds

Here’s the subtle thing: the oracle only works if you trust it.

If you’re using an AI storyteller that decides outcomes on your behalf — no visible roll, no published table, no auditable logic — you can’t tell whether the narrative is being managed for you. Did the villain escape because the dice said so, or because the system thought a cliffhanger would be more engaging? You’ll never know, and over time that uncertainty hollows out your investment in the story.

The oracle tradition insists on transparency. The dice roll in the open. The table is published. You can see exactly why the fence doesn’t know about the shipment, and you can trust that it wasn’t arranged for dramatic effect. That trust is what lets you feel the story happening to you rather than being performed for you.

This is why Soliloquest is built on the oracle tradition rather than pure AI narration — and why the AI Storyteller’s job is interpretation and prose, not outcome determination. The Mythweave play loop keeps the oracle at the centre: you ask, the dice answer, the Storyteller helps you read what the answer means. See also how Soliloquest compares to AI Dungeon, which takes the opposite approach.

The anatomy of a good oracle question

Most new solo players ask weak oracle questions. Here’s the difference:

Weak: “Is there a guard at the gate?”
Strong: “Is the gate lightly guarded enough that I can bluff my way through?”

The weak question has a trivially yes answer that doesn’t advance anything, and a no answer that just adds an obstacle with no texture. The strong question is binary in a way that actually matters: yes means one scene, no means a different and harder scene. Both answers are interesting.

A good oracle question has three properties:

Stakes. Something changes depending on the answer.
Specificity. You’re asking about a particular situation, not a general condition.
Interpretability. A “yes, but…” result should be able to mean something concrete, not just “yes, but somehow.”

Getting comfortable with oracle questions is the single skill that most improves solo play. If you’re new to it, the walkthrough of a real solo session shows this in practice — actual questions asked, actual rolls made, actual complications that emerged.

Omens, entropy, and the chaos factor

Pure yes/no oracles are powerful, but the richer implementations add a second layer: the chaos or entropy tracker.

In Mythic GME, the Chaos Factor rises when things go wrong and falls when the party has control. A higher Chaos Factor means random events are more likely and “yes” answers are harder to get. The world feels more out of control because it is more out of control — the oracle is modelling the fiction’s internal state.

Ironsworn handles this differently, through the Tension Clock and the Pay the Price mechanic: every failure has a cost, and costs accumulate into complications that feel organic rather than arbitrary.

Soliloquest calls this layer Omens and Entropy. The entropy track rises with misfortune and falls with victories; when it’s high, the oracle leans toward complications and unexpected events. You can see the track at all times, which means you can feel the story’s momentum — and plan accordingly.

The oracle vs. the AI: a clarification

People often ask: if there’s an AI Storyteller, why do you need an oracle at all?

The answer is that they do different things. The oracle determines what happens. The AI helps you understand what it means and renders it as prose.

When you roll “no, and…” on whether the fence knows about the shipment, the oracle has told you something went worse than expected. The AI Storyteller then helps you interpret that result in context — maybe the fence doesn’t know, and your contact in the city has gone silent — and writes the scene in the voice of your campaign. The outcome wasn’t chosen by the AI. The AI is helping you read the outcome the dice produced.

This is the distinction the ChatGPT-as-DM comparison explores in depth: using an AI to replace the oracle versus using it to augment one. The oracle keeps the story honest; the AI makes it readable.

Why this matters for the long game

A solo campaign that runs for twenty, thirty, fifty sessions needs to stay surprising. The oracle is the mechanism that makes that possible. Without it, you’re writing a novel — which is fine, but it’s a different thing. With it, you’re playing a game where the story can genuinely surprise its only player.

The best solo campaigns people share online — the Ironsworn AARs, the Mythic GME actual plays — all have the same quality: things happened that the player didn’t expect and couldn’t have scripted. The villain turned out to be sympathetic. The rescue mission became a heist. The heist became a funeral. The oracle did that.

Once you’ve played a few sessions with a well-calibrated oracle, you stop feeling like the author of your story and start feeling like its first reader. That’s the thing the oracle tradition promises, and it’s the reason solo RPGs are worth playing at all.

Ready to try it? Soliloquest gives you a full oracle — yes/no rolls, omens, entropy, the works — plus an AI Storyteller that helps you read the results. You can start your first campaign free, no subscription required. If you want a gentler on-ramp, the getting started guide walks you through your first session step by step.