Signal Zero is the first release in the Loner Files line: self-contained scenarios for Loner 4e, each built around a loaded situation, a cast with competing agendas, and a ticking clock. Think of them as the pilot episode of a show you’ve never seen.

Read Signal Zero on HackMD

This one is set at a remote archaeological research station in the Peruvian highlands. A team has gone dark. The last transmission from Dr. Constanza Reyes cut mid-sentence, mid-word, into static. You are not supposed to be here. Nobody is coming to check on you if you stop checking in. You came anyway.

What Signal Zero gives you: a situation, a cast of characters who are each telling a partial truth, a location full of pressure points, and a mechanic called discovery beats: short authored prose that fires when your fiction reaches specific conditions. Not mandatory scenes. Not roll results. Moments the scenario left waiting for your story to arrive.

The oracle and your instincts do the rest.

This is an open beta. The text is complete and ready to play. I’m looking for:

• Clarity issues anywhere in the rules recap or the cast

• Discovery beats that felt too narrow to fire in play

• Anything that confused your first read-through

Drop feedback here or in the doc comments. All of it is useful.

I’ve been designing around a particular problem for a while now: solo RPG play is at its best when the fiction has weight before you’ve rolled a single die. Not a blank world waiting to be filled, a situation already straining at the seams, with people in it who want things, hide things, and will act whether you prompt them or not.

That’s what I built the Loner Files line to deliver.

What a File Is

A Loner File is a complete solo scenario for Loner: self-contained, ready to play, built around a single loaded situation. You read a briefing. You pick up your dice. You find out how it ends.

Each File gives you:

• A cast of characters with agendas, secrets, and relationships that existed before you arrived

• A location under pressure, with specific discoveries waiting at specific moments

• A ticking clock that shapes the pacing without dictating the outcome

• Discovery beats: short pieces of authored prose that fire when your fiction reaches certain conditions: a confrontation, a revelation, a point of no return

This last element is worth explaining. Discovery beats are not boxed text. They’re not mandatory scenes. They’re moments I wrote and left waiting. The oracle and your instincts bring you to the threshold. The beat is what’s on the other side. It’s the difference between a situation that could go anywhere and one that means something when it gets there.

What a Loner File is not: a gamebook with numbered paragraphs, a sandbox with infinite hooks, or a railroad with a fixed destination. Think of it as arriving on set for the pilot episode of a show that hasn’t aired yet. You know the premise, the players, the pressure. No one, including you, knows the ending.

The First File: Signal Zero

Signal Zero drops you at Pucara Research Station, a converted 1940s mining outpost in the Peruvian highlands at 3,800 meters. The team went dark seventy-two hours ago. You came because you know Dr. Constanza Reyes, and when someone like her stops transmitting mid-word, you don’t wait for an official response.

The lights are on when you arrive. That’s the first wrong thing.

What you find: a dinner table with four place settings and cold food, a generator log with an entry in a hand that isn’t Reyes’s, a comms room with a removed radio component, and a man standing in the excavation pit photographing an artifact with the patient attention of someone doing a job. He hasn’t noticed you yet.

Seven people have converged on this altitude. Among them:

• A charming acquisitions agent who was here before the team disappeared, left, and came back

• A state intelligence officer carrying sealed orders he hasn’t read carefully enough

• A geophysics specialist hiding in the ruins who watched what happened and hasn’t decided whether telling anyone is safe

• A local elder who knows exactly what the artifact is, what it’s for, and where Reyes went, because he helped her leave

• A quietly dangerous operative present in three locations without ever explaining why

Each of them knows something. None of them knows everything. The extraction team lands at dawn.

Signal Zero is built in three phases (survey, fracture, choice) and includes six suggested protagonist concepts, full character creation tables, and everything you need to start playing in under fifteen minutes. The oracle determines what happens. The File ensures that when the fiction reaches certain moments, something authored and specific is waiting there.

I’m genuinely excited about this format. The Files give me a space to work at a different scale than a full game (tight, focused, with a clear emotional and dramatic shape) while staying completely true to how Loner actually plays at the table. Signal Zero is the first. There are more situations already in motion.

More soon.

There’s a particular kind of dread that cosmic horror does better than any other genre. Not the jump-scare kind, not the monster-in-the-closet kind, but the slow, creeping realization that the universe is vast, indifferent, and full of things that were old before humanity learned to speak. That dread, and everything it implies, is what Loner Cthulhu! is built around.

We’re thrilled to announce the release of Loner Cthulhu!, a minimalist solo tabletop RPG of investigation and madness set in the 1920s, an era of jazz and prohibition, intellectual awakening and social upheaval, and, beneath it all, the rising influence of forces humanity was never meant to encounter. You don’t need a gaming group, a game master, or an entire evening to play. All you need is four six-sided dice, something to write with, and the willingness to look into the dark.

Built on the Loner Engine

Loner Cthulhu! runs on the Loner system, the same rules-light, tag-based framework that has built a dedicated following among solo RPG players worldwide. The core mechanic is simple: you play a single Protagonist, guide them through a story that emerges as you play, and test your expectations by consulting the Oracle, a pair of six-sided dice that answers your questions with Yes, No, and everything in between.

Your character isn’t defined by stats or numbers. Instead, they’re described entirely through tags: short, evocative phrases like Determined Archaeologist, Traumatized War Veteran, or Mysterious Inheritor that tell you, and the Oracle, who this person is and what they’re capable of. Two Skills, a Frailty, two pieces of Gear, a Goal, a Motive, and a Nemesis. That’s your investigator. Everything else is story.

The Oracle doesn’t just say yes or no; it says Yes, and... or No, but... Uncertainty compounds. The Twist Counter climbs every time the dice land equal, and when it hits three, something unexpected happens: a third party appears, the location changes, the goal shifts. The story never goes where you plan, and that’s exactly the point.

DriveThruRPG

Amazon

The 1920s: The Perfect Moment to Look Into the Abyss

The game is set in a very specific window of history, and deliberately so. The 1920s are an era of contradiction: modern science pushing forward while spiritualism and occultism flourish in the same drawing rooms; the aftermath of a war that shattered civilization’s confidence in itself; a world where universities are uncovering ancient artifacts, radio towers are crackling with signals from unknown sources, and newspapers are running stories that the editors aren’t quite sure how to explain.

Your investigator might be a Skeptical Scientist forced to confront phenomena that contradict everything they’ve published. A Struggling Writer who finds that the manuscript they’re transcribing from a stranger’s notes is writing itself. A Paranormal Doctor treating a patient whose symptoms have no name in any medical text. The characters in Loner Cthulhu! come from all walks of life; what unites them is an insatiable curiosity, and the terrible cost of satisfying it.

Madness as Transformation, Not Punishment

Here’s where Loner Cthulhu! does something different from most horror RPGs.

Sanity loss isn’t a countdown to failure. It’s a transformation. The Sanity Track has three states, Clear, Unsettled, and Disturbed, before reaching Broken, and each step changes how your investigator perceives and interacts with the world. An Unsettled investigator starts noticing details that stable minds overlook. A Disturbed investigator rolls on a mental state table: Hypervigilant, Obsessively Focused, Temporally Displaced, Emotionally Detached, and each state comes with both a challenge and an investigative advantage.

A Hypervigilant investigator sees danger everywhere, which is exhausting and sometimes wrong, but it also means they gain an edge on detecting cult activity, surveillance, and lies. An investigator in a state of Obsessive Focus may struggle to engage with anything outside their fixation, but on research rolls tied to that fixation, they’re formidable. Even reaching Broken doesn’t simply end the character; it changes them, permanently, in one of six possible ways: Catatonic Withdrawal, Fragmented Identity, Prophetic Madness, Selective Amnesia, Compulsive Documentation, or Protective Delusion.

Sanity can be recovered: through quiet moments with people who accept what you’ve seen, through helping ordinary people with problems that have nothing to do with the Mythos, through acts of beauty or connection that remind you what human life is worth. But if your track ever reaches Broken, the scar remains. Every investigation after that begins with a character who has already looked into the abyss once, and knows what looked back.

The Mythos, in Full

Loner Cthulhu! doesn’t treat the Mythos as a backdrop. It gives you the full hierarchy: Outer Gods, Great Old Ones, and the Lesser Entities that carry out their will, each with their sphere of influence, cult practices, and signature manifestations.

Cthulhu slumbers beneath the Pacific, spreading shared nightmares and mass hysteria through dreams. Hastur, the Unspeakable One, reaches through art and literature, his influence trailing behind decadent theater productions and urban decay. Yog-Sothoth exists simultaneously across all dimensions and time periods, while Nyarlathotep walks actively among humanity in various forms. Each entity points toward a different category of investigation hook: maritime mysteries for one, scientific anomalies for another, artistic corruption for a third, so your story has direction from the very first scene.

The creature roster is equally rich: Deep Ones, Mi-Go, Shoggoths, Ghouls, Byakhee, Star Vampires, and dozens more, each built on the same tag structure as player characters, ready to drop into any scene.

Packed with Tables

Solo RPGs live and die by their random tables, and Loner Cthulhu! delivers. Over the course of play you’ll have access to:

• Investigation Hooks: from shared nightmares among university students to observatory signals from stellar coordinates that don’t exist

• Occult Artifacts: stone tablets whose hieroglyphs rearrange when unobserved, ritual candles that burn without diminishing, ancient keys that open locks they were never designed to fit

• Mythos Manifestations: new colors that human language can’t describe, geometric patterns that cause physical pain when observed, star constellations rearranging themselves in the night sky

• Cult Activities, Helpful Contacts, Hostile Encounters, Climactic Revelations, and more: everything you need to build an investigation from a single strange newspaper clipping all the way to the final, shattering truth

There are also dedicated tables for maritime mysteries, rural secrets, academic leads, corporate conspiracies, medical oddities, family curses, and library discoveries, because the Mythos hides in all of them.

Who Is This Game For?

Loner Cthulhu! is for anyone who has ever wanted to run a Lovecraftian investigation on their own terms, without scheduling a group session, without a game master to prep for hours, and without a rulebook the size of a phone directory. It’s for fans of cosmic horror fiction who want to experience the genre actively, not just read it. It’s for solo RPG veterans looking for a setting that rewards the Loner system’s emergent, oracle-driven storytelling. And it’s for newcomers: the rules fit on a few pages, the core mechanic takes five minutes to learn, and the game is designed to surprise you from the very first roll.

All you need to start is four dice in two colors, a pencil, and a question you’re not entirely sure you want answered.

The stars are almost right.

Based on the Fiction Engine framework and companion essays. This piece adapts the analysis of Open Strategy Games (OSG) from “The Faction and the Fiction” for players, GMs, and design-curious readers navigating the modern TTRPG landscape.

Most tabletop RPGs ask you one simple question: What does your character do?

You answer. The dice or the GM respond. The situation changes, and the story rolls forward. The whole design is built around individual people living inside a shared world.

But what happens when a game asks a completely different question?

What does your faction do?

Suddenly, you’re not inhabiting a hero. You’re steering a republic, a merchant syndicate, or a military coalition from above. The fiction is still the heart of the game. But you don’t experience it from the inside. You read it like a map. You negotiate treaties, position troops, hoard secrets, and outmaneuver rivals.

Does that mean it’s no longer “story-first”?

Not at all. It just means we’ve reached the edge of the map that traditional RPG design theory draws. And what’s sitting just outside it reveals something fascinating about how stories, strategy, and rules actually work together.

Characters vs. Factions: A Shift in Perspective

The “Fiction Engine” framework was built to describe games where players make choices as individuals inside a situation. The diagnostic for fiction drift is simple: Are you thinking about what your character would do, or what the rules allow?

Open Strategy Games (OSG) break that mold by changing the unit of agency. The subject of play isn’t a person. It’s a collective entity with interests, leverage, and long-term goals, but no interior life. You aren’t asking, “What would my character feel?” You’re asking, “Given our port access, our debt, and our rival’s last move, what should we do?”

The fiction is still alive, mutable, and primary. But it’s experienced from the outside, as a contested surface of forces and consequences. This isn’t a flaw. It’s a different kind of storytelling. And it exposes a gap in how we usually talk about “fiction-first” design: the framework assumes individual protagonists, but fiction primacy works just as well for factions, treaties, and trade routes.

Why the Rules Stay Visible (And Why That’s Intentional)

If you’ve read the earlier essays on the Transparency Threshold, you know it’s the invisible line where you have to stop thinking about the story and start thinking about the mechanics to keep play moving.

OSG sits firmly above that line.

Every turn requires you to format your move into a structured submission (Action / Expected Outcome / Fictional Leverage). You read private briefs. You track objectives. You wait for the “Report” to see how the world reacted. You’re constantly juggling strategy and story.

But this isn’t “rules bloat.” It’s load-bearing architecture.

In a character-driven game, thin rules keep you inside the fiction. In a faction-driven game, structured rules create the information asymmetry, strategic tension, and diplomatic friction that make the fiction interesting. Remove the submission format and the private briefs, and you don’t get a purer story game. You get unstructured collaborative writing. The mechanics aren’t getting in the way of the fiction. They’re building the stage it performs on.

Winning Without Breaking the Story

Traditional fiction engines don’t have win conditions. The story moves because consequences ripple forward, not because you’re checking off objectives. Momentum is the point.

OSG introduces competitive goals. You’re literally playing to win. And at first glance, that seems like it would distort the fiction into a spreadsheet exercise. But OSG proves the opposite: objectives can drive fiction forward, provided the resolution stays fictional.

Your faction’s goals shape every move you make. Those moves produce real consequences for everyone else. The competition creates pressure. The fiction provides the medium. The two aren’t in tension; they’re locked together. The game’s core instruction says it best: “Play to win. Play to find out. Both at once.”

This reveals something the original framework didn’t address: a game can have a winner and still be deeply story-first, as long as competition is resolved through fictional means rather than mechanical calculation.

The Power of Not Knowing Everything

In most TTRPGs, the fiction is fully shared. When the GM describes a scene, everyone hears it. When a character acts, it’s public. The table holds the same reality.

OSG breaks that assumption deliberately. You receive a private Brief with intel no one else sees. You submit actions secretly. The Referee publishes a “Report” that tells you what happened, but deliberately leaves gaps. You know your faction’s debt situation. Your rival doesn’t know you know.

The fiction is layered. It’s partially opaque. And that opacity is the whole point.

Intelligence, deception, misdirection, and diplomatic maneuvering only work when players don’t share the same version of reality. The public Report and the private Brief are two halves of the same story. The gap between them is where the drama lives. The framework assumed a fully shared imagined space. OSG proves that a fiction can be primary, deeply collaborative, and strategically compelling while remaining asymmetric.

