Combat — The Meaning of Violence in Threshold
Combat is one of the most visible parts of a tabletop RPG.
It's also one of the easiest places for a system to drift away from its own goals.
Before getting into initiative, actions, or mechanics, I want to step back and define what combat is actually supposed to be in Threshold. Not how it works, but what role it plays in the game.
Because once that's clear, the mechanical decisions become much easier to justify.
What Combat Does in Different Games
Combat tends to feel like a constant across tabletop RPGs, but its role varies more than it first appears.
In some systems, combat is the primary engine of play. It provides structure and challenge, and much of the game's depth comes from how encounters are approached and resolved. In games like Dungeons & Dragons, a large portion of the rules exist to support this kind of play.
In others, combat is simply one form of conflict among many. It sits alongside negotiation, stealth, and social pressure, often using the same core mechanics. Games like Blades in the Dark treat violence as one option rather than a default path.
There are also systems where combat is less about step-by-step resolution and more about consequences. A single roll or move can determine how an exchange unfolds, with the focus placed on what changes rather than how each moment is simulated. You can see this approach in games like Apocalypse World.
None of these approaches are inherently better than the others. They reflect different priorities.
What matters is that the mechanics align with the role combat is meant to play.
Combat as One Tool, Not the Default
In many systems, combat becomes the center of play almost by accident.
The rules for fighting are the most detailed. Character options often point in that direction. Encounters are structured with the expectation that violence will resolve them. Over time, this trains both players and GMs to treat combat as the default solution.
That isn't the direction I want for Threshold.
Combat is one way to engage with a problem. It sits alongside negotiation, exploration, manipulation, avoidance, and preparation. It should feel like a meaningful choice, not an assumed outcome.
When players choose violence, it should be because it makes sense in the moment, not because the system quietly funnels them toward it.
Stakes Before Strategy
It's easy for combat to become detached from the world it's happening in.
Once initiative is rolled, attention shifts toward positioning, sequencing, and optimization. The reasons the fight started can fade into the background.
I want those reasons to remain present.
Before a fight begins, there should be a clear sense of what's at risk. Who is involved, what happens if things go poorly, and what changes if the characters succeed.
Those questions should still matter while the fight is happening.
Winning isn't just about ending the encounter. It's about what that outcome means in context.
Fast Resolution, Lasting Consequences
One of the most consistent friction points I've run into with combat-heavy systems is pacing.
Fights expand to fill entire sessions. Turns stretch longer than the moments they represent. The table's attention shifts from decision-making to process.
That's not the experience I'm aiming for.
Combat in Threshold is designed to resolve quickly. Not because it's unimportant, but because it shouldn't crowd out everything around it. A fight should feel like a sharp moment rather than a prolonged procedure.
The outcome, however, should persist.
Damage carries forward. Resources are spent. Positions change. Relationships can shift. The world doesn't reset once the fight ends.
The contrast matters: resolution is brief, consequences are not.
Combat Is Not Binary
Many systems quietly assume that combat ends when one side is no longer standing.
That structure is simple, but it flattens behavior. Every fight becomes a question of endurance rather than judgment.
That isn't how conflict usually plays out.
Creatures respond to danger based on what they are and what they want. A wounded animal doesn't continue fighting if escape is possible. A pack may break once its leader falls. Something more cunning might withdraw early, choosing to regroup rather than risk a decisive loss.
Intelligent opponents go further. They assess risk, change tactics, and recognize when a situation has turned against them. Surrender, retreat, or negotiation can all emerge once the outcome is no longer in their favor.
That doesn't remove tension. It changes where that tension sits.
The question stops being "who survives to the last hit" and becomes "how far this situation escalates before someone chooses to end it."
Ending a fight also isn't the same as winning it. Driving something off, forcing a retreat, or reaching an uneasy pause can all resolve an encounter, but each leads somewhere different.
Combat becomes part of a larger chain of events rather than a closed loop.
Positioning Without Precision Counting
Positioning plays a meaningful role in combat.
Where you stand, what you can reach, and how you move all influence the outcome of a fight. Those decisions should remain visible to players.
At the same time, there's a point where precision stops helping.
Grid-based systems often push toward exact measurement. Counting squares can slow the flow of play and shift attention toward optimization rather than intent.
In practice, that's not how people actually experience distance in motion.
Through training and repetition, you develop a sense of what is within reach and what isn't. Whether that's striking distance, effective range with a weapon, or how far you can move before someone can respond, those judgments come from familiarity rather than measurement.
My military training and time in combat arts taught me this: when you're moving and fighting, distance is understood intuitively rather than calculated.
That's the perspective I wanted Threshold to capture.
Instead of tracking exact units, the system uses zones. The goal is to preserve the importance of positioning without requiring constant calculation. Players should be able to understand their options at a glance and act on them based on intent, not measurement.
Characters Are Capable, Not Untouchable
Power scaling has a direct effect on how combat feels over time.
In many systems, characters eventually reach a point where threats must escalate dramatically just to remain relevant. That escalation can disconnect the system from the world it's meant to represent.
In Threshold, characters become more capable, but they remain vulnerable.
They gain reliability. They expand their toolkit. They learn how to approach situations more effectively. What they don't gain is immunity from risk.
That keeps combat grounded. Stakes remain personal, and decisions continue to matter even at higher tiers of play.
Violence Has a Cost
This ties back to the broader themes of the setting.
The world of Threshold is already under strain. Environments are fragile. Resources are limited. Relationships are unstable.
Violence interacts with all of those.
A fight can solve an immediate problem, but it often creates others. It can escalate tensions, damage environments, or close off alternatives that might have been available earlier.
That doesn't mean combat is discouraged. It means it is consequential.
Choosing violence should feel like a decision, not a default action.
What This Means for the System
All of these ideas feed directly into the mechanics that follow.
The resolution system needs to be fast without becoming unclear—fights should feel like sharp moments, not prolonged procedures. Players need to stay engaged throughout, with meaningful decisions on every turn. Coordination matters, but rigid turn order can kill momentum. Positioning creates tactical depth, but counting squares slows everything down.
Most importantly, the results of a fight need to carry forward into the rest of the game. A combat system that resets the world to neutral after every encounter misses the point.
The system doesn't start with mechanics and hope they produce the right experience. It starts with the experience and builds toward it.
What I Worked On
This stage focused on clarifying the role combat should play in the game.
Rather than building mechanics immediately, I spent time examining how combat behaves in different systems and where it tends to pull attention away from the rest of play.
What Went Wrong
One recurring issue was how easily combat becomes the default focus of a game.
Even when that isn't the intention, systems tend to reward it simply because it is the most detailed and supported part of the rules.
What I Changed
The main shift was making the purpose of combat explicit.
Instead of assuming it would align naturally with the rest of the system, I treated it as something that needed clear boundaries and design goals.
That clarity makes it easier to evaluate every mechanical decision that follows.
What I'm Working On Next
The next step is to move from philosophy into structure.
How does a fight actually begin? How is initiative handled? What does a round represent, and what can a character do during it?
Those questions lead directly into the next post.
Questions
Two things I'm especially interested in:
In your experience, what causes combat to overtake a session? Is it the mechanics themselves, or how they're typically used?
Do you prefer combat systems that emphasize detailed tactics, or ones that resolve more quickly with broader decisions?
Next time, I'll break down how combat in Threshold is structured at the table, starting with initiative and the flow of a round.
