Chapter 44 — The Session Loop
The oracle answers questions (Chapter 43), but a session is more than questions — it's scenes that open and close, threats that push back, threads that tangle and pay off, and a sense of when to turn the screw and when to breathe. At a normal table the GM supplies that shape. Without one, you supply it with a handful of light procedures. This chapter is the loop that turns the oracle and the toolkit into a game you can sit down and play, alone or together. The next chapter covers what's specific to each — solo and co-op (Chapter 45); this one is the part they share.
Index§
- The session loop
- Framing scenes without prep
- Driving the toolkit
- Running opposition against yourself
- Keeping threads
- Pacing without a GM
- At a glance
The session loop§
A GM-less session runs in scenes, and every scene takes the same shape:
- Frame the scene. State where you are, who's present, and what's at stake right now — one or two sentences. If you're not sure of a detail, ask the oracle or roll a generator (below). Then ask the question that drives every scene, the same one a GM asks: what do you do?
- Play it out. Your Wanderer acts; you resolve uncertain actions with the core test against 8 (Chapter 5), and you resolve uncertainties about the world with the oracle. Most of a scene is the back-and-forth between those two.
- Check for what intrudes. A sparked oracle answer (Chapter 43) can throw the scene open on its own. When a scene runs quiet and you want pressure, roll an encounter (Chapter 41) or consult your threads (below) rather than letting it drift.
- Close the scene and bank it. When the stakes resolve, end the scene. Note what changed — a new thread, a shifted relationship, a wound. Frame the next one, or, if it's the end of a play session, run session-end exactly as written (Chapter 20): roll your marks, take your XP, tally invoked Banes, reset Momentum.
You don't need every step every time. A quiet scene is a frame and a couple of oracle questions; a dangerous one reaches for the damage dice. The loop just keeps you from staring at a blank page.
Framing scenes without prep§
The trick to framing scenes for yourself is to set an expectation, then test it. State what you reasonably expect to find — "the hangar should be empty this late" — and, if there's any real doubt, ask the oracle at the matching likelihood ("Is it empty?" — Likely). A Yes confirms your read and the scene proceeds; a No or a spark hands you something you didn't author. This expectation check is the engine of surprise in GM-less play: it lets you lean on your own sense of the fiction most of the time, while leaving the door open for the world to contradict you.
When you have no expectation at all — a place you've never pictured, a person who steps out of nowhere — don't strain to invent one. Roll it. That's what the toolkit is for.
Driving the toolkit§
Everything a GM would prep, you generate as you reach it. The generation order in the toolkit (Reference — All Tables; Part IX) doubles as your prep loop, run just-in-time:
| When you need… | Roll on… |
|---|---|
| A place to go — system, world, station, settlement | Sectors & Worlds (Chapter 37) |
| A reason to go there — patron, job, the catch, the payoff | Jobs & Salvage (Chapter 38) |
| A wreck to pick over | Salvage (Chapter 38) |
| Someone in the scene — face, demeanor, what they want, a name | People on the Fly (Chapter 39) |
| Something happening to you | Encounters (Chapter 41) |
| A power moving behind it all | Faction Play (Chapter 34) |
| An ally or rival who recurs | Contacts (Chapter 35) |
| A premise to start from, or a rumor to chase | Building Adventures (Chapter 33) |
Read every result through the oracle when it's ambiguous: roll the job (Chapter 38), then ask the oracle is the patron lying about it? The tables give you the what; the oracle gives you the whether; your judgment strings them into a scene.
Running opposition against yourself§
This is where Wanderstar's design pays off most. NPCs don't roll (Chapter 40), so running a threat takes nothing from you but a decision about what it does. When an adversary acts, you roll the skill that meets it against 8 (with Disadvantage if it's dangerous), and on a failure you roll its damage die. There's no enemy turn to play fairly against yourself — only your own defense roll.
What you do have to decide is the threat's intent, and the oracle and the existing tables make that nearly automatic:
- How does it take you? Use the reaction table (Chapter 41) for a starting disposition — hostile, wary, needy, friendly — rather than deciding in your own favor.
- What does it do now? Ask the oracle (does it press the attack? — judge the likelihood from its nature) or read its drive from its stat line (Chapter 40). A cornered mook and a patient hunter want different things; let that, not your preference, choose the action.
- When in doubt, it acts in its own interest, not yours. That's the whole of impartial GMing, and the oracle is there for every genuine fork.
Crewed vehicles and starships keep their own damage track (Chapter 25); even there, you roll your crew's actions and only the enemy's damage. The principle holds: your dice, the world's consequences.
Keeping threads§
The one thing a GM holds in their head that you'll want on paper is the web of open threads — the unresolved questions, debts, goals, and dangers that give a campaign continuity. Keep three short lists (there's a sheet for them in the Reference — GM Record Sheets):
- Threads — every open loop, as a question or a goal. Who hired the rival crew? Pay off the dock-boss before he calls the debt. Find the Sleeper's lost ark. When a scene needs pressure and the oracle hasn't supplied it, pull the next thread forward.
- Cast — the NPCs and Contacts you've met, a line each: what they want, where they stand (Chapter 35). The What Intrudes table (Chapter 43) and the spark love an old face.
- Powers — the factions in reach and their clocks (Chapter 34). Run the faction turn between sessions or across a jump week (Chapter 27) exactly as written — it's the same checklist, and it makes the galaxy move without you steering it.
Threads are how a GM-less campaign avoids becoming a string of disconnected scenes. Spend a sparked answer or a quiet moment to tie a new event back to an old thread, and the story coheres on its own.
Pacing without a GM§
A GM paces a session by escalating — turning quiet into danger when interest flags. You pace yourself with the same dials a GM uses (Chapter 32), plus one structural truth Wanderstar gives you free: trauma is the limiter (Chapter 33). Because harm accrues on two short tracks and the worst nodes need a full recovery session to clear (Chapter 10), you can lean into danger honestly without a GM rationing it — the trauma economy is what stops a scene from spiraling, not your restraint. Push hard, take the consequences the dice deal, and let recovery set the rhythm of rest and risk.
When a session sags, don't wait for permission you can't give yourself. Reach for the bluntest tools: roll an encounter, pull a thread, advance a faction clock, or ask the oracle a question whose Yes would change everything. The world is allowed to act first.
At a glance§
Frame a scene → ask "what do you do?" → resolve actions vs 8 and the world via the oracle → check for what intrudes → close and bank it. Generate places, people, and jobs from Part IX as you reach them. Run threats by intent, never by rolling against yourself. Keep threads, cast, and powers on paper. Let trauma — not willpower — be the brake.