The GM’s New Best Friend: The RAT Checklist

Of everything in this design space, one tool deserves to be stolen by every GM, referee, and solo player: The RAT Checklist.

It’s a three-question filter for any ruling, oracle result, or narrative outcome. Before you accept it, ask:

• Reasonable: Does this fit what we’ve already established? Is it proportionate to the situation, or does it bend the world to fit a dice roll?

• Actionable: Does this give someone something to respond to? Or does it cleanly resolve a thread and leave the table with nowhere to go next?

• Traceable: Can you point to earlier decisions or established facts that led here? Or did this feel like it dropped from the sky?

If an outcome fails any of these, rewrite it.

This checklist takes the vague advice of “keep the story moving” and turns it into a practical quality-control step. Reasonable grounds you in the present. Traceable connects you to the past. Actionable pushes you into the future. It’s the most exportable piece of design from OSG, and it works in any fiction-forward game, from D&D to solo journals to narrative indies.

Knowing Where the Map Ends

OSG isn’t a Fiction Engine by the strict definition. The rules stay visible. The subject is collective. The game has winning conditions. The fiction is deliberately incomplete.

But it shares the core commitment: every procedure exists to serve the fiction, not replace it.

It proves that “story-first” isn’t a single paradigm. It’s a principle that can wear different clothes. Sometimes it looks like a lone ranger rolling a d6. Sometimes it looks like a republic negotiating a treaty while hiding its true intentions behind a carefully worded public bulletin.

Knowing where one design region ends isn’t a failure of the map. It’s how you understand what the map actually covers. The next time you sit down to play, ask yourself: Are we living inside the story, or are we steering it from above?

There’s no wrong answer. But knowing which side of the line you’re on will change how you read the rules, how you frame your choices, and what kind of story you’ll actually get to tell.

Hey everyone,

We’ve made it to the usual summer update post!

A lot has happened since the September 8th post where I announced the release schedule for the Geared Towards Loner 2026 lineup.

These nine months have flown by, and I haven’t been able to fully keep to everything I promised, so let me try to bring some order to things and clarify what’s actually on the way.

The elephant in the room: Loner 4e

One of the most surprising things about my journey as a game designer has been how naturally so many editions of Loner have followed one another in such a short time. From the outside this might look like chasing audience trends, but the reality is quite the opposite: both the 3e and the 4e grew out of requests for clarification and framework development from the playing community. And that makes me genuinely proud of my work as Loner’s designer. You all know it was never conceived as a closed system: it’s been open in license and hackable since its very first incarnation. Obviously I haven’t accepted everything uncritically. I have an authorial vision (or more precisely, a conceptual framework) for what does and doesn’t make sense within Loner’s rules framework, and some of those things are non-negotiable. Conceding them would turn the game into something fundamentally different from what it is.

But I do try to take all the feedback from players seriously, and this upcoming edition is also the fruit of that ongoing conversation with the community. It all started with a single question (”how do I introduce Ironsworn’s Momentum into Loner?”) that set off a chain of reflections about what Loner was and wasn’t doing. On one hand, this let me conceptualize the Fiction Engine Framework; on the other, it helped me fill in some gaps left by previous editions’ design. So the design question on the table wasn’t “how do I implement Momentum in Loner,” but rather “what does Momentum represent in Ironsworn, and how can I design something that delivers the same value in Loner?” It sounds like a subtle distinction, but from my perspective it’s fundamental: it’s the difference between a ruleset that’s coherent with a clear intention and a Frankenstein monster stapled together with paperclips.

In the end, as you’ve seen in the dedicated series here on Zotiquest, the 4e essentially brings:

1. Text cleanup and clarifications

2. Making explicit procedures that were previously left implicit

3. Pacing procedures and rules that many players felt were missing

This has required considerable rewriting effort, which is still ongoing (though nearly finished), helped enormously by the feedback I’m getting through the Open Beta. If you read the draft two or three weeks ago, you’ll notice how substantially it’s been revised since then. And if you haven’t looked yet, I’d encourage you to check it out.

I’m planning to publish the Loner 4e core set in late summer/early autumn (sooner, if I manage to sprint through the typesetting). It will fully replace the current edition, and anyone who purchased the previous edition digitally will automatically receive the update. This applies to those who purchased the old Loner Complete (2e) as well.

As with previous editions, all four volumes (Core Rules, Companion, Character/World Builder’s Guide) will be available on DriveThruRPG as PWYW. A new edition doesn’t mean a new commercial policy.

And as a final step, I’ll also update the website and the web SRD, though that’s a lower priority for now.

Geared Towards Loner 2026

As I mentioned, more than nine months have passed since the famous survey, and I’ve realized I muddled the lineup that came out of it a bit, but I intend to fix that. Here are the upcoming Geared Towards Loner titles:

• Cthulhu, Jun. 26

• Rocketpunk, Jul. 28

• Prime Time Hero, Sep. 4

• Slice of Life, Sep. 30

• Ragnarok, Oct. 30

• Teen Drama, Nov. 27

• [Undisclosed Title], Dec. 17

“Hey, what happened to Grand Strategy?” It doesn’t work. After four rewrites and a lot of playtesting I’ve concluded that Loner wasn’t the right foundation for that kind of game. You have two excellent alternatives I designed over the past months: Contested Ground (solo mode) and Breaking Point (which I’m very happy with). And you know what’s even better? They’re both free.

“Wait, weren’t you going to do a Narrative Bundle?” Yes, I announced that... but the way the various games transformed during revision, bundling them together no longer makes sense. I’ll confess the original concept was “how do I play Life is Strange with Loner?” I’d identified three components (Time Loop/Leap, Teen Drama, and Slice of Life) and split them into three standalone but mixable games. Which you can still absolutely do (especially The Path Not Taken, which works with any Loner game), but I’m no longer convinced a bundle adds real value.

Geared Towards Loner 2027

The big challenge for next year will be delivering the ambitious Horror Compendium: five standalone GTL games that together will form a larger volume. The drafts are ready; there’s still work to do. In autumn I’ll open an open beta, and you’ll start seeing the first results of a design effort that’s been going on for over a year.

But that’s not all. Here are the other titles in the pipeline:

• Celtic Fantasy

• Wuxia

• Weird West

• Stone & Spirit (Stone Age)

• The Dreaming (Jungian Dreamwalkers)

There’ll be a survey to help determine their priority order.

Ensemble 2e and the Tuned for Ensemble games

Working so intensively on Loner 4e made it natural to want to align its group-play counterpart, Ensemble. The first edition was already a significant improvement over the original Italian version, but I felt it was still more a design philosophy treatise than an actual rulebook. I rewrote it from scratch, building a useful parallel structure with Loner 4e and importing the components that translate well to group play.

Ensemble 2e will consist of a Core Rules volume and a compilable SRD (or, if you prefer, a Creator’s Kit). And I already have drafts ready for four companion games:

• Wayfarers of Eldoria — a full development of Ensemble Core’s example setting. For anyone who wants to dive into “classic” fantasy.

• Hideout & Heartbeats — kids on bikes, the ‘80s, mysterious events... we’re going back to Clearview!

• Dino Breach — the illegitimate child of Jurassic Park and Dino Crisis.

• Reverie Unbound — Final Fantasy, but as a Fiction Engine rather than a paper JRPG.

The ETA is very uncertain. I’d like Ensemble 2e to release alongside Loner 4e in autumn. The four companion games... that remains to be seen. The schedule is packed as it is, and another piece is joining it soon (see below). In the meantime, I’m asking for your priority preferences in the survey below.

And finally: a new path

Next Friday I’ll be announcing the real new addition to the Loner ecosystem. It’s an experimental publication format, and designing it has given me a lot of satisfaction. Will it land? That depends entirely on how you receive it. Stay tuned.

There’s a moment in every sprawling creative project when you look up from the individual pieces and realize they’re already telling the same story, you just hadn’t noticed yet.

That happened to me in the last months, and I want to take you through it properly. Not as a victory lap, but as an honest account of what the work actually looked like: the embarrassing parts, the accidental continuity, the dead game I refused to bury, and the design question I think I finally answered correctly.

Discover The Five Galaxies!

The Piece I Couldn’t Let Go

Let me start with Plerion.

I deprecated it years ago. Pulled it off the market. The setting was good, genuinely, I still think the Five Galaxies setting I built for it is solid, but the game itself didn’t work the way I needed it to. Plerion was built on Cairn, which is a clean OSR descendant that does dungeon-fantasy exploration beautifully. The problem: I kept forcing it into space opera. And it kept fighting back.

OSR design logic has mortality and attrition baked in at a structural level. That’s perfect for a dungeon. It’s deeply strange for science fiction, where the genre’s tone doesn’t typically hinge on “you opened the wrong door and the space-beast crits you dead.” I built an entire Book of Cosmic Creatures, a hundred-odd space monsters, and every time I ran the game, it felt like D&D with a coat of chrome paint. I’m a Jack Vance reader. Jack Vance doesn’t do that. Mass Effect doesn’t do that. Space opera is about scale, politics, competing interests, strange cultures. It’s not about the things in the next room trying to kill you before you reach the treasure.

So I shelved it. Kept the setting in a drawer. Moved on.

What I couldn’t move on from was those Five Galaxies.

The Setting That Was Already There

The Five Galaxies is an umbrella setting I originally wrote for Plerion and then ignored for years. The premise: it’s the year 7,396 CE. Five galaxies of the Local Group, the Milky Way, Andromeda, Triangulum, the Large Magellanic Cloud, the Small Magellanic Cloud, are connected by the Wormhole Access Network, a system of artificial bidirectional wormholes whose nodes are owned, operated, and controlled by whoever has the political and military muscle to hold them.

Humans exist in this universe. The Terran Compact governs a narrow strip of Orion’s Arm. Outside that margin, human colonies are independent stations, struggling outposts, or communities absorbed into larger polities. Humanity is not the dominant species, not the most ancient, not particularly important in the grand scheme. There are six major species: the Lynem, Che-esune, Tesu, Wrulisu, Omale, and Hetsu. Extinct civilizations have left ruins in four galaxies.

In the version I originally published, this was all written encyclopedically, accurate, well-crafted, and about as interesting to read as a policy brief. The setting had everything: political tension, resource conflicts, alien cultures with genuine internal fractures, a travel system with real friction built in. What it didn’t have was a game that could carry it.

The Line That Connected Everything

Here’s where the accident of continuity happened.

While I was revising, I kept finding one sentence that I apparently wrote years ago and then forgot: the Terran Compact “governs a fraction of Orion’s Arm in the Milky Way.” That’s it. A throwaway line of worldbuilding that I included for scale, to signal how marginal humanity is relative to the broader Five Galaxies setting.

Except that line describes exactly where the Terra Beyond trilogy ends up.

Sol: Beyond Earth is set in 2090 CE. The solar system has just reached 200,000 people living off-Earth. The Federated Autonomy Treaty has created the Sol Union. The technology is hard SF: fusion rockets, O’Neill cylinders, Hohmann transfers calculated by onboard computers, orbital mechanics as a genuine constraint rather than background flavor. It’s retrofuturistic NASA aesthetics, the 1970s vision of where we’d be by now, delayed and scaled up.

Frontier: Beyond Sol, set around 2400 CE, has humanity across 85 star systems, the Sol Union controlling half the jumpgates, and the discovery of alien ruins reshaping everything politically and culturally. The game is inspired by the Terran Trade Authority aesthetic: gritty interstellar logistics, politics shaped by gate control, the gap between core systems and frontier worlds that want nothing to do with core governance.

Orion: Beyond the Frontier, the third game that I had never quite finished, is set around 4000 CE. By then, Orion’s Arm is a patchwork of post-scarcity core worlds, rugged frontier colonies, rogue AI collectives, and the Zynthari, an alien civilization with technology built on spacetime manipulation that makes everything humanity has achieved look provincial. Psionics are documented, real, and employed by every major military intelligence apparatus. Precursor ruins have been partially translated. Humanity is, to quote the setting’s own phrasing, “a major but not supreme power in Orion’s Arm.”

A major but not supreme power in Orion’s Arm. Governing a fraction of Orion’s Arm. The same sentence, written from 3,396 years apart. I hadn’t planned that. I don’t think I consciously knew those two settings were the same setting until this year.

Building the Spine

Once I saw the continuity, the rest was editorial work rather than creative work. The timeline from the Terra Beyond trilogy already established that by 4000 CE, humanity has encountered the Zynthari and accepted the Rim Concord, a limitation on expansion. The Five Galaxies, set 3,396 years later, references the Precursor ruins in Orion’s Arm that multiple powers are still studying. The Terran Compact, humanity’s polity by 7,396 CE, is operating under the legacy constraints of that Rim Concord, which explains why humans remain local while alien empires span multiple galaxies.

The complete timeline now runs like this:

• 2090 CE — Sol: Beyond Earth. Hard SF. Solar system scale. The Age of Settlement becoming the Age of Expansion.

• ~2400 CE — Frontier: Beyond Sol. Interstellar. 85 systems. The jump to space opera begins here.

• ~4000 CE — Orion: Beyond the Frontier. Orion’s Arm scale. First major alien contact. Humanity powerful but not supreme.

• 7,396 CE — The Five Galaxies. Full space opera. Five connected galaxies. Humanity marginal in a civilization of six major species.

The three Terra Beyond games are a continuous future history. The Five Galaxies is what that history looks like from the far end. They don’t need to know about each other to work, the games are separated by enough time and scale to be entirely self-contained, but the internal logic is coherent across all of them.

Why 24XX and Not Cairn

The other half of this year’s work was deciding what game system to use for the Five Galaxies material, and being honest about why the previous answer was wrong.

I keep saying that you can’t do everything with one system. This is a lesson I have apparently needed to learn several times. Cairn does dungeon fantasy well. When I built Plerion on it, I was riding the wave of “OSR for everything” enthusiasm that swept through indie TTRPG design for several years, the assumption that if a system is open and light, you can transpose it into any genre. The transposition doesn’t work, because the design logic is embedded at a level below the surface aesthetic. OSR systems assume a certain relationship between risk, mortality, and resource attrition. That relationship fits dungeon fantasy. It fights science fiction at every turn.

24XX, the system by Jason Tocci, is technically OSR-descended in its lineage but operates on a fundamentally different model in practice. It’s fiction-first, episodic, built around jobs with defined scopes. The party takes a job, executes it across three to five scenes, collects pay, advances, and asks what comes next. The pressure systems, debt, Heat, Notoriety, fuel state, exist as background that surfaces when the fiction demands it, not as tables to process between sessions. It’s designed for exactly the kind of play space opera actually needs: situations already in motion, competing interests, operators doing work for patrons whose real agendas are never fully disclosed.

