What a Fight Costs
Encounter budgets price a fight before anybody rolls. But the formulas are measuring one thing and the table pays for another.
01The Arithmetic of an Enemy
Every system with encounter-building guidelines runs some version of the same math: compare the offensive output of the enemies against the defensive capacity of the characters, adjust for numbers on each side, and produce a difficulty rating. The numbers go by different names — challenge rating, threat level, encounter points — but the structure is identical. You are estimating how much of the characters' resources a fight will consume before one side collapses.
The inputs are straightforward. Enemy damage output across some expected number of rounds, set against character hit points (or their equivalent). Enemy defenses against character attack rates and damage. The result is a projected cost in hit points and, where healing is rationed, in spells or charges spent restoring them. Get this roughly right, and the referee can plan a session around a believable resource budget without accidentally scheduling three easy skirmishes followed by an encounter that ends the party.
What the formulas count vs. what they miss
- 01Attrition (hit points, spell slots drained per round) — what encounter math is built to measure
- 02Spike damage — high variance on a single hit; budget formulas use averages and miss it
- 03Action economy asymmetry — more bodies change the shape of the fight, not just the total threat
- 04Terrain — chokepoints and elevation alter effective action economy; invisible to standard budgets
- 05Real time — a 45-minute fight is expensive regardless of HP spent; no formula captures this
The thing these formulas measure is attrition: steady, round-by-round pressure that slowly drains both sides until one breaks. Attrition is measurable. It is also only half the story.
02The Two Variables Nobody Prices
The first missing variable is spike damage — the sudden burst that ends a fight in a round or two before the expected math can unfold. A creature with a low average output but a high maximum single hit can drop a character before they act twice, regardless of what the budget predicted. Encounter math tends to use average values because averages are tractable, but averages conceal variance. A fight against one powerful enemy swings harder than a fight against four equal-budget weaker ones, even when the totals are identical on paper. The distribution matters, not just the mean.
The second missing variable is action economy. Four enemies and four characters are not four fair duels running in parallel — they are one economy operating against another. Each side benefits from having more activations per round, and the benefit is not linear. An extra body on the enemy side doesn't just add damage output; it splits the characters' attention, forces target priority decisions, and may deny a focus-fire tactic that would neutralize one threat quickly. None of the standard encounter formulas model this directly. They scale by total threat, not by the shape of the initiative order.
They are extremely good at one thing: preventing the referee from accidentally scheduling something wildly beyond or beneath the party's capacity.
Then there are the costs that appear nowhere in the budget at all: time and narrative. A fight that takes forty-five minutes of real play is expensive even if the characters emerge unscratched. It consumed a third of the session. Players made hundreds of decisions. Momentum shifted three times. That is a high-cost encounter by any practical measure, and it shows up on no budget spreadsheet.
How to use a budget tool without being fooled by it
- 01Treat the result as a ceiling-and-floor sanity check, not a simulation
- 02Apply a separate multiplier for lopsided action economies (one big enemy vs. a swarm)
- 03Audit spike potential independently: what is the worst-case single-round output against any one character?
- 04Factor terrain before assigning the encounter, not after the roll
Terrain belongs in this category too. Chokepoints, elevation, difficult ground, forced exposure to ranged fire — all of these change effective action economy and spike risk without changing the numbers fed into a budget formula. Two encounters with identical challenge ratings can feel radically different because one is fought in a corridor and one in an open room. The formula does not know the shape of the space.
03What the Budget Is Actually For
None of this means encounter budgets are useless. They are extremely good at one thing: preventing the referee from accidentally scheduling something wildly beyond or beneath the party's capacity. Used as a floor-and-ceiling sanity check rather than a prediction, they work. The problem comes when the formula is treated as a simulator rather than a calibration tool.
A referee who understands what the math is counting can compensate for what it ignores. Price spike threats higher than their average output suggests. Treat action economy asymmetry as a difficulty multiplier independent of raw stats. Account for terrain before the players touch it, not after. And recognize that session time is a real cost — a budget that only counts hit points spent is missing the most visible currency at the table.
The formulas tell you what the fight will drain. Only the full context tells you what the fight will cost.