Skip to content

Solo Oracle and Session Loop

Overview

Solo oracle and session loops convert scattered solo tools into a single playable runtime. Instead of rolling disconnected prompts, the player cycles through a stable sequence: establish intent, resolve uncertainty, apply pressure, update world state, and continue.

The loop's purpose is continuity. It keeps solo play from drifting into unrelated scenes.

Core Pattern

The model is five-stage:

  1. track active threads and elements
  2. frame a concrete scene question
  3. resolve uncertainty with an oracle ladder
  4. apply consequence and pressure movement
  5. close scene with state updates

Each stage leaves a record that feeds the next scene.

Standard Session Loop

  1. State pass: list active Threads (goals, plots) and Elements (NPCs, factions, locations, items).
  2. Scene frame: ask one operational question about what happens now.
  3. Oracle pass: answer with probability tiers; on exceptional outcomes, trigger event logic.
  4. Pressure pass: advance a clock, matrix position, or equivalent tension tracker.
  5. Resolution pass: run encounter, travel, social, or mission procedure as required.
  6. Aftermath pass: update Threads/Elements, prune stale entries, and seed one next-scene hook.

Why It Works at the Table

  • Keeps GMless play coherent across long campaigns.
  • Prevents oracle spam by tying every roll to a scene question.
  • Produces visible campaign drift through tracked threads.
  • Supports both dungeon and urban mission play with the same skeleton.

Oracle Rule

Use a short probability ladder rather than bespoke tables for every question.

  • very likely
  • likely
  • uncertain
  • unlikely
  • very unlikely

On exceptional outcomes, fire a random event that changes or creates a Thread/Element. This prevents solo play from stagnating.

Pressure Rule

A solo loop is strongest when uncertainty is paired with pacing pressure.

  • expedition mode: hazard or supply pressure
  • mission mode: hex-flower or clock escalation
  • social mode: relationship or faction heat shifts

Without pressure, solo scenes become consequence-light.

Between-Session Cleanup

At session end:

  1. advance one unresolved major thread
  2. downgrade or remove dead elements
  3. promote one emerging element to campaign significance
  4. log one concrete world change

This makes the next session start faster and more legible.

Referee-Free Governance

The loop uses existing procedures rather than replacing them:

  • reaction rules decide disposition
  • procedural generation decides space growth
  • pressure systems decide escalation
  • oracle only handles genuine uncertainty

This preserves old-school procedural texture in solo mode.

Design Guidance

  • Ask narrower scene questions to reduce oracle ambiguity.
  • Tie every random event to a tracked thread or element.
  • Keep thread count low enough to manage at a glance.
  • Use one primary pressure tracker at a time unless complexity is intentional.

Practical Comparison Rule

Use this concept when solo play needs campaign continuity and reliable pacing. Use isolated prompt tables only for short one-shot inspiration bursts.

See Also