74XX Oddspace is the Five Galaxies game built on that chassis. The same core structure, roll a skill die, higher with a relevant skill, lower when hindered, take the highest, runs through all the 74XX games. The setting material, the oracles, the faction systems, the travel pressure all sit on top of a rules layer simple enough to disappear when the fiction is working.

The Terra Beyond trilogy games share the same underlying rules approach, tuned differently for each period. Sol is tightest, orbital mechanics as an actual constraint, resource management foregrounded, the solar system’s physical reality treated as the primary source of pressure. Frontier opens it up, jumpgates change the scale, the political fragmentation of interstellar expansion becomes the source of friction. Orion is the widest version, alien contact, Precursor archaeology, factional politics across hundreds of systems, psionics as documented phenomenon. Each game uses more or less the same procedures, calibrated to the scale and tone of its period.

What This Is and Isn’t

Let me be precise about what I’ve actually built, because the scope is easy to misread.

The Terra Beyond trilogy and the Five Galaxies setting are thematically distinct. The Terra Beyond games are about humanity’s expansion, the politics of who controls the gates, what we owe the civilizations we encounter, what counts as human when bodies and minds can be modified or uploaded. They’re grounded, even in Orion, in a recognizably human political drama.

The Five Galaxies is not that. It’s full space opera, deliberately exaggerated, designed for play at a scale where humans are one minor polity among dozens, where alien empires have been running for tens of thousands of years, where you can play a Lynem noble house operative or a Wrulisu caravan pilot or a Hetsu clan surveyor and the human characters are the exotic ones. Six thousand years of future history sits between Orion and the Five Galaxies. A lot changes in six thousand years.

What unifies them is the background continuity: a consistent physical universe, a coherent account of how humanity got from here to there, and the same Orion’s Arm that appears first as the entirety of human space and later as a small provincial corner of a much larger civilization.

That’s enough. It doesn’t need to be more than that.

The 74XX Family

A brief note on what else lives in this space. The Five Galaxies is the umbrella for all the 74XX games. Oddspace is the main game. Space Cadets is another. There are a couple of one-pages. There’s a trading sim I’d hesitate to call a TTRPG because there’s no roleplaying in it, it’s a paper-and-pencil Elite, pure procedure for trading across systems, resources and routes and margins.

The Terra Beyond trilogy is its own axis: Sol, Frontier, Orion, a future history in three games, each one a step further from Earth in time and distance and genre convention.

And Sector Seven remains separate from all of this. Different universe, different rules. Not everything needs to connect.

The full revised files are in progress. I’ll be sharing them through the usual channels as they’re finalized. In the meantime: if you’ve been following the Terra Beyond trilogy or keeping an eye on the Five Galaxies material, you’ll notice the continuity when you read both. I didn’t plan it, but I’m glad it’s there.

Six thousand years is a long time. It turns out I’ve been writing it for a while.

This piece adapts concepts from the Fiction Engine Framework and companion essays. Original analysis of Freeform Universal (Nathan Russell / Peril Planet), 24XX, Breathless, and Hints and Hijinx appears in “Four Designs, One Framework.” Written for players and GMs navigating the modern TTRPG landscape.

If you’ve browsed the TTRPG scene lately, you’ve seen the label everywhere: rules-light, fiction-first, narrative. It sounds like a promise. Less crunch, more story. Just talk, roll, and go.

But here’s the thing: pick up four games all tagged “rules-light” (say, Freeform Universal, 24XX, Breathless, and Hints and Hijinx), and play them back-to-back. They don’t feel the same. Not even close.

One feels like pure improvisation. Another feels like you’re managing a resource dashboard. A third asks you to solve a puzzle. A fourth suddenly shifts gears halfway through.

Same label. Different experiences.

The problem isn’t the games. It’s the label. “Rules-light” tells you how many rules a game has. It doesn’t tell you what those rules do, where your attention goes, or what kind of play you’re actually signing up for.

Let’s fix that.

Two Questions That Matter More Than Rule Count

Instead of asking “how many rules?”, try these:

1. What does each rule actually do? Does it create a new story moment? Support the conditions for play? Or just add busywork?

2. Does the rule operate in the background, or does it demand your conscious attention to move forward?

These two questions reveal why two “rules-light” games can feel worlds apart. One might have fewer rules but ask you to constantly classify your actions into mechanical categories. Another might have more moving parts but let you stay inside the fiction the whole time.

It’s not about quantity. It’s about function and attention.

Meet the Four Games (And Why They’re Not the Same Family)

All four games are slim, solo-friendly, and fiction-forward. But they make very different tradeoffs. Here’s the layman’s tour.

🟢 24XX: The Pure Baseline

Where it comes from: OSR / FKR minimalism, pushed to its logical extreme.

How it plays: You describe what your character does. The GM asks: is this risky? If yes, roll. Three outcomes: something goes wrong, it partially works, or it succeeds. Then you keep going.

Why it feels transparent: No action categories to sort into. No move list to consult. No resource pool to manage. The procedure is so thin it becomes muscle memory fast. You’re not thinking about the rules; you’re thinking about the heist.

The tradeoff: It gives you almost no built-in pacing, genre texture, or structural support. If your table needs the system to create momentum, 24XX won’t do that for you. That’s not a bug. It’s the price of purity.

Best for: Tables that want maximum fiction, minimum mediation. Solo players who don’t want to juggle subsystems.

🟡 Freeform Universal: The Flexible Ancestor

Where it comes from: The narrative indie tradition that helped define “fiction-first.”

How it plays: Describe your action, roll a d6, interpret the result on a simple six-point scale (from “yes, and” to “no, and”). Keep going.

What makes it special: Your character isn’t a stat block. They’re a handful of fictional descriptors: grizzled, quick with a lie, haunted by the old war. Gear works the same way. Conditions like injured or trapped are both mechanical penalties and fictional facts. One statement does double duty.

The variable element: FU Points. A light metacurrency you earn for cool roleplay and spend for bonus dice. Optional by design. Turn them off, and FU sits as low as 24XX. Use them heavily, and you introduce a light resource-management layer.

Best for: Groups that want a dial they can adjust. Tables that value collaborative storytelling with just enough structure to keep uncertainty meaningful.

🔶 Breathless: The Pressure Engine

Where it comes from: A direct hack of 24XX, but with a different goal.

How it plays: Same clean core: describe, roll if risky, interpret. But now every roll degrades the die you used. Your d10 becomes a d8, then a d6. You’re getting tired. Resources are depleting.

The elegant part: To reset your dice, you ask to “catch your breath.” The GM immediately introduces a complication. You can’t restore your resources without the fiction changing. Mechanical action and fictional consequence are locked together.

Where it crosses the line: Breathless adds a stress track, a loot die, and an inventory limit. Each rule is justified. Together, they ask you to track multiple degrading resources while staying in the fiction. That combined attentional load pushes the game above the transparency threshold.

Why that’s intentional: Breathless isn’t trying to disappear. It’s trying to create tension. The pressure of depleting dice, the risk of pushing too far, the tough choice of when to rest — that’s the experience. The tracking isn’t overhead. It’s the point.

Best for: Players who want strategic tension and a tension-and-release loop. Solo players who enjoy resource management as part of the drama.

🔴 Hints and Hijinx: When Genre Forces a Crossing

Where it comes from: A Breathless hack built for mystery investigation.

How it plays (Part 1 — Investigation): Same as Breathless. Describe, roll, degrade, reset with complications. Clean and transparent.

How it plays (Part 2 — Deduction): Now you switch modes. You’ve been collecting clues as a count. You spend them to build a die rating for your final hypothesis. The more clues you’ve gathered, the better your chance of being right.

Why it crosses the threshold: Clues aren’t fictional states. They’re tokens you track and spend. The deduction phase asks you to manage a metacurrency economy. That’s a different paradigm.

Why it’s not a flaw: Mysteries have structural needs. They require accumulation, synthesis, and stakes at the moment of revelation. A pure fiction engine can’t reliably produce the sense that “enough evidence has been gathered.” The clue economy solves that. The game crosses the threshold deliberately, at a specific moment, for a genre reason.

Best for: Mystery fans who want the satisfaction of assembling evidence and making a big, consequential deduction.

The Solo Player’s Reality Check

Three of these four games are solo-capable. That matters.

In a group, procedural weight gets distributed. The GM holds the move list. An experienced player smooths transitions. The table shares the cognitive load.

Solo? You carry it all.

That means the transparency threshold is effectively lower for solo design. A tracking system that feels light with four people can feel heavy when you’re alone. A classification step that a group internalizes together becomes your sole responsibility.

This is why ultra-thin designs like 24XX are so popular in solo spaces. Not because they’re “better.” Because one person can carry them without the procedure drowning out the fiction.

If you’re playing solo, ask: Can I hold all of this in my head while also imagining the story? If the answer is no, the game might be rules-light on paper but procedurally heavy in practice.

So… Which One Should You Play?

None of these games is “best.” They’re optimized for different things.

The real takeaway isn’t which game to pick. It’s learning to read past the label.

Next time you see “rules-light,” ask:

• What do the rules actually do?

• Where does my attention go when I play?

• Is the procedure serving the fiction, or am I serving the procedure?

The answers will tell you more about the experience than any tag ever could.

After the previous issue, I realized there’s a second layer to the problem that is worth unpacking. It sits underneath the mechanical discussion, and it has more to do with how we talk about play than with any specific system.

It comes up every time someone says “fiction first” and means something slightly different.

So let me state it as clearly as I can.

Fiction first does not mean improvising everything.

It does not mean showing up with nothing and building the story moment by moment based only on player input. That is a possible play style, and a valid one, but it is not what fiction first means.

Fiction first is about priority, not absence of preparation.

What I Actually Prepare

When I prep a campaign, I do not write a plot.

But I absolutely prepare.

I know what the situation is. I know what different actors want. I know how they are likely to behave if nothing interferes. I have a baseline mission structure, even if it is loose. I have a sense of tone, constraints, and internal logic.

That preparation is what allows the world to respond in a way that feels consistent.

If you remove that layer entirely, the world stops being consequential. Reactions become arbitrary. Things happen because they are convenient in the moment, not because they follow from anything.

That is where the experience breaks for me.

So yes, there is always preparation. There has to be.

Where Fiction First Actually Happens

The “fiction first” part kicks in after play begins.

Players act. They make decisions I did not predict. They ignore hooks, they create new directions, they push into corners I had not considered.

At that point, I do not try to bring them back to a planned sequence. I look at what I prepared and ask a simple question: given this situation, these actors, and these motivations, what happens now?

That is the whole loop.

Prepare a situation. Play. Adjust based on what actually happens.

There is no middle ground where I am half-planning outcomes and half-improvising reactions. The preparation defines the space of possibility. The players determine how that space is explored. My role is to keep the responses coherent.

A concrete example from the current campaign: the group left the expected path early, took a ship, and ended up in a small fishing port that I had not positioned as a major node. That was not planned. There was no branch in my notes for that specific move.

But the setting was prepared well enough that I could still answer: who is here, what do they want, how do they react to outsiders, what tensions already exist?

That is fiction first in practice. Not absence of prep, but flexibility built on top of it.

Why This Gets Misunderstood

Part of the confusion comes from how these ideas have been communicated over time.

Games in the PbtA and Fate space carry a lot of useful design thinking, but they also come with a layer of terminology that is not always transparent in play. The language can be dense, sometimes overly abstract, and often interpreted differently by different tables.

Concepts like “play to find out,” “fiction first,” or “agenda and principles” are doing real work, but they are easy to misread if you approach them as slogans instead of procedures.

The result is a gap between what the design intends and what people actually do at the table.

You end up with players who think fiction first means “the GM should not prepare,” or GMs who think “play to find out” means “I must avoid having any structured situation in mind.”

Then, when the game stalls or feels inconsistent, it is not clear why.

This is not a failure of those games as such, but it is a real accessibility issue. The ideas are powerful, but they are not always communicated in a way that is easy to operationalize.

The Practical Version

If I strip away all the terminology, the way I run fiction-first play is very simple:

• I prepare a situation with actors, goals, and internal logic.

• I do not prepare outcomes or sequences.

• When players act, I resolve what happens based on that preparation.

• I let the situation evolve, even if it moves away from what I initially expected.

That is it.

No ideology, no purity test. Just a clear separation between what is prepared and what is discovered.

Back to the Actual Problem

This ties directly into the issue from the previous session.

My difficulty as a GM right now is not that I do not know how the world should react. That part is working. I can answer questions about the setting, the NPCs, and their behavior without much trouble.

The difficulty appears one layer above that.

When the players engage in low-stakes interaction, like extended conversations with an NPC, I can keep things coherent, but I struggle to make those moments produce consequences that matter.

Not because I cannot invent something, but because there is nothing in the system pushing that interaction toward a change in state.

So we end up with scenes that are consistent but static.

From the player side, it is a natural exchange of information. From my side, it feels like time passing without transformation.

The Temptation to Force Movement

At a certain point, I stepped in and forced the situation forward.

I had the innkeeper push the characters toward the back room, toward the hidden refuge, effectively accelerating the scene. It worked in the sense that it moved things along.

But I was not comfortable with how I got there.

That decision did not come from the fiction alone. It came from me recognizing that the game was stalling and injecting a solution. I took a meta-level need and translated it into an in-fiction action.

That is a tool, and sometimes it is necessary. But it sits in a grey area.

The discomfort comes from the fact that the push was not fully grounded in either preparation or system output. It was a correction.

When that becomes the main way you maintain pacing, something is off.

Where the Two Threads Meet

At this point the connection becomes clearer.

On one side, there is a style of play where the world is prepared and reacts coherently to player input.

On the other side, there is a system that only engages when actions carry explicit risk.

If the players operate in a careful, low-risk mode, the system stays silent. When the system stays silent, all the weight shifts onto the GM to both maintain coherence and generate movement.

Preparation helps with the first part. It does not solve the second.

That is exactly where I am feeling friction.

What I Am Taking From This

There are two takeaways I am carrying forward.

First, I need to be more explicit, both with myself and with the table, about what fiction first actually implies in terms of preparation. Not as a theoretical stance, but as a shared expectation of how the game runs.

Second, I need systems that remain active across different levels of intensity. If a game naturally includes long stretches of careful play, investigation, or social interaction, I want mechanics that can still contribute during those phases.

Otherwise, I am left bridging the gap manually.

And while I can do that, it is not where I do my best work.

The goal is not to remove the GM from the process, but to avoid carrying the entire process alone.

That distinction is easy to blur in discussion, but very obvious at the table.

