Designer's Note

Where It Started

Breaking Point started from a single dissatisfaction: most solo roleplaying games ask you to play a character. You inhabit a person, follow their arc, resolve their story. That is a legitimate and well-explored form. It has produced some genuinely inventive games. But it is not the only one, and for what I wanted to explore, it was the wrong shape entirely.

What I wanted was something that felt more like reading a political history than playing a protagonist – the experience of watching a situation develop under its own pressure, where the outcome is not a story about someone but a record of what happened when incompatible powers collided. The unit of play needed to be the faction, not the individual. The question at the center of each session needed to be not “what does my character do?” but “what does the board demand, and what am I willing to spend to answer it?”

This distinction matters more than it might first appear. When you play a character, the game’s implicit contract is emotional: you are invested in a person, their survival, their growth, their relationships. When you play a faction, the contract is strategic: you are invested in a position, its sustainability, its leverage, its exposure. The fiction still matters – it has to, or the decisions have no weight – but it is the context for choices rather than the primary focus. That shift in emphasis changes almost everything about how the game is designed and how it is played.

Why Breathless

The Breathless SRD, designed by René-Pier Deshaies-Gélinas, gave me the right foundation. Its core mechanic – skills that step down each time they are used, resources that exhaust and apply systemic constraints, recovery that is never free – is already a system about cost and constraint rather than heroism. Every action in Breathless carries a price. The question is not whether you will pay, but when and how much.

That structure maps cleanly onto the strategic level. A faction’s skills represent operational capacities that degrade under pressure. Its resource tracks represent the dependencies that sustain those capacities. When Supply exhausts, every Push becomes more dangerous. When Military exhausts, Force and Strike are simply unavailable. The degradation is not a punishment for failure – it is the baseline condition of operating in a contested environment over time. Eventually, everything costs more than you have. That is what the game is about.

The work of building Breaking Point from that foundation was mostly a matter of scaling. Individual skills became organizational capacities. A single character’s health became three resource tracks chosen at setup to reflect the faction’s specific dependencies. The oracle that resolved a character’s action became two distinct oracles: one player-facing, calibrated by the quality of the faction’s preparation; one world-facing, calibrated by the rival’s behavioral disposition. The social layer of a traditional roleplaying game – the other players, the game master, the shared table – became a procedural system of rivals and activation rolls and competitive resolution. Same skeleton, different scale.

The Condition Check

The Condition Check was the design problem that took longest to resolve, and it is probably the mechanic I am most satisfied with in the finished game.

The original instinct was correct: there needed to be a moment of honest reckoning before the dice were touched. A player should have to look at the actual fictional situation and ask whether the action they want to take is genuinely supported. The temptation in solo play is to narrate your way to the outcome you want. The Condition Check is the mechanism that resists that temptation – it externalises the fictional positioning into something countable and therefore auditable.

The early versions failed in two different directions. The first was too loose: the criteria were vague enough that players could count whatever they wanted, and the system became a formality that preceded the dice rather than a genuine evaluation. The second overcorrected: it required a roll to confirm every criterion, which added friction without adding information and made the game feel bureaucratic rather than procedural.

The version that worked emerged from a simple observation about the four criteria themselves. Three of them – skill alignment, resource availability, and situational scale – are objectively readable. You either have an unexhausted resource track or you do not. The action either falls within your skill domain or it does not. These are binary conditions that the player can evaluate directly from the faction sheet and the immediate fiction. But the fourth criterion – whether a rival faction is actively opposing the objective – is genuinely epistemic. It requires information the player does not automatically have. It is the only criterion that cannot be read from the board.

That asymmetry is where the Probe earns its exclusive mechanical territory. The Probe Oracle does not just set a die for information-gathering scenes. It confirms or denies the one criterion that requires situational knowledge. A Yes, and… confirms it cleanly and opens the possibility of the d12 upgrade. A Yes, but… confirms it with a complication attached. A No, and… denies it and fires the immediate backfire consequence. The result has weight because the criterion has weight. And because criterion 3 is unconfirmed by default without a prior Probe, Pushes made without that groundwork are structurally capped – they can never reach Stable, Perilous remains the floor for uninformed action in contested situations. This gives the Probe its purpose without making it mandatory through explicit rule. Players who skip it pay a structural price. Players who do it earn a structural reward. The incentive is built into the architecture rather than enforced by a prohibition.

The Rival System

Rivals went through more iterations than any other part of the game, and the early versions were substantially worse than what ended up in print.

