Interludes — Showing the World Without the PC
The engine's most important asymmetry is that the world exists independently of the player. Interludes are the tool that makes that visible: short cutaway scenes where the PC is not present, narrated to the player so the world's off-screen life has texture. This chapter is about the design intent behind them and how to use them without breaking the system.
What an interlude is
An interlude is a POV cutaway — the villain making plans, allies talking about the PC when they can't hear, a lover remembering, the city going about its business, enemies closing distance. It is narrated like any other scene (third-person present, novel-length, vivid) and the player watches it as an audience member. The PC is not there, and the player does not act in it.
The rule that makes them work — dramatic irony
The player may witness an interlude, but the PC does not. The PC never gains knowledge from a scene they were not in. What the player saw surfaces later through things the PC can actually observe — a rumor, a changed expression, an ambush that makes sense in hindsight, a door that's suddenly locked.
This is the load-bearing constraint, and it's the whole point of the mechanic. It keeps interludes from becoming spoilers, and it keeps the player from acting on knowledge the PC has no in-fiction way to possess. If you build on this system, preserve it: an interlude that hands the PC information directly breaks the honesty of the fiction, and the player's anticipation is the flavor you're actually buying.
Why they exist
Two existing rules pay for interludes: the world does not scale to the player, and NPCs have their own lives. Interludes are the payoff of both — they let the player feel the world moving without them. They build dread and anticipation, deepen NPCs who otherwise only exist when the PC walks into the room, and make consequences feel earned when they finally arrive in a scene the PC is part of.
Restraint is part of the design
An interlude is a beat, not a full scene — a few paragraphs, one or two per session, at natural seams (between scenes, during travel or downtime, as a cold open). If an interlude can't be felt later in a scene the PC actually experiences, cut it. The PC's scenes are the main course; interludes are garnish. A session that is mostly cutaways has stopped being the player's story.
What they must never do
- Never let the player act in one. The PC isn't there; the player watches only.
- Never resolve the PC's fate off-camera. The PC cannot die, and interludes don't get to reach them where the fiction won't.
- Never dictate what the PC will feel or think about what they learn later.
- NPCs still act only on what they reasonably know. An interlude is one NPC or group's moment, from their own knowledge — never a God's-eye tour.
Building on interludes
If you're adapting the engine to a setting, you can give interludes a shape without touching the core:
- Define who is interlude-worthy. In a cyberpunk game, the corps and the fixers; in fantasy, the court and the rival houses; in a space game, the fleet and the syndicates. Interludes are how you keep those threads alive between the PC's scenes.
- Decide how interludes surface in your setting. Rumors, news, messages, changed behavior, a locked door. The surface is the PC's bridge back into the story — it's how the dramatic irony pays off.
- Keep the POV honest. An interlude shows what one person or group knows and does, never omniscience. If you need the player to know something no NPC could, that's not an interlude — that's a problem with the reveal.
The rule of thumb that governs everything else: an interlude should change something the PC will eventually feel. If it doesn't, it's decoration — and the system has no room for decoration that doesn't pay off.