This piece adapts concepts from the Fiction Engine Framework and companion essays.

If you’ve played enough tabletop RPGs, you’ve probably noticed a weird pattern: two games can both be described as “rules-light” or “story-focused,” but they feel completely different at the table.

In one, you’re just talking, rolling a die, and watching the story unfold. The rules feel invisible. In the other, you’re constantly checking move lists, tracking stress clocks, debating aspects, and managing resource economies. The rules are right there in the foreground, and you have to interact with them to move forward.

Neither experience is wrong. They’re just operating on different sides of an invisible design boundary. Let’s call it the Transparency Threshold.

Understanding where this line sits changes how you pick games, how you run them, and why certain mechanics “click” for some tables but grind to a halt for others.

Plumbing vs. Dashboard: What the Threshold Actually Is

Think of RPG rules as either plumbing or a dashboard.

When rules act like plumbing, they’re background infrastructure. You describe what your character does, the mechanics quietly handle the uncertainty, and everyone stays focused on the fiction. You don’t think about the pipes; you just get clean water.

When rules act like a dashboard, they’re persistent objects of attention. You’re still driving the car, but you’re actively watching gauges, checking warning lights, and managing fuel. The mechanics aren’t just handling uncertainty; they’re generating tension, strategy, or dramatic rhythm.

The Transparency Threshold is the exact point where the game forces your attention to shift from the fiction to the system in order to keep play moving.

Crossing it doesn’t mean a game is “rules-heavy.” It means the game is asking you to look at the dashboard. And that’s a deliberate design choice, not a flaw.

Two Ways Rules Work (and Why Only One Pulls You Out)

Not all mechanics grab your attention the same way. There’s a crucial distinction between:

1. Background Tracking (Abstraction of Form) Hit Points, ammo counts, or fatigue markers are technically non-diegetic (your character doesn’t see a “14 HP” floating above their head). But in practice, they often stay invisible. You don’t think, “I have 8 hit points.” You think, “I’m bleeding badly and need to get behind cover.” The number does its job in the background.

2. Procedural Translation (Abstraction of Procedure) This is where the threshold gets crossed. Games like Powered by the Apocalypse require you to pause and classify your fictional action into a predefined category: “Is this Acting Under Fire? Defying Danger? Going Aggro?” You can’t just say what your character does and roll. You have to match your intent to a mechanical trigger first. That split-second translation step pulls you out of the fiction and into the rules. It’s necessary for the game to function, but it’s undeniably foregrounded.

A Quick Map of Where Popular Games Sit

Using this lens, we can place familiar design paradigms without ranking them. They just create different experiences:

🟢 Below the Threshold: Freeform Universal, Loner, 24XX, many OSR games. You describe an action, roll if it’s risky, interpret the result, and keep going. There’s no classification step. The mechanics become muscle memory fast, and attention stays on the fiction.

🟡 At the Threshold: Powered by the Apocalypse. Fiction triggers the mechanics, but you must identify the correct Move before the fiction can advance. New players feel the speed bump. Veterans internalize the taxonomy, and it fades into the background. But structurally, it’s always there.

🔴 Above the Threshold: Blades in the Dark (FitD) & Fate. These games want you looking at the dashboard. Position & Effect, stress, clocks, aspects, fate points—they’re designed to be visible. Managing them is the core experience. In Blades, the tension comes from watching the stress track fill. In Fate, the fun is in the collaborative negotiation of narrative leverage. The fiction doesn’t flow through invisible pipes; it flows through conscious mechanical choices.

The “Practice Effect” (Why the Threshold Moves)

Here’s the twist: the threshold isn’t fixed. It’s player-variable.

A beginner hitting Apocalypse World for the first time will feel every Move trigger. A veteran who’s run it for two years barely notices it. The classification step has become habitual, and habitual steps don’t demand conscious attention.

This has three major implications:

1. Learning Curve vs. Permanent Friction: Some games feel “rules-heavy” at first but become transparent with play. That’s not a design failure; it’s an amortized learning cost.

2. How You Teach Matters: If you introduce a game by listing stats and move triggers, it will feel procedural. If you drop players into a situation and let the rules emerge from fiction, it will feel fluid. Same game, different threshold experience.

3. The Solo Player’s Burden: In a group, the GM or experienced players absorb procedural weight. They hold the taxonomy, manage clocks, and smooth transitions. Solo? You carry it all. A tracking system that feels light in a group can feel heavy when you’re alone. This is why games with ultra-thin rules are so popular in the solo space.

Good Mechanics Can Still Be Heavy

Just because a rule sits above the threshold doesn’t mean it’s bad. In fact, some of the most beloved mechanics are highly visible by design.

Blades in the Dark’s clocks are brilliant. They create pacing and tension. But they demand attention. A rule can be load-bearing (essential to the fun) and still push the game above the transparency line.

The real design trap isn’t bad rules. It’s accidental accumulation. You add a stress track for tension, a clock for pacing, a metacurrency for drama, a position/effect matrix for clarity. Individually, each is justified. Collectively, they shift the table’s focus from the story to the system without anyone deciding to cross the line. The game didn’t break; it just drifted into a different paradigm.

The Takeaway: Pick the Right Tool for the Table

This framework isn’t about declaring one style “better.” It’s about intentionality.

• If you want fluid, improvisational storytelling where mechanics stay out of the way, look for designs that sit below the threshold.

• If you want strategic tension, dramatic rhythm, or explicit collaborative authorship, look for designs that sit above it.

• If you’re playing solo, lean toward thinner procedural layers unless you enjoy dashboard management as part of the solo experience.

The best games know exactly where they sit and lean into it without apology. The best tables know what they want for the night and pick accordingly.

Next time you sit down to play, ask yourself: Are we talking about the story, or are we talking about the rules? There’s no wrong answer. But knowing why you’re on one side of the line or the other will save you mismatched expectations, frustrated players, and a lot of mid-session rulebook flipping.

The rules are just the engine. Decide whether you want it hidden under the hood, or mounted on the dashboard where you can watch it work.

The Companion started as a handbook. It was a friendly explainer, the kind of thing you write when people keep asking “but why does it work this way?” And for what it was, it did its job. But going into 4e, I realized it had a problem: it was still talking to a reader, not a player. That distance showed up everywhere, in the tone, the structure, and most painfully, in what it left out.

So when it came time to revise it for 4e, I didn’t patch it. I rewrote it section by section, asking each time: what does someone actually need to know here, and are we telling them that?

Here’s what changed.

The Introduction Got a Purpose

The 2024 introduction was a bit of a memoir. It told the story of how Loner came to be, which is charming but not what someone holding the Companion actually needs. I moved that history to Appendix A and replaced the intro with something more direct.

The new intro opens with three sections: What This Book Is, Who This Book Is For, and How to Use It. That sounds obvious, but the old version had none of it. You didn’t know whether to read it cover to cover or use it as a reference. You didn’t know what it assumed you already knew.

The new opener also draws a cleaner line between the Core Rules and the Companion. The Core Rules answer how. This book answers why. Once I had that framing, the rest of the restructure followed naturally.

The section on Zahra changed too. She was just mentioned in passing before. Now she’s introduced properly as a thread running through the whole book: the same protagonist from the Core Rules examples, followed across multiple sections so you can see how the same fiction looks from the mechanics angle, the judgment angle, and the character development angle. Beta testers found this much easier to follow than scattered, disconnected examples.

The Philosophy Section Got Teeth

The three core principles (Fiction First, Emergent Narrative, Fictional Positioning) were already in the 2024 Companion. But the explanations read like a brochure. Lots of “invites you to” and “lets the story grow.” Not much how or why it matters when things get hard.

The 4e versions are more concrete. Fiction First now explains that tags replace stats because the question you’re asking is “does this make sense for who this character is?”, not “do I have the right number.” The tag is not a bonus; it’s a claim about the fiction. That distinction matters in practice.

Emergent Narrative gets a point that was completely missing before: Loner is procedure-enabled play, not plot-driven play. You start with a character and a situation, and the story comes from what the tools generate, not from a plot you’re moving through. This is what separates Loner from creative writing. You don’t decide what happens, you respond to what the Oracle made true.

Fictional Positioning gets the clearest upgrade. The old version explained the concept fine. The new version adds the practical filter: before asking the Oracle anything, ask whether the action follows from who your character is and what the scene has established. The locksmith example was already there. I added the Grizzled Soldier example to show that it cuts in both directions, tags that open possibilities and tags that close them.

The “Everything is a Character” Section Got Extended

This was one of the more interesting additions. The principle was already in the Companion, but it stopped at “you can stat a ship.” In 4e, we added The Promotion Rule, which gives you a practical test for when to write a character sheet.

The short version: if something matters once, keep it as plain tags. If it keeps showing up, or actively pushes back, promote it to a character and play it by the same rules. Most factions are just world tags until they become an active opponent. Most locations are just atmosphere until they resist, reward, or remember.

I added two worked examples: a biotech conglomerate as an active antagonist with Goals and Nemesis, and a cursed location as a character you can exorcise through conflict, flipping or erasing its hostile tags one oracle success at a time. Both came directly from closed beta play. The faction example in particular was something a tester worked out on their own and then wrote up; I just formalized it.

Scene Structure Got Clarified

A section I’ve seen trip people up in every edition. The 2024 Companion gave you good advice about scene purpose and the 5W+H framework, but it didn’t connect that advice to the formal procedures in the Core Rules.

The 4e version adds a section called Establishing the Scene Before You Roll, which explains those three questions the Core Rules ask (Where/Who/What) in terms of when and why they matter. The key observation, which came out of beta feedback, is that players skip the setup most often mid-campaign, when the next scene feels like it should just follow automatically. It rarely does. If you don’t know what a Yes would even look like, the Oracle’s answer means nothing.

I also added a note about tracking what your protagonist knows versus what’s actually true. That gap between assumed and actual is usually where the best oracle question lives.

The transition to the next scene got updated too. The old text said “think about where the story leads next.” The new text names the Scene Transition roll explicitly and ties it to the three scene types: dramatic, quiet, and Meanwhile. Each type now has a procedural description, not just a mood label.

The Oracle Got a Section It Was Missing

The most significant structural addition in the mechanics chapter. The 2024 Companion explained the dice mechanics clearly. What it didn’t do was explain what the Oracle is for.

So I added What the Oracle Actually Does: the Oracle doesn’t tell you what happens. It tells you whether what you hoped would happen did happen, and at what cost. If you already know the answer before you roll, the roll is theater. The Oracle only does its work when the outcome matters and surprises you.

The four result tones get a reframe too: emotional weights. A “Yes, but” is uneasy success. A “No, and” is collapse with consequences. Each result asks you to inhabit the character’s position, not just update the game state.

I also added When the Oracle Keeps Saying No: something beta testers asked for repeatedly. A single No is a roadblock. Three or more consecutive No results are a pattern. The section tells you to step back and ask what the story is telling you, rather than treating each roll in isolation. And it connects directly to the Dead Ends procedure in the Core Rules, which is what you reach for when a line of inquiry collapses entirely.

Character Development Got a Full Treatment

This was almost entirely rewritten. The 2024 version described the idea of evolving tags, but treated it as one option among several. The 4e version puts it at the center and explains the mechanism clearly.

Tags are claims about what is currently true in the fiction. Fiction changes. Tags change with it. That’s the whole system.

I added four new sections here:

• Condition Tags Come and Go: conditions are temporary by design. Remove one when the fiction no longer supports it. No roll required; ask whether the fictional state has changed.

• Character Growth Emerges from Play: the Core Rules allow you to add, modify, or remove tags after an adventure. This section explains what that means in practice, noticing when the fiction has made an old tag obsolete, and when a new one has been earned.

• Tags as Beliefs, Not Stats: the mechanism of character development in Loner arrives quietly. You reach a moment where you look at a tag and realize it no longer describes what is true. The section traces how this happens: scenes create pressure, pressure bends tags, eventually the drift becomes visible.

• What to Ask After Each Adventure: three questions to run through before touching the character sheet.

The Zahra examples here are specific: her Shadow Walker tag becoming obsolete after three sessions in broad daylight; Afraid of Confined Spaces softening to Tense in Tight Quarters. Specific examples outperform abstract advice by a wide margin in playtesting, so I leaned into them.

NPCs Between Scenes (New)

A small addition, but one that came up constantly in the closed beta: what are NPCs doing while you’re not in a scene with them?

The Meanwhile rule handles antagonists: the story cuts away to show the opposition advancing. But allies, contacts, and wildcards have no equivalent. I added a short section explaining the simplest approach: when a tracked NPC hasn’t appeared for a session or two, ask one Oracle question about their current state before the next scene begins. Not “what did they do in precise detail”, just “Is Tobias still in the city?” or “Has the Naturalist Order made a move while I was gone?” A Yes or No with modifiers is enough.

The section also points out that a Loyal Informant tag is a claim, not a guarantee. If the story has moved significantly since you last checked in, that loyalty may have been strained or deepened. Either outcome is more interesting than unchanged.

The “Towards Open Beta” Bit

Most of the structural changes above came from three recurring types of feedback in the closed beta:

1. People understood the mechanics but couldn’t connect them to the “why” behind the design.

2. People handled individual scenes fine but lost the thread across multiple sessions.

3. People weren’t sure when to update their character sheets.

All three of those gaps are addressed directly in the 4e Companion. Whether we’ve closed them completely is what the open beta will tell us. The Companion is more opinionated now, more willing to say “here is specifically what this means and when it applies.” That’s a bet. Some players will push back on it. That’s fine: I’d rather get pushback on something specific than silence about something vague.

I’ve been running a play-by-chat campaign set in Marethar, and over the past couple of weeks I hit a kind of stall that didn’t look like a stall at first.

The players were engaged. The fiction was coherent. The tone was exactly what we wanted. Careful, low-profile infiltration in a coastal village. Slow conversations, probing questions, testing allegiances. No chaos, no loud moves, no unnecessary exposure.

Everything was working.

And yet I found myself increasingly stuck behind the screen.

Not because I didn’t know what could happen next, but because I had no support in deciding how things should evolve. I was resolving more and more of the fiction by pure judgment, without the usual back-and-forth with the system. That started to feel heavy very quickly.

The root of it, as it turns out, is not pacing, not player passivity, and not even the specific scenario. It’s the interaction between this style of play and a very specific design choice in 24XX.

Risk as the Only Trigger

24XX is built on a clean idea: you roll only when there is risk.

Not uncertainty. Not difficulty. Risk.

If an action is plausible and there is no meaningful downside, it just happens. No roll, no friction, no noise. This removes a lot of unnecessary dice checks and keeps the focus on meaningful moments.

