A Practical GM Guide to Pathfinder Weakness, Resistance, and Immunity Rulings

If there's one argument that erupts at more Pathfinder 2E tables than any other, it's this: does that resistance apply once, or does it apply to each damage chunk separately? The Remaster complicated things further by swapping out good, evil, lawful, and chaotic damage for holy, unholy, spirit, void, and vitality, leaving GMs scrambling over whether older stat blocks even interact correctly with the new damage vocabulary. Paizo's Spring 2026 errata addressed instances of damage more directly than any previous update. This guide translates that into a workflow you can run at the table in real time.

The Single Question That Settles Most Arguments

Before you touch the dice result, ask one question out loud: "Is this one effect or multiple effects?" That single prompt, drawn directly from Paizo's Spring 2026 errata language on damage instances, resolves the majority of resistance and weakness disputes before they turn into a full-table standoff. One effect means you process weakness and resistance once, total, for that effect. Multiple effects means each gets its own pass.

This distinction sounds simple but breaks down fast in practice. A Magus triggering Spellstrike fuses weapon and spell damage into a defined single effect. A player who casts a fire spell and then independently triggers a wand on the same turn has generated two distinct effects. The rule is the same; only the situation changes.

The Four-Step Ruling Workflow

Step 1: Identify the Effect

Determine whether all the damage in question comes from a single effect or multiple effects before resolving anything. An attack that includes weapon base damage plus attached magic damage that the rulebook treats as part of the attack is one effect. Two spells cast on the same turn are two effects. Announce the determination before the dice hit the table. Saying it out loud before the roll prevents the retroactive argument that always arrives after an unexpected crit.

Step 2: Combine Same-Type Damage Where Appropriate

If multiple components of the same effect deal the same damage type, say two electricity sources explicitly produced by the same spell, combine them into a single total before applying resistance or weakness. This prevents the defensive math from firing twice against what is functionally one source. The Spring 2026 errata language favors once-per-effect processing, and combining same-type components within an effect is the mechanical expression of that principle.

Step 3: Apply Immunities, Resistances, and Weaknesses in a Single Pass

Once you've established the effect and combined totals, resolve immunities first, then weaknesses, then resistances, in that order. This sequencing is confirmed in the Archives of Nethys and consistent with the core rules. If an effect contains multiple damage types (slashing plus fire, for instance), treat each type as its own component and run weakness and resistance for each independently, but still only once per effect for that specific type. A creature with fire resistance 10 facing a flaming longsword strike does not apply that resistance to the whole attack; it applies fire resistance once to the fire component, and the slashing component is processed on its own terms.

Step 4: Announce the Ruling and Move On

Unresolved disagreements stall games. Adopt a "tentative ruling" posture: announce the ruling with a one-sentence rationale, invite a brief flag if someone disagrees, and then move initiative forward. Save lengthy appeals for after the session. Keep a written note of each edge-case ruling so you apply the same logic consistently in later encounters with the same creature type. The goal is not winning the argument; it's keeping momentum.

The Three Most Common Table Arguments (and How to Rule Them)

Argument 1: The Flaming Weapon and Partial Resistance

A fighter swings a +1 striking flaming longsword at a fire-resistant demon. The question that derails the game: does the demon's fire resistance reduce the whole attack, or just the fire portion? The ruling is clean. Slashing and fire are separate damage types within a single effect. Apply resistance to the fire component only. The slashing goes through at full value. In practice: 12 slashing + 7 fire against fire resistance 5 becomes 12 slashing + 2 fire, total 14. Write that math out loud. It ends the debate immediately.

Argument 2: Short Sword Plus Alchemist's Fire

This is where the "one effect or multiple" question earns its keep. If a character delivers an alchemist's fire alongside a Strike in a way that the rules treat as a separate alchemical instance, process that fire damage independently, with its own resistance check. If the extra fire is explicitly fused into the weapon's Strike as a unified magical property, combine the fire totals and apply resistance once. Paizo's forum discussions on this scenario confirm the distinction: a delivered alchemical item and a weapon property that generates additional damage as part of the attack are mechanically different. When in doubt, check whether the rules text describes the extra damage as part of the Strike or as a separate effect.

Argument 3: Spellstrike and the Unified Effect Problem

A Magus using Spellstrike channels a spell through a weapon attack, and the rules explicitly define Spellstrike as a single combined effect. If the weapon and spell both deal the same damage type, combine those totals and apply the target's resistance once. If a second, separately triggered effect (a wand discharged independently, not as part of the Spellstrike) adds damage on the same turn, it is a distinct effect and earns its own resistance calculation. The fact that damage lands simultaneously does not make it a single effect. Timing is not the test; the rules definition of the effect is.

What the Remaster Changed, and What Didn't

The Remaster's biggest contribution to GM confusion around damage defenses is the removal of good, evil, lawful, and chaotic damage and their replacement with holy, unholy, spirit, void, and vitality. A pre-Remaster vampire stat block listing "weakness to good damage" no longer maps cleanly onto a post-Remaster session. Spirit damage targets the spiritual essence of a creature regardless of possession. Void damage harms only living creatures. Vitality damage harms only undead. These are not cosmetic changes; they affect which creatures take damage at all.

The practical ruling for GMs running pre-Remaster content: convert the old damage type to its closest Remaster equivalent (typically holy for good, unholy for evil), note it as a table conversion, and apply it consistently. What has not changed is the resolution order: immunities first, weaknesses second, resistances third. The four-step workflow holds across both eras; only the damage type vocabulary shifted.

The Two-Line GM Script for Every Contested Roll

Use these two lines verbatim or adapt them to your voice.

Before the roll: "This attack will include X and Y. I'm treating them as [one effect / two effects]."

After the roll: "Total X fire, Y slashing. I'm applying resistance to [the combined fire / each instance separately]. Final damage to the target: Z."

Delivering this consistently makes your reasoning audible before anyone has cause to dispute the outcome. It's a small habit that eliminates a disproportionate share of table friction.

Session Zero Script

Read or paraphrase this before the campaign starts: "When it comes to weakness, resistance, and immunity, this table uses an effect-first approach. Before each contested roll I'll call out whether I'm treating the damage as one effect or two, and I'll resolve immunities before weaknesses before resistances. If you think I've got it wrong, flag it briefly and I'll note it; we won't pause mid-fight to rule-lawyer it. Remaster damage types like holy, spirit, and void will follow the Remaster stat blocks. If we're running older content I'll name the conversion I'm making so it's transparent. The goal is a ruling you can predict, not one you have to fight for."

That paragraph, delivered once at session zero, sets the expectation that rulings are principled, transparent, and final for the session. It also signals to your players that the GM has thought this through, which, more than any specific ruling, is what actually keeps combat moving.