The first versions were damage sources. They activated at the end of each scene, rolled a die, and produced a result that usually meant something bad happened to the player faction. They were pressure in the mechanical sense – they degraded resources, they complicated plans – but they had no agency of their own. They were weather, not opponents.

What changed everything was giving rivals Goals. A rival with a Goal is not just producing pressure; it is moving toward something. Its actions have direction. When it activates and succeeds, it is not just hurting you – it is winning. That distinction changes how the player relates to the rival. You are not just trying to absorb its damage; you are trying to prevent it from achieving its objective while achieving yours. The board is contested in both directions simultaneously.

The Goal Tracker formalises this. Four boxes, marked only for progress that would be difficult to reverse. Not activity, not success, but closure – actions that meaningfully reduce the distance between the rival and its stated objective. The tracker serves two purposes: it gives the player a concrete read on how close each rival is to winning, and it feeds the Disposition Shift.

The Disposition Shift was the last piece. Fixed Dispositions at setup are a convenience that becomes a fiction-breaking constraint by mid-campaign. A Reactive faction that watches two rivals collapse around it should not be rolling d4 forever. A faction that has achieved momentum, that has marked two of its four Goal Tracker boxes, should be pressing harder – not because the rules say so, but because that is how power actually moves. The shift mechanic makes Disposition responsive to the fiction rather than locked at creation. A rival that is winning becomes more aggressive. A rival that is overstretched pulls back. Both directions are causally grounded in things the player is already tracking.

The Competitive Resolution Problem

One of the less obvious design challenges in a solo faction game is simultaneous activation. At the end of every scene, every rival activates. In a three-rival setup, that is three Autonomy Oracle rolls, potentially producing three successful results that all want to apply simultaneously. If you resolve them independently, the game produces pressure spikes that feel arbitrary rather than causal – two factions both achieve their objectives in the same scene cycle, the player faction is hit by both consequences without any mediating logic, and the fiction becomes incoherent.

The Competitive Resolution rule addresses this by imposing a dominance hierarchy on simultaneous results. The highest-impact activation applies fully. All other successful results are downgraded to complications, interference, or partial effects – because the factions collided, because the world cannot absorb two clean successes at once, because that is also how power actually moves. This is the rule most likely to be forgotten in actual play, and the text flags that explicitly. Resolving activations independently is not just inaccurate – it is the most common way the system breaks.

What the Game Is Not

Breaking Point is not a game about progression. There is no advancement system, no improvement track, no accumulation of capabilities over the course of a campaign. Skills degrade. Resources exhaust. Recovery is partial and costly. The faction at the end of a successful campaign is more constrained than the one at the beginning, not less. This is intentional.

Progression mechanics incentivize optimization and create power curves. They reward patience – the faction that plays conservatively, accrues advantages, and strikes from a position of strength. That is a legitimate design space, but it is not the one Breaking Point occupies. The game is designed to make cautious play increasingly untenable. Resources deplete. Rivals accumulate progress. The window for decisive action narrows with every scene that passes without one. The pressure is not just fictional; it is mechanical. Eventually the system forces the question.

It is also not a narrative game in the sense of being primarily concerned with story. There is fiction here – it is the context for every decision – but the game does not ask you to produce a satisfying narrative arc. It asks you to operate under pressure and find out where your faction’s actual limits are. Sometimes the result is a clean victory. More often it is a pyrrhic partial success, a strategic retreat, a collapse that was almost prevented. Those outcomes are not failures of storytelling. They are accurate records of what happened when the mechanics played out honestly.

The Name

The game is called Breaking Point because that is what it is actually about. Not the campaign as a whole, not the arc of a faction’s rise and fall, but the specific moment when the situation demands more than cautious play can provide – when the conditions align just enough, when the window is narrow enough, when the cost of not acting has finally exceeded the cost of risking everything on a single move.

Everything in the system is designed to make that moment arrive. The skill degradation makes every subsequent action more expensive. The resource exhaustion removes options. The rival pressure compounds. The Decisive Action rule exists to mark that moment procedurally – to give it a name, a cost, and a consequence that the system can actually process.

When you declare a Decisive Action, you are not just rolling a d12. You are acknowledging that the board has reached the place where everything has to be risked. The Regroup vulnerability that follows is not a punishment. It is the intended shape of the moment after the gambit: the pause where you find out whether it worked, exposed and committed, with the rivals rolling to exploit what you have become.

That is the game.