In isolation, I still think this is a strong design decision.

The issue shows up when you look at what happens in extended stretches of play where the characters are actively trying to avoid risk. Infiltration is the clearest example. If the players are doing their job well, they are constantly steering away from anything that could blow up in their face.

They gather information. They test boundaries. They move slowly and deliberately. They choose the safe approach whenever possible.

And the system agrees with them.

No risk means no roll.

What Happens When You Don’t Roll

In our current situation, the group has been operating out of a fishing village, establishing contact with what might be a dormant cell of their organization. Most of the play revolves around conversations, observation, and small positioning moves.

All of it makes sense in the fiction. None of it triggers a roll.

After a few days of this, a pattern becomes visible:

• The players propose actions that are careful and plausible

• The system does not engage because there is no risk

• I resolve the outcome directly

• The fiction advances, but only along lines I choose

This is the key point. Without rolls, I lose an external source of input. There is no success with complication, no unexpected failure, no escalation injected by the dice. Everything depends on my judgment in the moment.

I do not enjoy that kind of authority.

I am not interested in steering the story toward a pre-shaped outcome, and I do not want to invent complications just to keep things moving. I rely on system outputs to push back against my own instincts. Dice results are not just resolution tools for me, they are prompts that keep the fiction honest and surprising.

When that layer disappears, I feel like I am carrying the entire structure alone.

The Stall Is Subtle

This does not look like a traditional stall.

Nobody is waiting for something to happen. There is no silence, no confusion, no lack of ideas. The players keep interacting, asking questions, refining their understanding of the situation.

But the state of the fiction does not change in meaningful ways.

No pressure builds. No complications emerge organically. No new problems force decisions.

We stay in a loop of safe actions leading to safe outcomes.

At some point I tried to introduce an external event. A patrol passing nearby, something that could potentially disturb the situation. It is a classic move. You add a new element to shake things up.

But even there, the structure of 24XX holds.

If the players avoid engaging with that patrol in a risky way, there is still no roll. And if there is no roll, there is no mechanical consequence. The event exists, but it does not generate traction on its own.

So the loop continues.

This Is Not a Player Problem

It is important to be clear about this.

The players are doing exactly what the fiction calls for. They are playing competent infiltrators in a hostile environment. Acting cautiously is not only valid, it is the correct approach.

If I need them to take risks in order for the system to function, then the responsibility is on me as a facilitator, or on the choice of system itself. It is not reasonable to expect players to act against their own goals just to keep the mechanics active.

This is where the tension becomes structural.

24XX assumes that risk will be present often enough to keep the resolution cycle alive. If that assumption fails, the system does not offer a fallback.

The Hidden Requirement

After sitting with this for a while, I would phrase it like this:

24XX requires active pressure management from the GM.

The system does not create pressure. It resolves it.

If the situation is already tense, everything works. Climbing a wall under time pressure, slipping past guards, making a desperate call with incomplete information. In those moments, risk is obvious and frequent, and the dice come into play naturally.

If the situation cools down, the system steps back completely.

That means the GM has to do one of two things:

• Continuously introduce elements that create risk

• Accept that parts of the game will run without mechanical support

Both are valid approaches, but they lead to very different experiences.

In my case, I realized I was not comfortable sustaining that level of pressure artificially. It started to feel like I was pushing the fiction instead of discovering it.

Why This Matters for My Style

My approach to running games depends heavily on shared uncertainty.

I like situations where neither I nor the players fully control how things unfold. The system acts as a mediator that introduces friction, surprises, and constraints. It gives me something to react to, not just something to adjudicate.

When that layer is missing, I start second-guessing my own decisions. Am I making things too easy? Too convenient? Too static? Too harsh?

Even when the answers are reasonable, the process feels less grounded.

That is the real cost of long stretches without rolls. Not the absence of failure, but the absence of an external voice in the conversation.

The Decision to Switch

At a certain point I proposed switching the system.

Not because 24XX failed in a general sense, but because it was not supporting the specific kind of play we had drifted into.

The alternative I suggested was Ensemble, mainly because it keeps the resolution layer active even when the fiction is calm. The oracle component produces outcomes that can shift the situation without requiring explicit risk from the characters.

This is the key difference.

In Ensemble, you can ask a question about the fiction and get an answer that moves things forward. You do not need to wait for a risky action to justify a roll. The system participates in quieter moments.

That alone changes the texture of play.

A Note on Breathless

There is another point of comparison that helped me clarify what was missing.

Breathless, which is structurally close to 24XX, behaves very differently in practice. The resource economy creates a chain reaction where actions degrade your capabilities, which in turn creates new problems, which then require further action.

Once you start rolling, it is difficult to fall back into a completely stable state.

Even if the scene is not outwardly dangerous, the system is constantly nudging things toward tension. It does not rely entirely on the GM to maintain that pressure.

I have used it enough times to see a consistent pattern. It rarely stalls, even in slower sequences.

That contrast made the limits of 24XX more visible.

What I Would Do Differently

If I were to run 24XX again in a similar scenario, I would make some adjustments from the start.

• First, I would define explicit sources of ambient risk in the setting. Not immediate threats, but underlying conditions that can surface without forcing the players into reckless behavior. Suspicion levels, time pressure, resource constraints.

• Second, I would consider adding a lightweight oracle or event generator to activate during low-risk phases. Something that introduces change without needing a triggering action from the players.

• Third, I would be more intentional about framing scenes closer to the edge of uncertainty. Not by forcing danger, but by starting in situations where something is already slightly unstable.

All of these are ways to compensate for the system’s silence in calm moments.

Where 24XX Still Shines

None of this changes what 24XX does well.

When the fiction is already under stress, it is fast, clear, and effective. It gets out of the way and lets risky decisions take center stage. It avoids the noise of constant rolling and focuses attention where it matters.

For short missions, action-heavy play, or scenarios where danger is always close, it is a strong choice.

The problem is not in those conditions.

The problem appears when the game naturally shifts into a lower register and stays there for a while.

The Practical Question

So the question I am left with is simple:

Do I want a system that waits for risk, or a system that helps create it?

There is no universal answer. It depends on the kind of play you want to support and how much responsibility you are willing to take on as a GM.

For this campaign, the answer became clear through play rather than theory. I need a system that stays active even when the characters are being careful, because careful play is not a temporary phase here. It is the core of the experience.

Switching systems is not a failure. It is part of the process of aligning tools with intent.

And in this case, the friction was useful. It exposed something I had not fully articulated before.

Silence in a system is not neutral. It shifts weight onto the person running the game.

The real question is whether that is a weight you want to carry.

Last week, I published “Fiction Engines, Pressure Engines, and World Engines” here on the Substack. The core idea was simple: the label “narrative game” has become so broad it hides more than it reveals. Games grouped under that umbrella often do radically different things at the table.

The clearer question isn’t what a game cares about (fiction, character, world). It’s how the game transforms what you describe into what happens next. Where does the momentum come from?

That article mapped the terrain. This post is about one specific region of that map: the fiction engine paradigm.

And I have two pieces of news:

1. The full Fiction Engine Framework is now live online.

2. Starting next week, this newsletter will run a weekly series: down-to-earth, playable versions of each companion essay.

But first: what is a fiction engine, in plain language?

The Short Version

A fiction engine is a game design that tries to stay out of the way.

You describe what your character attempts inside the story. The game gives you a quick, honest answer. That answer changes the story. Play continues.

The goal isn’t to simulate everything. It isn’t to formalize every possible action. The goal is momentum: keeping the fiction moving while preserving uncertainty, agency, and consequence.

Think of it like this: the rules are the plumbing. The fiction is the water. A good fiction engine makes sure the pipes don’t leak, don’t clog, and don’t demand your attention while you’re trying to drink.

What This Is Not

This framework is not a claim that all good RPGs should work this way.

Other paradigms are coherent, intentional, and excellent at what they do:

• Move engines (like PbtA) give you dramatic rhythm by sorting actions into predefined categories.

• Pressure engines (like FitD) make risk legible and costly through managed economies.

• Metacurrency engines (like Fate) externalize authorial control so you can shape story beats directly.

• World engines (like OSR) center the environment as a puzzle to navigate.

None of these are “wrong.” They just optimize for different experiences.

The fiction engine paradigm optimizes for thin mediation. It accepts tradeoffs: less structural scaffolding, less prescribed pacing, less genre texture baked into the mechanics. In exchange, you get a fiction that stays primary, responsive, and lightly framed.

Who Is the Framework For?

Three audiences, really:

🔧 Designers: Use it as a checklist. For any rule you’re considering, ask: Does this produce a new fictional state, support the conditions for fictional play, or generate dead overhead? If it’s the third one, cut it.

🔍 Analysts & Players: Use it as a lens. When you look at a game, ask: Where does authority sit? What is the core unit of resolution? How much does the system ask me to think about the system itself? You’ll see patterns that labels like “narrative” or “rules-light” obscure.

🗣️ Everyone: Use it as a shared vocabulary. Terms like fictional intent, diegetic, overhead, and authority drift let us talk about design with less ambiguity. That makes conversations at the table—and in designDiscord—more productive.

What’s Live Now

The full Fiction Engine Framework v1.0 is available online. It includes:

• Precise definitions of core terms

• Operational criteria and failure modes

• Guidelines for designers and players

• A glossary for shared vocabulary

It is technical by design. It is meant to be referenced, not read cover-to-cover.

What’s Coming Next

Starting next week, this newsletter will run a dedicated series: Fiction Engine, Explained.

Each week, I’ll publish a layman’s version of one companion essay:

1. The Transparency Threshold: How much abstraction is too much?

2. Four Designs, One Framework: Applying the lens to FU, 24XX, Breathless, and Hints and Hijinx

3. Faction and Fiction: Testing the framework against OSG and finding its edges

These posts will be short, practical, and focused on play. Think of them as the framework’s “user manual” rather than its “spec sheet.”

One Last Thing

The fiction engine paradigm rests on a single bet: that a system transparent enough to disappear into the fiction produces better play (for the specific aims this paradigm serves) than one that makes its own operation the object of attention.

That bet isn’t for every table. But if it sounds like the game you want to play, or the game you want to design, I hope this framework helps you build it.

— Roberto

P.S. Questions? Play reports? Design experiments you want to run through the framework? Reply to this email. I read everything.

Today I’m releasing the open beta of Loner Core Rules 4e.

This version is fully playable, but still open to revision based on feedback from actual play, edge cases, and places where the text may create friction or fail to communicate intent clearly.

What is Loner 4e?

Loner is a fiction-first, tag-based solo roleplaying game built around emergent play, fictional positioning, and a compact Oracle.

In this fourth edition, the core loop remains the same, but the text has been expanded and sharpened with procedures for:

• Framing a Scene

• Closing a Scene

• Relationships

• Dead Ends

• Challenge Tracks

• Leverage

• The Living World

Why this is an open beta

The rules are playable now.

What I want to test in public is not whether the game exists, but how clearly the text teaches play, where procedures create friction, and whether the fiction-first intent comes through cleanly in actual use.

Files

• Readme: https://hackmd.io/@zotiquest/Bk7k-BAh-e

• Loner Core Rules: https://hackmd.io/@zotiquest/SJLlxfPefx

• Loner Companion: https://hackmd.io/@zotiquest/H1PTkGWTZe

• World Builder’s Guide: https://hackmd.io/@zotiquest/H13ml3NTWe

• Character Builder’s Guide: https://hackmd.io/@zotiquest/SyvOe34abg

What feedback I’m looking for

Please focus on things like:

• Where the text made you stop and reread.

• Which procedures were clear in theory but awkward in play.

• Edge cases that made you unsure what to do next.

• Places where the game felt more mechanical than intended.

• Places where the fiction-first approach came through especially well.

How to leave feedback

You can comment directly on the HackMD review copy here:

https://hackmd.io/@zotiquest/SJLlxfPefx

Or send notes in this format:

• Section:

• Problem:

• What I expected:

• What happened in play:

• Suggested fix (optional):

Final note

If you read or test this version, thank you.

A compact game like Loner lives or dies on clarity. This beta is about making sure the text does the job.

I’ve been sitting on this one for a while, and now it’s finally real: Loner: Cinematic Action is out in the world.

DriveThruRPG

Amazon

This is the supplement I made for those moments when I want Loner to stop being quiet and lean hard into the kind of action that feels like a movie in motion. The kind where the hero slides under a closing door, tumbles forward, and comes up swinging. The kind where the rules don’t get in the way of the scene, because the scene is the point. I love Loner already for how clean it is, how fast it moves, and how much trust it puts in the Oracle. This book doesn’t replace any of that. It just gives me a way to push the system into a more kinetic register when that’s the mood I’m after.

That was the starting point, anyway. I wanted something that could support rooftop chases, impossible leaps, messy heists, over-the-top duels, and those slightly ridiculous action beats that make you grin when they happen at the table. Not because I wanted to turn Loner into a crunchy tactical engine. Quite the opposite. I wanted to keep the same minimalist feel and add a few tools that make action scenes feel sharper, bolder, and a little more dangerous.

The first thing I built was Action Points. I kept thinking about those scenes where the protagonist is hanging by a thread, everything is going wrong, and then they make one last push. In a lot of games, that moment gets flattened into either a generic resource spend or a pile of special-case rules. I wanted it to feel more like a dramatic decision. So Action Points became a small pool you can spend on cinematic moments: getting an edge, canceling a bad outcome, attempting something that should not work, or forcing the story to give you one more shot.

What I like about that mechanic is that it creates choices without turning the game into accounting. You only get a few points, which means you really have to decide what matters. Do you save that AP for the chase, or do you spend it now to make the stunt work? Do you accept the failure and keep moving, or do you burn the resource to keep the scene alive? That tension is exactly the sort of thing I wanted this supplement to have.

The next piece was Stunts. This was the easiest to imagine and the hardest to get right in a way that stayed faithful to Loner. I didn’t want “stunt” to mean “special combat trick.” I wanted it to mean any action that feels bold, visual, and a little over the line. If the description matters as much as the outcome, it’s a stunt. If the move has style, risk, and a real chance to change the shape of the scene, it belongs here.

That matters because I think a lot of the fun in cinematic action is not just whether the character succeeds, but how they succeed. Do they vault over the banister? Do they crash through the window? Do they talk their way through the checkpoint while still moving? The answer can be yes, but the fun is in the shape of the yes. Stunts give that shape a place to live.

I also wrote chase rules, because I wanted pursuits to feel like more than “we’re moving fast now.” Chases in fiction are never just about distance. They’re about obstacles, timing, the environment, and the moment when the whole thing either slips out of control or becomes weirdly elegant. So the chase rules stay light on purpose. A few Oracle questions, some loose distance tracking if needed, and a focus on what the scene is actually doing emotionally.

