GM Guide: Adjudicating Weakness and Resistance Rules After Spring 2026 Errata

The phrase "instance of damage" appeared in Pathfinder's weakness and resistance rules for years without ever being formally defined. The errata notes it plainly: "The rules on weakness and resistance refer to an 'instance' of damage, but that term isn't defined." That gap produced years of inconsistent rulings at tables, and when Paizo added a clarification to the Pathfinder Player Core FAQs earlier this year, it triggered a large community response, much of which was negative — making it clear the issue couldn't be resolved without actual errata to the text. What followed was, by Paizo's own description, major surgery on that section of the rules.

What Changed: The Core Rule

Under the revised rules, each weakness and resistance can trigger only once during an effect, such as a single Strike or spell. A creature with weaknesses to both a damage type and a special material can have them both activated at the same time. That second point is crucial and easy to miss: the once-per-effect restriction governs individual weaknesses and resistances independently, not the total count of all weaknesses applying to a single Strike. A cold iron axe against a monster vulnerable to both cold iron and slashing still applies both weaknesses — you just can't double-dip on the same weakness through two separate sources of the same type within one effect.

In a substantial change from both the original rules and earlier interim guidance, resistance to all damage now also applies only once. The errata also covers what happens when multiple resistances could apply to the same damage, as often happens when a character has both resistance to one type of damage and resistance to all damage. If those two resistances overlap on the same damage instance, you use only the highest applicable value rather than stacking them.

How "Instances" Actually Work in Play

Think of each distinct source of damage on a single Strike as its own instance. The Foundry community's deep-dive example using a terotricus illustrates this cleanly. Take a character hitting with a +2 striking holy flaming cold iron battleaxe, where the damage roll results in 4 fire damage from the flaming rune, 7 spirit damage from the holy rune, 16 slashing damage from the cold iron battleaxe, 3 cold damage from one spell, and 6 cold damage from a second cold spell.

Breaking that down under the new rules:

• The holy trait adds damage from weakness to holy; it applies to the whole Strike and triggers only once.
• The cold iron battleaxe is where the "instance of damage" rules apply directly: it deals both slashing damage and qualifies as cold iron, so you apply the cold iron weakness and not the slashing weakness, since cold iron is the higher value.
• The two sources of cold damage come from different spells, so each triggers the cold weakness individually.
• The fire damage from the flaming rune is negated entirely by the creature's fire resistance.

The practical takeaway: one rune, one spell effect, one weapon property — each is its own instance. Each instance interacts with applicable weaknesses and resistances independently, and each specific weakness or resistance fires no more than once per effect.

The GM Tiebreaker Rule

Paizo's designers are still working on a comprehensive clarification entry to cover the full process of applying immunities, weaknesses, and resistances, but that work has been delayed because it is an extremely complicated and time-consuming process. In the meantime, the official guidance from Paizo is a golden rule for GMs: favor the attacker when applying weaknesses, and favor the defender when applying resistances, if the process isn't clear from the existing erratum text. Engrave that on your GM screen. It is the cleanest possible resolution principle for the edge cases this errata doesn't yet cover explicitly.

The Order of Operations Hasn't Changed

It is worth emphasizing what the Spring 2026 errata did *not* change. The sequence for applying defenses remains the same: immunities first, then weaknesses, then resistances third. If a creature is immune to fire, the fire damage never exists to trigger anything else. If a weakness applies, add that bonus damage before resistances reduce the total. Running these in the wrong order is one of the most common table errors, and the new errata doesn't patch it — so double-check your sequencing before anything else.

Where to Find the Updated Text

The Spring 2026 changes appear in the Pathfinder FAQ page under sections for Pathfinder Player Core, Pathfinder GM Core, Pathfinder Player Core 2, and Pathfinder Guns & Gears (Remastered). These changes will also appear in the next printing of Starfinder Player Core. If you run from physical books, check the FAQ page before every session until your books are updated — the distinction between old and new rulings on stacking resistances is significant enough to affect encounter math in creatures with high resistance values.

Why This Revision Matters for Encounter Design

The practical impact runs both directions at the table. Players running heavily rune-stacked martial characters and casters who layer cold or fire damage onto Strikes will find their output is more predictable now — each added damage type interacts with the target's statblock cleanly, without the ambiguity that previously let some GMs collapse multiple sources into a single resistance check. The latest revision came after significant negative feedback from the community, signaling that Paizo is genuinely listening to how its rules land in actual play. The intent, as Paizo stated, was to make the rules less vague, easier to apply, and more in line with how most GMs were already intuitively running weaknesses and resistances. For the majority of tables, that intuition turns out to have been correct all along.