·StoryRoll

Resistance and Vulnerability 5e: Why They Don't Just Cancel Out

The red dragon breathes fire on the party's tiefling, who has fire resistance from their lineage, and the warlock mutters a curse that happens to grant fire vulnerability on the same creature for one round. Someone at the table says the obvious thing: resistance and vulnerability cancel out, so just deal normal damage and move on. The table nods, the damage gets written down, and the math is wrong, by exactly one point, every single time.

Resistance and vulnerability 5e are two of the simplest-sounding rules in the game, each a single sentence long, and together they produce one of the more common small errors at the table. Not because the individual rules are hard. Because "they cancel out" is a mental shortcut that feels true and isn't, and the gap between the shortcut and the actual math never gets big enough for anyone to notice something's off.

Resistance and Vulnerability 5e: What Each One Actually Does

Taken alone, neither rule is complicated.

Resistance to a damage type means damage of that type is halved against you, rounded down. Vulnerability to a damage type means damage of that type is doubled against you. That's the entirety of both rules in isolation, and most tables apply them correctly when only one is in play.

Resistance and vulnerability are per-damage-type, not general. A creature resistant to fire gets no benefit at all against cold, radiant, or bludgeoning damage from the same attack. Each damage type on a single hit is checked against the creature's own list independently.

The trouble starts the moment a creature has both resistance and vulnerability to the same damage type at the same time, which is exactly what happens whenever a resistant character picks up a curse, a debuff, or a bad interaction with terrain that grants vulnerability to the one thing they're already resistant to.

Why They Don't Perfectly Cancel Out

The rules don't say "resistance and vulnerability to the same type cancel each other." They say both apply, in a fixed order, and that order matters because one of the two steps rounds down.

Here's the sequence a hit actually goes through:

  1. Immunity check. If the creature is immune to the damage type, the damage becomes 0 and nothing else below matters.
  2. Flat additions and subtractions. Any modifier that adds or removes a flat amount of damage is applied to the raw total first.
  3. One relevant resistance. Whatever damage is left is halved, rounded down.
  4. One relevant vulnerability. Whatever damage survives resistance is then doubled.

Run an actual number through it. Say the dragon's fire breath deals 25 fire damage to that resistant, cursed tiefling. Resistance applies first: 25 divided by 2 is 12.5, rounded down to 12. Vulnerability applies second, doubling what's left: 12 times 2 is 24. The tiefling takes 24 fire damage, not 25.

One point isn't going to swing many fights. But "one point lower than the raw damage, every time an odd number is involved" is a very different outcome from "no damage reduction or increase at all," which is what most tables assume they're delivering when they wave the two rules at each other and call it even. The rounding happens exactly once, during the resistance step, and because vulnerability comes after and doubles whatever that rounding left behind, the lost half-point never comes back.

The Verdict

Resistance and vulnerability 5e rules both apply to the same damage type, in a fixed order, rather than cancelling each other out. Resistance halves and rounds down first. Vulnerability then doubles what's left. The result lands close to the original damage, usually one point under on an odd number, but it is not a wash, and treating it as one quietly shaves damage off every resistant-and-vulnerable hit in the campaign.

Multiple Resistances to the Same Damage Type Don't Stack Either

A second, related resistance and vulnerability 5e mistake shows up whenever a character picks up resistance to the same damage type from more than one source. A tiefling with innate fire resistance who also drinks a potion of fire resistance, or a dwarf with poison resistance who also benefits from a cleric's Protection from Energy, doesn't get fire or poison damage quartered.

Multiple instances of resistance to the same damage type count as a single instance. The damage is still halved once, not halved and halved again. The same rule runs in reverse for vulnerability: two separate sources of vulnerability to the same damage type still only double the damage once, not quadruple it.