Then there’s Momentum. This was the part I probably cared about more than I expected to. Action is fun, but action without contrast gets noisy. I wanted something that would help me build those arcs where a quiet scene matters because it comes after a chase, or a confrontation lands because the story has been climbing toward it for a while. Momentum is the glue between scenes. It’s the sense that things are escalating, choices are narrowing, and the next beat matters because of the one that came before.

I also added genre-specific advice, because I knew I’d want this thing to work in more than one kind of story. Kung fu needs a different feel than spy fiction. Superhero action wants spectacle and impossible feats. Heists want improvisation and pressure. Sci-fi wants scale and systems and the occasional very bad decision made at high speed. The mechanics stay the same, but the flavor changes depending on the kind of story you’re telling.

What I’m happiest about is that the whole thing still feels like Loner. It still trusts the Oracle. It still keeps the math minimal. It still leaves room for the story to surprise you. I didn’t want a book that told me how to run an action scene in exhaustive detail. I wanted a book that gave me enough structure to make cinematic action feel effortless, while still letting the fiction breathe.

So that’s the pitch, except I’m not really trying to pitch you on it. I’m mostly excited to share something I made because I wanted it to exist. If you like solo games, if you like action stories, if you like the idea of pushing a rules-light system into a louder and more dramatic mode without losing what made it elegant in the first place, this supplement was built with that exact itch in mind.

And honestly, the best part is still the same thing that makes Loner work in the first place: the conversation between you and the Oracle. The supplement just gives that conversation a little more engine noise, a little more speed, and a few more excuses to do something reckless on purpose.

I’ve been putting off writing this one. Not because the Status Track is complicated, it isn’t. But because it’s the last issue in this series, and I wanted to get the framing right. So let me just start with the problem it was trying to solve.

The Problem with “Fine Until You’re Not”

In Loner, Luck resets between conflicts. That’s intentional. It keeps the system light and prevents attrition from becoming a slow death spiral. But testers kept running into the same situation: a character loses badly, we agree it matters narratively, and then two scenes later... nothing. The fiction had absorbed the defeat without leaving a mark. Tags could carry consequence, sure. Zahra gets tagged Injured. But without structure, that tag tends to evaporate the moment you forget to apply it.

The question became: how do you make losing a conflict stick to the character, mechanically, without bolting on a health point system?

The answer I landed on is the Status Track.

Three Boxes, Three Stages

The Status Track is a row of three boxes. When a character suffers a defeat and the consequence should persist across scenes, you open a track and start filling it. Each box gets a tag. The tags escalate.

The defaults in the rules look like this:

Those aren’t a fixed list, they’re starting points. In a sci-fi game, Hurt might be Suit Breach. In a political drama, Rattled might be Caught Off Guard at the Senate Hearing. The tag is always specific to the fiction. The three-box structure just tells you how bad it’s gotten.

Each filled box gives you one active tag. Not cumulative. When you fill box 2, Injured replaces Hurt, it doesn’t stack on top of it. This is important: the track isn’t a damage counter, it’s a condition tracker. At any given moment, one tag is in play.

When to Open It

This came up a lot in testing. The rule says “when a character suffers a defeat and the consequence should persist,” but that “should” is doing real work.

The short answer: open the Status Track when the defeat has a type. Physical, social, psychological. When you can name what kind of pressure the character is now carrying.

Don’t open it for every loss. A failed lockpick roll doesn’t warrant a track. A brutal interrogation that leaves the protagonist genuinely rattled, that’s worth tracking. A firefight that ends with Zahra pinned and disarmed, that’s worth tracking. The test isn’t “did they lose?” it’s “will this still matter two scenes from now?”

In practice, most conflicts in a session won’t generate a Status Track. When one does appear, it signals to both you and the fiction that something landed.

Recovery

Recovery works the way condition tags work in Loner generally: the fiction has to support it. Rest clears a box. A scene framed explicitly around treating the wound, rebuilding a reputation, or processing what happened clears a box. A Quiet Scene rolled off the Scene Transition table is often where this happens naturally.

What doesn’t clear a box is time passing. Zahra doesn’t stop being Injured because three scenes went by. She stops being Injured because she stopped to treat the wound, or because someone helped her, or because a Quiet Scene gave her the space to deal with it. Fiction first, always.

One thing I noticed during closed beta: players sometimes felt guilty spending a scene on recovery, as if it was wasting time. The opposite is true. A scene where Zahra is patching herself up in a back-alley clinic, nervous about the footsteps outside, is not dead air. It’s where the cost of the last conflict becomes visible. Those scenes earn the next dramatic one.

How It Plays with Other Modules

The Status Track is independent. You can run it alongside Challenge Tracks and Leverage without any interaction rules, because there aren’t any. But in practice they inform each other.

A character with On the Back Foot asking the Oracle about a Challenge Track scene is going to approach that scene differently. That tag is in play if the action connects to the social pressure. Maybe it’s Disadvantage. Maybe it’s just narrative context. Either way, the track has added weight to the scene without adding rules.

Leverage also reads differently when a Status Track is open. Banking a Yes, and... when you’re at box 2 feels more significant. You’re not just holding narrative momentum, you’re holding it under pressure.

Why It’s Optional

Loner 3e handled all of this through pure narration. Defeat happened, you described the consequences, tags went on the character sheet if you felt like it, and play continued. That still works. For short, fast sessions or games where the protagonist feels slightly larger-than-life, a formal consequence track adds friction you may not want.

The Status Track is for campaigns where attrition matters. Where you want the third big loss to feel structurally different from the first. Where Shaken being on the sheet should make both you and the Oracle take it seriously.

If that’s not the kind of game you’re playing, skip it. The core rules are complete without it.

Where This Leaves Us

Ten issues. All four core procedures, all three optional modules, and enough of the connective tissue that I think the system is legible as a design. The closed beta has been running long enough that I’m starting to see where the edge cases cluster, and the feedback has been genuinely useful. Surprisingly few surprises, honestly. The places people got stuck were the places I expected: Dead Ends, Tag Promotion, and figuring out when to open a Challenge Track. The Status Track barely came up as a problem, which I take as a good sign.

Open beta is next. I’ll have more to say about the timeline once I’ve finished consolidating the feedback pass. For now: thanks for following this series. It was useful to write it. That’s more than you can usually say.

Let me be upfront about something. Of the nine core features I’ve worked through in 4e, this one gave me the most trouble to articulate. Not because the rule is complicated, but because it isn’t really a rule. It’s a judgment call. And judgment calls are hard to write.

The mechanic itself fits in two sentences in the core rules. If something matters once, keep it as plain tags. If it keeps showing up, or starts actively pushing back against the protagonist, promote it and give it a sheet. That’s it. That’s the whole rule.

So why did I spend weeks fussing over it?

The Problem Under the Problem

Here’s what kept nagging at me. In Loner, everything is a character is one of the central design ideas. Factions, ships, cursed locations, corporate megaliths: they can all carry tags, and those tags work the same way a protagonist’s skills do. The system is deliberately flat that way.

But “everything is a character” and “give this thing a full character sheet” are two different statements, and I wasn’t being clear enough about the line between them.

In early beta drafts, I had no explicit promotion rule at all. The companion for 3e sort of gestured at it, something vague about “when the fiction demands it.” Playtesters kept asking: when exactly does the fiction demand it? One tester had a safehouse appear in four sessions and never promoted it. Another promoted a single informant after two scenes. Neither was wrong, but neither felt grounded in the system logic either.

The rule needed a threshold.

What Promotion Actually Means

Let me back up and say what I mean by “promotion,” because the word matters.

In play, most named things carry a few tags. The Leton Corporation vault is High-Security, AI-Patrolled, Deep in Corporate Territory. That’s enough to create friction. The oracle uses those tags to color answers and grant disadvantage. You don’t need a concept, a frailty, a goal: you just need enough description to know what pushing against it feels like.

Promotion means giving something the full character structure: concept, skills, frailty, and optionally a goal, motive, and nemesis. Once something has that structure, it stops being scenery and starts behaving like an opponent. You can roll against its skills. Its frailty becomes something to exploit. It has pressure points.

The question is: what earns that treatment?

Two conditions. First, the thing keeps showing up: it’s not a one-scene obstacle, it’s a recurring presence. Second, it pushes back: it isn’t just texture or atmosphere, it actively creates complications for the protagonist.

Both conditions matter. A faction can recur for five sessions as background context and never need a sheet. A single location can qualify for promotion after two scenes if it already feels like it has agency. The test isn’t time in the fiction, it’s the quality of the pressure.

What Closed Beta Revealed

The first version of the rule I sent to playtesters was framed around frequency alone: “if it appears in three or more scenes, promote it.” Clean, testable, mechanical.

It produced bad results.

One tester promoted a city district because it kept appearing as a setting. The district got a concept and a frailty, and the tester dutifully rolled against its skills during infiltration scenes. Nothing clicked. The district wasn’t an opponent. It was a stage. Frequency alone wasn’t the right trigger.

I scrapped the number entirely. The second version was “promote it when it starts acting,” meaning when the oracle’s answers start implying that this thing has its own agenda. Better. But still too fuzzy for players newer to emergent fiction.

What actually helped was shifting the framing question. Instead of asking how often has this appeared?, the question became: if this thing had a frailty, would I know what it is?

That’s the practical test I ended up recommending in the companion. If you can answer that question, if you can already name the weakness in the thing you’re up against, it’s ready for a sheet. If you can’t, it’s still a set of tags, and that’s fine. Tags are not a lesser form of character. They’re just a different one.

The Reluctant Beneficiaries

There’s a class of entities that tends to resist promotion: abstract forces.

A reputation. An ongoing investigation. A promise the protagonist made. Playtesters kept trying to promote these, and they kept not quite working. The problem is that abstract forces don’t push back the way a character does. They generate stakes, they color scenes, but rolling against “the weight of my protagonist’s oath” is not the same as rolling against a corporate fixer who has skills and a frailty.

The guidance I ended up writing: abstract forces work better as tags on the protagonist than as promoted characters in the world. Haunted by the Promise is a frailty. The Promise as a character with a goal and a frailty is a category error. The distinction sounds obvious when stated plainly, but in practice, players in the grip of a resonant fiction want to give everything structural weight. Sometimes the most useful thing a rule can do is say: this belongs here, not there.

The term “narrative game” has become so broad that it conceals the very differences it is supposed to clarify. I wrote Loner out of a specific dissatisfaction with heavier forms of narrative mediation, and out of a clear lineage from Nathan Russell’s Freeform Universal. That makes complete neutrality impossible, but it also makes one thing easier to say plainly: games that are all called “narrative” often do radically different things at the table, and lumping them together does no one any favors.

This article is not a ranking. It is not a polemic against any design tradition. It is an attempt to map the actual terrain of contemporary RPG paradigms using a single, concrete question: where does the game place its engine of play?

The answer to that question (whether momentum comes from fictional consequence, codified moves, managed pressure, metacurrency, character capability, world procedure, or modular architecture) tells you more about how a game actually runs at the table than any label on its cover.

Why “Narrative” Is Too Blunt a Label

Walk into any online RPG space and you will quickly find a common shorthand: on one side, “traditional” games; on the other, “narrative” games. Underneath that narrative umbrella you will find Apocalypse World next to Fate Core next to Blades in the Dark next to Ironsworn next to, yes, Freeform Universal and Loner. These games are apparently siblings.

They are not.

A game can be fiction-forward while still being mechanically dense. It can foreground story while prescribing the shape that story is allowed to take. It can strip down resolution to a simple roll while burying enormous interpretive overhead in its metacurrency. Calling all of these “narrative” is like calling all of Italian, Spanish, and Romanian “Latin”: technically defensible, practically useless.

The clearer distinction, as I see it, is not what the game cares about (fiction, character, world) but how it transforms fictional input into play momentum. That is where the paradigms actually diverge.

Method: What This Comparison Is Actually Measuring

I am not comparing quality here, or genre support, or commercial viability. I am comparing paradigms using a consistent set of criteria:

• Where does authority sit? With the GM, the procedure, the players collectively, or some negotiated blend?

• What is the core unit of resolution? A task, a conflict, an intent, a move trigger, a position/effect judgment, an oracle answer, or a resource spend?

• How much metacurrency does regular play require?

• How much does the system prescribe the shape of fiction: its rhythm, its permissible beats, its dramatic structure?

• What generates story? Consequence? Scene pressure? Exploration? Dramatic framing? Player authorship?

• What kind of cognitive load does the paradigm create at the table?

No paradigm is perfect across all criteria. Each one makes tradeoffs, and each tradeoff reflects a coherent design philosophy. My job here is to describe those philosophies fairly before saying which one I built my own games inside, and why.

FU and Loner: The Fiction Engine Paradigm

Let me start with my own corner.

Freeform Universal is built on a deceptively simple premise: describe what you want to do, roll a die, interpret the result as yes/no with gradations. Tags provide fictional color. The system’s job is to stay out of the way while keeping the fiction moving forward. There is no move list. There is no elaborate consequence economy. There is a fictional situation and a small, honest question: does this go the way you intend?

Loner inherits that philosophy and adapts it for solo play. The oracle structure I built into it (closed questions, a twist die, scene-level chaos tracking) is still organized around the same core principle: minimum mediation between fictional intent and fictional consequence. The oracle does not prescribe dramatic beats. It does not tell you that your scene must escalate, or that failure must cost you something specific. It gives you a nudge and trusts you to do the rest.

This is what I mean by a fiction engine: a small, transparent procedure that keeps events moving without imposing a metalanguage about how narrative should be shaped. These games do not aim to encode dramatic structure. They do not use metacurrency as their primary pacing device. They do not define play through action taxonomies.

What they offer instead is something rarer than it sounds: responsiveness. The fiction stays primary. The mechanics respond to the fiction rather than pre-shaping it.

This paradigm is most likely to appeal to players who want to stay inside the fiction without learning a thick meta-language about narrative control. It is also, I will admit, the paradigm most likely to feel loose to players who need the system to provide structure and momentum. That is not a flaw. It is a design choice with real costs, and I own them.

PbtA: The Move Engine Paradigm

Powered by the Apocalypse games (Apocalypse World, Dungeon World, Monster of the Week, and their many descendants) represent one of the most influential design shifts in modern roleplaying. Their core insight is elegant: if you formalize the categories of meaningful fictional action into procedural triggers (”moves”), you get clarity, momentum, and a shared grammar for what counts as play.

