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.