This is easy to miss because it feels like it should work the way advantage and disadvantage sources feel like they should stack (they don't, for the same underlying reason): more sources of the same named effect feels like it should mean more effect. It doesn't. The game checks whether the condition applies at all, not how many separate reasons produced it.

Resistance to One Type, Vulnerability to Another, on the Same Hit

A cleaner case, and one that trips up fewer tables, is a single attack that deals two different damage types to a creature that resists one and is vulnerable to the other. A young dragon's breath that deals both fire and poison damage against a creature with fire resistance and poison vulnerability isn't run through one combined calculation. Each damage type is evaluated on its own, start to finish, before the totals are added together.

So the fire portion gets halved and rounded down, the poison portion gets doubled, and the two results are summed. Nothing about the fire math touches the poison math, and nothing about having resistance to one type offsets vulnerability to the other. The "they cancel" instinct that misfires on same-type resistance and vulnerability has no foothold here at all, because there was never a shared number to cancel in the first place.

Common Sources of Resistance and Vulnerability in 5e

Resistance shows up on player character sheets constantly: racial traits (a dwarf's poison resistance, a tiefling's fire resistance), class features (a raging barbarian's resistance to bludgeoning, piercing, and slashing damage), and spells like Protection from Energy or the various resistance potions. It's common enough that most tables handle a single instance of it correctly without thinking twice.

Vulnerability is rarer on player characters and far more common on the monster side of the table. Skeletons take extra damage from bludgeoning weapons. Trolls take extra damage from fire. Certain undead are vulnerable to radiant damage. When a table runs into the stacking question at all, it's usually because a monster with a built-in vulnerability also got hit with a spell or curse that happens to grant the matching resistance or vulnerability on top of its stat block, and nobody paused to check whether the two were supposed to combine into something bigger than either rule actually produces.

Did the 2024 Rules Change This?

No. The halve-then-round-down, double-afterward sequence carried over unchanged from the 2014 rules into the 2024 Player's Handbook. If a table is arguing about whether resistance and vulnerability cancel out, that argument isn't the product of a recent rules change, the way weapon mastery or the Hide action's fixed DC actually did change between editions. This particular piece of math has read the same way for a decade.

Where an AI Game Master Actually Helps With This Rule

Resistance and vulnerability 5e math isn't a rule that fails because it's conceptually hard. It fails because, mid-combat, nobody wants to stop and do long division on a d20 roll's damage total while four other players are waiting for their turn. "Close enough, call it even" is a completely reasonable thing for a human table to default to under time pressure, even when it quietly shaves a point or two off the right answer most nights.

That's the exact kind of arithmetic StoryRoll's AI Game Master doesn't skip. When a hit lands on a creature carrying both resistance and vulnerability to the same damage type, the narration runs the actual sequence, immunity check, flat modifiers, one resistance, one vulnerability, instead of defaulting to a shortcut that feels right but isn't. The combat still plays out from the table's choices: what the players attack, what damage type their weapons and spells deal, whether anyone bothered to curse the dragon's rider with vulnerability in the first place. What doesn't happen is a quiet, repeated rounding error nobody ever goes back to check.

⟡

Frequently Asked Questions

Do resistance and vulnerability cancel out in 5e?

Not cleanly. Both apply, in a fixed order: resistance halves damage and rounds down, then vulnerability doubles whatever is left. Because the halving step rounds down, the result usually lands one point below the original damage instead of landing back on it exactly.

Do multiple resistances to the same damage type stack in 5e?

No. Multiple instances of resistance to the same damage type count as a single instance. A character with racial fire resistance and a ring of fire resistance still only halves fire damage once, not twice.

What is the order of operations for 5e damage resistance and vulnerability?

Immunity to the damage type is checked first and ends the calculation if it applies. Then any flat addition or subtraction to the damage total is applied. Then one relevant resistance halves what's left, rounded down. Then one relevant vulnerability doubles what remains.

What happens if an attack deals two different damage types and a creature resists one but not the other?

Each damage type is evaluated on its own. If an attack deals separate fire and acid damage, resistance to fire only halves the fire portion. The acid damage goes through at full value, because resistance to one damage type never touches a different one.

Did the 2024 D&D rules change how resistance and vulnerability work?

No. The core math carried over unchanged: halve and round down for resistance, double for vulnerability, applied after flat modifiers and before nothing else. The 2024 Player's Handbook didn't touch this calculation.

What are common sources of resistance and vulnerability in 5e?

Resistance commonly comes from race (a dwarf's poison resistance, a tiefling's fire resistance), class features (a raging barbarian's resistance to bludgeoning, piercing, and slashing), and spells like Protection from Energy. Vulnerability shows up far more often on monster stat blocks than on player characters - skeletons take extra damage from bludgeoning weapons, trolls take extra damage from fire, and some undead are vulnerable to radiant damage.

Resistance and vulnerability sit next to a handful of other combat rules that look like simple arithmetic and turn out to have a fixed order hiding underneath: temporary hit points, critical hits, and advantage and disadvantage all reward knowing the exact sequence instead of the rule-of-thumb version, and all of them get easier to run once the sequence stops being a guess.

S

Written by StoryRoll

Founder of StoryRoll. Building AI-powered tabletop RPGs.

Share:Share on X

Related Posts