When you trigger a move in Apocalypse World, the game sorts your fictional action into a pre-defined type, applies a specific procedure, and pushes play in a direction the game has already thought about. The GM’s moves respond to this with their own codified toolkit. The whole conversation is shaped, at a subtle but real level, by the game’s grammar.

This creates something that deserves real credit: consistent dramatic rhythm. PbtA games rarely stall. They rarely produce scenes where no one knows what happens next or what was at stake. The moves do that work for you.

But here is what that costs from where I design: the game’s grammar is always visible. Every moment where you ask “does this trigger a move?” is a moment where you are managing your relationship with the system’s taxonomy rather than simply inhabiting the fiction. For many players that overhead is invisible; they internalize the grammar quickly and it fades into background. For me, and for the design sensibility behind Loner, it is a layer of mediation I find myself wanting to remove.

I say this not to diminish PbtA. I say it because if you prefer move engines, Loner will probably frustrate you, and that is useful information.

FitD: The Pressure Engine Paradigm

Forged in the Dark games, Blades in the Dark most prominently, are often discussed alongside PbtA as if they were close cousins. Procedurally, they are meaningfully different.

Where PbtA’s engine is moves, Blades‘s engine is managed pressure. Position and effect. Stress. Resistance rolls. Consequences and clocks. The whole system is organized around making risk legible, costly, and strategically interesting. Fiction flows through a persistent economy of tradeoffs, and that economy is always running, even in downtime, even between scores.

What this produces is remarkable: play that feels tense, where every decision has perceptible weight, where the fiction is always pushing against something. Blades in the Dark is one of the most carefully designed pressure chambers in RPG history, and I mean that as a compliment.

What it is not is thin. FitD is fiction-forward, but absolutely not fiction-light. The interface between fictional intent and fictional consequence is rich, dense, and highly managed. If you are running it well, you are constantly tracking position, weighing stress costs, managing clock advancement, and evaluating consequence severity. That is real cognitive load, and it requires system fluency.

From my design position, FitD asks for a much thicker engagement with its mechanics than FU or Loner does. For tables that want risk and consequence to be the heartbeat of play, that is exactly right. For tables that want to wander, discover, and let events unfold without a running economy in the background, it can feel like the game never lets you simply be in the fiction.

Fate: The Metacurrency Engine Paradigm

Fate Core and its variants represent the clearest case of explicit narrative mediation in common use. Aspects and fate points are central to how the game transforms description into leverage, and leverage into story shape; they are not a supporting layer on the resolution system but its primary engine.

When you invoke an aspect, you are not describing something that happens in the fiction. You are making a claim about the fictional world’s relevance to a mechanical outcome, spending a token to make that claim count, and in doing so, participating directly in the game’s ongoing negotiation of dramatic stakes. That is a specific kind of play, and it is a coherent one. Fate externalizes dramatic control. It makes authorship visible. For some tables, especially those comfortable with metatextual thinking about their characters and their stories, this is exactly what they want.

Here is where I should be fully transparent about my own trajectory. The design path that led from FU to Loner was, in part, a reaction against this kind of mediation. Not because Fate is badly designed (it isn’t), but because I find that the persistent negotiation over aspects and fate points pulls me out of the fiction rather than deeper into it. I am always aware of the game as a system of authored leverage, and that awareness competes with my desire to simply be inside the story asking what happens next.

If you want explicit authorial control over your story’s dramatic shape, Fate is probably one of the most honest tools available. It does not pretend to hide its design logic. For me, that honesty is the cost of admission.

Traditional Games: The Character-Interface Paradigm

I want to be careful here, because “traditional” is an even blunter label than “narrative,” and it covers an enormous range of design.

The defining feature of what I am calling the character-interface paradigm is not crunch, not GM authority as a problem, and not a lack of narrative ambition. It is this: action is primarily mediated through the character sheet as an interface to the world. Stats, skills, abilities, and class features form a detailed vocabulary for what your character can attempt, and the GM adjudicates world response through their own expertise and the game’s guidelines.

This model privileges internal-world causality. Things happen because the world has properties and characters have capabilities, and the intersection of those two things produces outcomes. Story is typically emergent, a result of situation plus adjudication, rather than a procedure the game overtly structures.

The strengths of this paradigm are real: staying present inside a consistent world, a strong sense of character capability as identity, and a kind of play where the fictional stakes feel grounded in an actual place rather than a narrative construction. The costs are equally real: as the character sheet grows denser, the interface can produce friction: moments where the mediation between “what I want to do” and “what the rules say happens” becomes the dominant cognitive activity.

OSR: The World Engine Paradigm

OSR games deserve their own section rather than being absorbed into “traditional,” because their engine of play is meaningfully distinct.

Where traditional games often center the character sheet, OSR games often center the world as procedure. Risk, information, logistics, resource management, and open-ended interaction with a dangerous environment are the primary sources of play momentum. The classic dungeon crawl is not an aesthetic preference: it is the mechanical expression of a design philosophy that puts the world’s consistent indifference, and the player’s careful navigation of it, at the center of everything.

What is interesting about this from a paradigm-mapping perspective is that OSR games can be rules-light without being narrative in the modern indie sense. Their lightness serves the world as puzzle and environment, not fiction as expressive flow. A system with only three stats and a reaction table is not trying to produce story; it is trying to stay out of the way of exploration and consequence.

This makes OSR, in some ways, a closer neighbor to the fiction engine paradigm than it first appears. Both paradigms value thin mediation. But where FU and Loner are thin in service of quick fictional consequence, OSR is thin in service of open world interaction and player problem-solving. The goals are different even when the procedures are comparably spare.

Cypher and Cortex Prime: The Middle Zones

Not every important design fits cleanly into a paradigm family, and two systems in particular are worth describing as middle-zone or assembled cases.

Cypher System (the engine behind Numenera and The Strange) has a relatively streamlined resolution core: roll versus difficulty, spend effort to modify the target. In operation it often feels lighter than its character options suggest. But the effort economy is meaningfully different from metacurrency as Fate uses it: rather than externalizing dramatic control, effort is a player-managed resource that tilts odds rather than shapes narrative. Cypher tends to feel adventure-forward, scenario-friendly, and more system-facing than FU or Loner but far less prescriptive about fictional shape than PbtA or Fate.

Cortex Prime is a different kind of challenge to categorize because it is deliberately not a single paradigm. It is a framework for assembling one. Dice pools, modular traits, SFX, and genre emulation modules can support highly expressive play across wildly different contexts; they can be tuned to approximate other paradigms. The cost of that flexibility is visible system architecture and non-trivial design overhead. Playing Cortex Prime well means understanding what you are building and why. That knowledge requirement is itself a kind of cognitive load, and for tables without a design-minded player or GM, it can be more burden than freedom.

I find both systems interesting precisely because they complicate clean family trees. Any honest map of paradigms needs to have edges where the categories blur.

Comparative Synthesis

Here is the map as I currently understand it. Treat these as ideal types: useful lenses, not prison cells.

The useful work this table does is not to rank these paradigms but to identify their dominant source of play momentum. In FitD, momentum comes from managed pressure. In PbtA, it comes from move-triggered procedure. In Fate, it comes from aspect invocation and narrative authorship. In FU and Loner, it comes from asking a small, honest question and following wherever the fiction leads.

Many actual games blur these categories, and some of the most interesting designs do so deliberately. But the categories remain useful because they give us something specific to talk about: a vocabulary for the actual machinery of play rather than its marketing description.

Acknowledging Bias Without Collapsing Into Subjectivity

Let me be direct: I prefer low-mediation fiction engines. My work grows from that lineage. Loner is an attempt to make solo play as frictionless as possible, to get out of the way of the fiction and trust the player to do the creative work.

That preference shapes every comparison I have made above, and you should factor it in.

But here is the move I want to make carefully: disclosed bias is not the enemy of rigor. The real danger is not having a perspective: it is pretending that all paradigms seek the same thing, or evaluating each one using criteria borrowed from another. When someone criticizes PbtA for “not being a real roleplaying game” because it uses moves, they are applying character-interface criteria to a move engine and finding it lacking. When someone criticizes traditional games for “not being narrative enough,” they are applying fiction-engine or metacurrency criteria to a world-interface system and finding it lacking. Both critiques miss.

The more honest question for any paradigm is: given what this design is trying to do, does it do it well? By that standard, Blades in the Dark is a superb pressure engine. Apocalypse World is an extraordinary move engine. Fate is an unusually coherent metacurrency system. Knave or Into the Odd are elegantly functional world engines.

None of them is what Loner is. That is not a failure. That is the map working.

Conclusion: Stop Asking Which Paradigm Is “More Narrative”

The question I keep encountering, in forum threads, in design conversations, in reviews, is some version of: is this game actually narrative? As if there were a single narrative ideal that games approximate or fail to reach.

I want to suggest a replacement question: how does this game transform fictional input into play momentum?

That question opens the map rather than collapsing it. It lets you recognize that Blades in the Dark and FU are both fiction-forward in intent but radically different in structure. It lets you see that OSR and Loner share a value for thin mediation while pursuing entirely different kinds of play. It lets you stop arguing about which tradition is “real roleplaying” and start asking which procedure serves your table and your fiction right now.

FU and Loner occupy a specific, describable position on that map: games that try to keep the engine small, the mediation thin, and the fiction moving. They are not the only valid position. But they are a real and distinct one, and I think they deserve to be recognized as such rather than blurred into a generic “narrative” category alongside games that work by entirely different means.

That is the design conviction behind everything I build. I thought it was time to say it clearly.

The last session ended two weeks ago. The adventure wrapped up, the notes got closed, and now you’re sitting down to start something new. You flip back through what you wrote: a handful of NPCs, a location that got messy, a thread you never resolved. And somewhere between “where did I leave off” and “where do I start now,” the question surfaces: what happened to all of this while I wasn’t playing?

Why Continuity Costs Something

The Living World is an optional module, and I want to be upfront about what that means. In 3e, there was no formal procedure for post-session world upkeep. You played, you stopped, and next time you started fresh. Any continuity came from memory or improvisation. Geared Towards Loner games inherited the same approach: some handled it through setting-specific conventions, most left it to the player. The module is optional here for the same reason the others are: to keep 4e compatible with that existing body of work. If you’re upgrading from 3e or running a GTL setting, nothing breaks if you skip it. Appendix B covers the transition in full.

That said, it solves a problem that every player running an ongoing story will eventually run into: the world doesn’t pause between sessions, but your notes might imply that it did. Once you’re three adventures deep into the same protagonist’s story, and the relationships have accumulated weight, the locations have history, and a few threads are still visibly dangling, “starting fresh” actually costs you something. If none of that carries forward, you’re playing a series of disconnected events rather than a story.

What the Procedure Actually Does

It’s a post-adventure pass. After the story concludes, before you put the notes away, you go through three categories of elements and update them to reflect what just happened.

NPCs and factions are the first category. For each NPC or faction who played a meaningful role, you ask a few questions. Has the relationship with the protagonist shifted? If so, update or assign a relationship tag. What do they want now, given that the adventure changed their situation? Are they still in play, or have they gone somewhere the protagonist can’t follow?

That last one matters. If an NPC is gone, dead, arrested, fled offworld, whatever the fiction established, then any relationship tag built with them loses its anchor. You record it in your notes as history, but it stops functioning in play. The loss is a story fact. It may cast a shadow on future scenes, but it doesn’t grant advantage anymore, because there’s no one there on the other end of it.

Locations are next. For each place that featured in the story, what’s changed? Tags update to reflect the fiction. The Neutral Ground from the first adventure might be Enemy Territory now. The Abandoned Safehouse might be Burned to the Ground. These aren’t cosmetic notes. They’re immediately in play the moment you return. If the protagonist walks into a location tagged Enemy Territory, that tag is doing work before the first oracle question is asked.

Events are the third category: unresolved threads, hanging consequences, revelations that nobody acted on yet. You note whether each one has been addressed or still hangs in the air, and what pressure it continues to exert. An event that nobody dealt with didn’t go away. It accumulated.

How Much Is Too Much

The question players kept running into during closed beta wasn’t “what do I update?” It was “how much do I update?” The procedure asks you to note what’s changed for each significant NPC, location, and event. But after a dense adventure with a dozen speaking parts, that could mean a lot of notes, and the friction was killing the post-session momentum. Players were either overdoing it, writing paragraph summaries for every background character, or skipping the whole thing because it felt like homework.

The answer I landed on is: only update what would actually change a tag. Not everything that happened matters going forward. An NPC the protagonist spoke to once, who didn’t shift their stance, whose situation is basically the same as before, doesn’t need an update. The test is simple: if this element reappears in the next adventure, would anything about how I’d play it be different? If yes, note the change. If no, leave it.

This is a judgment call, and I’ve been explicit about that in the text. The Living World procedure is not a bookkeeping requirement. It’s a prompt to think about what the world retained.

The Living World and Meanwhile

One thing the beta made clearer than I expected: players wanted to know how The Living World interacts with Meanwhile.

Meanwhile is the in-session version of the same idea: the world doesn’t pause when your protagonist is offstage. When you roll Meanwhile during play, you cut to whoever holds power, update their tags, and ask whether an ally acts independently. That’s the same logic as The Living World, compressed into a single procedural interrupt.

The Living World is what you do at the end. Meanwhile is what you do during. Together, they create a fiction where things happen that your protagonist doesn’t control and doesn’t always know about. That’s what gives the world the texture of something that was going on before you arrived and will keep going after you leave.

One Thing I’m Still Watching

There’s one design decision I’m still monitoring as the beta continues. The procedure currently specifies that updated tags are “immediately in play the moment the next adventure begins.” That phrase comes up twice in the text, once for NPCs and once for locations. I put it there on purpose: I wanted to be clear that these aren’t background notes for atmosphere. They’re active fictional conditions.

But a few beta players read it as a directive to front-load every updated tag into the opening scene, which isn’t quite right. The tags are available from the start. Whether they come into play depends on what the next adventure is actually about. A tag that’s live but not yet relevant is waiting, not wasted.

I’ll probably add a line clarifying this before we move toward open beta.

In a previous post, I asked a simple question: where does a game place its engine of play? Does momentum come from moves, metacurrency, character sheets, or world procedure? I argued that lumping everything under “narrative” hides what actually happens at the table, and that the clearest distinction between paradigms isn’t what they care about, but how they transform fictional input into play momentum.

Today, I’m introducing a framework that doesn’t fit neatly into any of those buckets, because it runs on a different axis entirely: the faction engine.

Free OSG Resources

What Open Strategy Games Actually Are

Open Strategy Games (OSG) sit between wargames and role-playing games, but they aren’t a compromise between the two. They take factional conflict, strategic stakes, and turn structure from wargames. They take open-ended action and play within a fictional world from RPGs.

What they leave behind is just as important:

• No dense combat resolution tables or zone-of-control math.

• No single protagonist moving through a referee-authored arc.

• No character sheet acting as an interface to the world.

In an OSG, you play a faction. You receive a brief that tells you what you want, what leverage you hold, and why the scenario matters to you. Then, turn by turn, you act: one action at a time, in a world that changes in response to what everyone else is doing.

Lineage & License (Credit Where It’s Due)

Before going further: this framework is not my invention.

The Open Strategy Game format was defined by Chris McDowall (Bastionland) and Sam Doebler (Dreaming Dragonslayer), building on the Matrix Game tradition established by Chris Engle and Tom Mouat. What I have done is systematically distill their posts, scenario handouts, and design notes into a single, plain-language reference.

Everything in the Open Strategy Games Resources is released under Creative Commons Attribution-ShareAlike 4.0 International. You can use it, adapt it, build on it. Just credit the source and share alike. That is the point.

The Core Loop: How It Runs at the Table

The structure is deliberately thin so the fiction can breathe. Every turn follows the same rhythm:

1. Private Submission. Each faction submits exactly one action, sent directly to the referee. Not public. Not reactive. The format is three parts:

   • Action: What specifically are you doing?

   • Outcome: What result do you want?

   • Leverage: Why is this likely to produce that outcome? Ground it in established fiction: resources, relationships, position, prior actions.

2. Simultaneous Adjudication. The referee reads all submissions, grades leverage, rolls where needed, and writes outcomes. No public arguing. No table debate. The referee adjudicates, stays consistent, and protects interesting outcomes from being argued away by the loudest voice.

3. The Public Report. The referee publishes a short, factual, third-person summary of what happened. The Report does two things at once: it chronicles the turn, and it re-seeds the board. Every outcome leaves at least one hook for other players to respond to.

4. Repeat. Players read the Report, negotiate, adjust strategy, and submit again. The game ends after a fixed number of turns. Each player self-assesses whether they achieved their objectives. Then you run the debrief. That conversation is often the best part of the whole experience.

The Adjudication Engine

I want to be plain about how calls are made, because this is where OSG’s engine actually lives.

When an action faces opposition, the referee doesn’t calculate modifiers or consult a combat table. They ask one qualitative question: given what is established in the fiction, does this faction have enough of an advantage that success is more likely than not?

• Strong leverage: keep the high die on 2d6.

• Weak leverage: keep the low die on 2d6.

4–6 means the desired outcome occurs. On a 6, something especially good may also happen.
1–3 means the action proceeds, but the outcome is worse than desired. On a 1, something especially bad may also occur.
Doubles open the door for a Force of Nature: a chaotic external event that complicates the situation for everyone.

Before writing any outcome, the referee runs the RAT checklist:

• Reasonable: Proportionate to the action and the fiction?

• Actionable: Does it leave at least one hook for another faction?

• Traceable: Can you point to earlier events that led here?

And there is a hard design rule: No Action Without Friction. Every outcome, successful or not, leaves a mark on the world. Friction complicates; it does not block. Replace “no” with “yes, but.” A failure that produces three hooks is better for the game than a success that produces one.

The Philosophy

The founding OSG scenario opened with two sentences that still define the entire framework:

The goal of the game is to achieve your objectives.
The point of the game is to create a credible narrative.

Play to win. Play to find out. Both at once.

Strategy emerges from position, action, and consequence rather than from optimizing against a closed menu of moves. A player who sacrifices their objectives to make the narrative more interesting is playing correctly. A player who exploits a rules gap to win while collapsing the fiction is playing incorrectly.

What’s in the Handbook

The Open Strategy Game Handbook is built as a playable design framework, not a rigid rulebook. It treats OSG as a structure you can adapt to any genre, scale, or format.

• Part I: Practice covers how to play and run the game: the turn sequence, private submission, referee adjudication, report writing, handling overflow players (Consultants, Team Actors), async timing, dropout policies, and the mandatory debrief.

• Part II: Design walks through scenario construction in seven steps: writing a one-sentence problem statement, differentiating factions by leverage type (not power level), drafting paired short/long objectives, designing maps as argumentative surfaces, assigning spendable bonuses, building Non-Player Actors, and running Turn Zero to surface assumptions before play.

• Appendices provide blank brief templates, referee checklists, genre seeds (war, politics, mythology, ecology, corporate, supernatural), a single-page reference card, a glossary reconciling OSG terms with traditional Matrix Game vocabulary, and a complete ready-to-run scenario (The Corentine Succession).

All of this is a systematic reorganization of material that already existed in scattered form across McDowall’s and Doebler’s posts, scenario documents, and actual-play reports. The value is not in novelty, but in accessibility: a single place to point someone who asks, “How does this actually work?”

Where It Sits on the Paradigm Map

If we map this against the framework from the last post, OSG doesn’t run on character capability, move triggers, or metacurrency authorship. Its momentum comes from managed strategic consequence and public re-seeding.

It shares OSR’s preference for thin mediation, but where OSR serves exploration and character survival, OSG serves factional strategy and emergent political narrative.
It shares PbtA’s drive for forward momentum, but replaces procedural moves with a single submission format and referee judgment.
It shares traditional games’ internal-world causality, but strips away the character-sheet interface in favor of faction briefs and asymmetric leverage.

The engine is thin by design so that positional asymmetry and fictional leverage do the heavy lifting. The Report is the heartbeat. The debrief is where the meaning is made retroactively.

What Comes Next

Maybe, someday, I’ll post scenario breakdowns, design notes, or actual play transcripts. For now, the handbook is open. The engine is running.

If you want to run a game where strategy emerges from position, where every turn reshapes the board, and where the conversation after the final report is often the best part of the experience, this is the framework.

There’s a particular kind of silence that falls over a table, physical or virtual, when the fiction just stops working. Not because anyone did something wrong. Not because the rules are broken. Everyone is present, everyone is willing, and yet the game goes completely numb. Prompts land flat. Decisions feel arbitrary. The story refuses to move.

I’ve seen this happen, and I’ve felt it happen, and for a long time I blamed the usual suspects: unclear rules, undercooked scenarios, the wrong oracle, not enough prep. But the more I’ve run and designed and watched other people play, the more I’ve come to a different conclusion.

The game went numb because the people at the table didn’t share a world.

Not a rulebook. A world. And that distinction, I think, is the most important one in all of tabletop RPG design.

The Rulebook Doesn’t Run the Game

In any tabletop RPG, roughly ninety percent of what makes the game actually function comes from familiarity: familiarity with the specific setting, or, when that isn’t possible, familiarity with the genre’s tropes. The rulebook accounts for far less than we think. Less than we’ve been taught to think.

This isn’t a knock on rules. Good mechanical design matters. Procedures, resolution systems, tables, oracles: these are real tools and they do real work. But they are scaffolding. They hold the fiction up. They are not the fiction itself, and they cannot generate it from nothing. What generates the fiction is the shared imaginative material that everyone at the table brings in before the first die is rolled.

Think about what actually happens during play. The GM describes a scene, or the oracle generates one, and immediately every player at the table is filling in details the scene didn’t provide. What does this place smell like? How do the NPCs here carry themselves? What are the unspoken rules of this social encounter? What is probably behind that closed door? None of this is in the text. All of it flows from what the players already know, or think they know, about the world they’re in.

This gap-filling is the game. It is the core cognitive act of tabletop play. And it only works when everyone at the table is drawing from roughly the same pool.

When they are, the fiction becomes self-sustaining. Prompts ignite rather than stall. Improvised details feel coherent rather than random. The game develops the texture of a real place, with its own logic and weight. When they aren’t, when players are working from different mental models of the world or from no model at all, every gap becomes a negotiation, every detail becomes a potential contradiction, and the whole thing gradually seizes up.

The shared world is the real rulebook. Tropes are its grammar.

“Play Worlds, Not Rules”

The Free Kriegsspiel Revolution (FKR, for those unfamiliar) is a loose movement in tabletop design that advocates for radically referee-driven, fiction-first play with minimal mechanical overhead. Its prescriptions vary in usefulness, but one central maxim is exactly right: play worlds, not rules.

What that means in practice, what it has always meant even before FKR named it, is that a deeply understood world provides better play infrastructure than any rulebook. If everyone at the table knows the world intimately, the referee barely needs mechanics to adjudicate. Would this character succeed? You don’t need a difficulty table. You need to know the world well enough to answer honestly. What happens next? You don’t need a random event generator. You need to know how this world works, its physics, its politics, its people, its logic, well enough that the next thing follows naturally.

The rulebook steps in precisely where world-knowledge runs out. Mechanics exist to fill gaps in shared understanding. They are a necessary tool, but a compensatory one. The more everyone at the table knows the world, the less you need them.

Rules serve the world. They don’t create it, and they can’t substitute for it.

Why Established Media Is More Immediately Playable

This is why a game set in Middle-earth, the Star Wars galaxy, or the world of Berserk is more immediately playable than a brand-new original setting.

Not more interesting, necessarily. Not better, artistically. More immediately playable: a specific, practical claim. The world already exists in the heads of everyone at the table. The tropes, the tone, the logic, the social texture, the bestiary, the physics of how things work: all of it has been pre-loaded by years of engagement with the source material. You sit down, you say “you’re in the Shire and something is wrong,” and the game moves. Everyone knows what the Shire feels like. Everyone knows what “something is wrong” implies in that world. The shared knowledge is already there, doing its work, before anyone opens the rulebook.

This is also why genre-fluent players can pick up almost any game in a familiar genre and be functional within minutes. A veteran fantasy player handed an unfamiliar fantasy system doesn’t really need to read the setting chapter. They already know the genre’s grammar: what taverns mean, what the wilderness implies, what an ancient ruin probably contains, what a hooded figure in the corner of the room is probably there to do. The tropes transmit a vast amount of world-logic compressed into instantly recognizable forms.

Tropes are the accumulated craft of a genre. They encode what the genre has learned, through decades of stories, games, films, and shared play, about what works. What generates momentum, feeling, stakes, recognizable meaning. They are not the enemy of originality. They are its infrastructure.

The Original Setting Problem

Original settings can work. Some of the most memorable play I’ve had has been in worlds with no genre precedent. But there’s a real cost that designers and GMs often underestimate: everyone at the table needs to be inside the world together, and getting them there takes active, deliberate work.

This is a transmission problem as much as a design problem. A fully realized original world still won’t run well if the people sitting down to play don’t share it. A lore document in the GM’s Dropbox folder is not shared knowledge. Three paragraphs of read-aloud text at session zero is not shared knowledge. What makes it shared is sustained exposure, repetition, and play itself; original settings often need a warm-up period, a season of play where the world is being learned as much as inhabited, before it can start generating the kind of frictionless fiction that established settings deliver on day one.

There’s also a subtler failure mode: the drift. When players don’t yet have a strong enough mental model of the original world, their brains quietly reach for the nearest familiar handhold under pressure. Your original grimdark fantasy starts feeling like Warhammer. Your strange space opera acquires Star Wars gravity. Not because those sources are bad (they’re excellent, and that’s precisely why they’re magnetic), but because the players were filling gaps with the nearest available material, and the original world hadn’t yet given them enough to fill with instead.

Both paralysis and drift are symptoms of the same thing: insufficient shared material.

The practical implication for designers: if you’re building an original setting, your first design job is not the cosmology or the history or the magic system. It is transmission: making the world learnable, communicable, and memorable enough that a group of players can carry it in their heads and work from it under improvisation pressure. That means evocative names that encode meaning, consistent internal logic, and a tone clear enough to generate answers to questions you didn’t anticipate. It means, frankly, knowing which tropes you’re borrowing and being explicit about it, so players know which of their existing cognitive shortcuts apply and which need updating.

What Everyone at the Table Needs to Know

Shared knowledge is easy to invoke as a principle and harder to verify in practice. When a game is running well on it, everyone at the table can roughly answer the following without looking anything up:

• What does this world feel like? (Tone, atmosphere, emotional register. Is this grim? Swashbuckling? Eerie? Domestic?)

• How does danger work here? (Is it random and brutal, or does it follow logic? Do characters die easily? Can problems be solved by force?)

• Who has power, and how do they use it? (Political texture. Who the players can rely on, who they can’t, what institutions exist and whether they function.)

• What does the world want from the protagonists? (The implied contract. Are they heroes? Survivors? Operators? Witnesses?)

• What are the rules the world doesn’t break? (The metaphysical ground floor. Magic works like this. The dead stay dead. Or don’t.)

In an established setting or a genre-fluent game, most of these answers are inherited automatically. In an original setting, they need to be built and transmitted deliberately. And crucially, they need to be consistent enough that players trust their own intuitions about them.

The moment a player second-guesses their own world-intuition, wait, would that actually work here?, is the moment the game starts dragging. Because now they’re playing the rules, not the world. And the rules are a much slower, colder way to play.

Tropes Are the Shared Grammar

Tropes get a bad reputation in design circles, and most of it is undeserved. Any trope used without awareness calcifies into cliché. The grizzled mentor, the chosen one, the tavern as social hub, used thoughtlessly, these are dead weight.

Used with awareness, tropes are compressed world-logic. They carry an enormous amount of information (social, moral, atmospheric, procedural) in an extremely small package. When you say “this is a heist story,” every player at the table immediately knows: there will be a plan, the plan will go wrong in an interesting way, the team dynamics matter as much as the target, success is possible but not guaranteed, and the tone is tense but probably not tragic. That’s a paragraph of setting information delivered in four words.

This is why genre literacy is such a productive play asset. A player who has deeply internalized the conventions of sword-and-sorcery, or noir, or cosmic horror, or space opera, brings a sophisticated generative toolkit to the table, one that can produce plausible, resonant fiction quickly, under pressure, in the gaps between rules. And a designer who understands which tropes their game relies on can build procedures that encode that genre logic, rather than leaving it entirely to the players to supply.

The table that goes numb is almost always a table where that shared grammar broke down. Different players were working from different genre assumptions, or from none at all. The world existed on paper but not yet in everyone’s heads.

The fix is not better rules. The fix is more world: learned together, carried together, played from together.

That’s what “play worlds, not rules” has always meant. The rulebook is a guide. The world is the game.

A Practical Check

Before your next session, design session or play session, ask everyone involved these three questions:

1. Name three things this world has that no other world has.

2. Name one thing that would be totally out of place here.

3. What does a stranger arriving in town probably want?

If the answers converge, if everyone’s working from roughly the same picture, you’re ready to play. If they diverge sharply, that’s your prep work. Not more rules. More world, shared.