Weaknesses!?


Rules Discussion


Can someone explain to me where in the Damage Rules it explains where multiple weaknesses can not be trigger if you deal multiple types of damage? As far ashow i read "Instant of Damage" is that ever damage is it's own Instant meaning you need to go through


Here you go. Weakness

The last two sentences of paragraph 2 seem to be what you are looking for,


1 person marked this as a favorite.

I don't think it says that at all, It speaks about not applying multiple weaknesses to the same TYPE of damage. Specifically about abilities that trigger both a material weakness and a damage weakness.

Player Core pg. 408 Weakness wrote:
If more than one weakness would apply to the same instance of damage, use only the highest applicable weakness value. This usually only happens when a creature is weak to both a type of damage and a material or trait, such as a cold iron axe cutting a monster that has weakness to cold iron and slashing.

Instance pretty much means each individual damage type. This behavior is further explained under resistances aswell where a single resistance can apply to several damage types at the same time. Such as Physical resistance stating that any physical damage is reduced, So an attack dealing both slashing and piercing gets reduced twice.

or in the case of All-Damage resistance

Player Core pg. 408 Resistance wrote:
It's possible to have resistance to all damage. When an effect deals damage of multiple types and you have resistance to all damage, apply the resistance to each type of damage separately. If an attack would deal 7 slashing damage and 4 fire damage, resistance 5 to all damage would reduce the slashing damage to 2 and negate the fire damage entirely.


We would need to look up damage instances, to better understand how the game is defining it, but I think NorrKnekten might be correct.

The example given is a cold iron axe (which deals slashing damage) hitting a creature with weakness to cold iron and slashing. That axe dealing damage is only one instance of damage, and thus only activates the greater of the weakness to cold iron or slashing, you don't get both on a single damage instance.

What's slightly unclear to me at this time, is if you have the same axe with fire damage rune on vs a creature with weakness to slashing (5), cold iron (10), and fire (6).

I think the axe's physical damage counts as one damage instance, and the fire counts as a separate instance (but I'm not 100%).

Thus the axe should deal an extra 10 damage for cold iron weakness and an extra 6 for fire damage weakness.


Wasn't there a part of the Damage Rules where each different Damage Type is it's own check/Go through the steps of Damage Rolls again? I know this is a thing but I can not find the rules for it and i know they use to exist unless I am going insane which I could be.


Pathfinder Roleplaying Game Superscriber; Pathfinder Starfinder Adventure Path, Starfinder Roleplaying Game, Starfinder Society Subscriber

So, there isn't a formal definition of "instance of damage", in the book.

There is the symmetry with resistance, and Resist All showing that each damage type is addressed separately.

And there was this confirmation way back in the PF2 playtest that weaknesses really work that way. The playtest was working with the same rule as the release for this, specifically, so I still consider it valid.

So for the original question

Quote:
Can someone explain to me where in the Damage Rules it explains where multiple weaknesses can not be trigger if you deal multiple types of damage? As far ashow i read "Instant of Damage" is that ever damage is it's own Instant meaning you need to go through

The answer is simply "they don't say that, and it's been confirmed that they don't mean that since before day 1".

There are edge cases that are unclear, because of the lack of a formal definition of "instance of damage". And I'd like for that to be cleared up. But this isn't one of them.

Envoy's Alliance

Pathfinder Rulebook Subscriber

It would make sense if we are talking about multiple types of damage, like a lot of Tree creatures are weak to both axes and fire, so if you use a battle axe with a flaming rune, they would be weak to BOTH the slashing damage of the battle axe and the fire damage of the flaming rune. I think the provision is to prevent them from taking DOUBLE weakness to the fire damage of the Flaming Battle axe. Eg: the weapon normally deals 1d8+strength Slashing and 1d6 Fire,and the weakness in both cases is 5, they would take 1d8+5+strength slashing and 1d6+5 Fire, not 1d8+5+strength slashing and 1d6+5+5 fire.


Wait so why would Weakness only trigger once? IF Resist all effects reach damage type then wouldn't Slashing 10 and Fire 5 Weakness trigger both from the Fire Rune Greataxe mentioned above? For an additional 15 damage, that seems odd that if you had Resist 10 all you would negate any damage rune because 10 is greater then 6 and then this also makes Elemental Instinct (Assuming Fire/Energy Damage) Barbarian weaker because your Rage damage is now reduced by 10 as well as your normal physical attack by 20 instead of just 10 if it was all one damage type. this doesn't sound right.


And as was pointed out in that old thread, Mark's conclusion does not match the written rules. In order to get the behavior he describes, there are one or two "missing steps" that do not exist in the RaW.

Imo, the "community norm," which is mostly due to Foundry running it w/ that old thread's stated output, does not match RaW. Imo, it's written so that each swing is one "instance" and should only apply the single highest weakness/resistance.

This is especially obvious with "combine these hits for sake of weakness/ resistance" actions like Flurry of Blows. The procedure for getting to "community norm" of both separating & combining by type is some serious nonsense in the "each type is its own instance" ruling.

.

As brief as I can, aside from the wording of the Flurry-style abilities, the main evidence against that ruling is weak/resist all text, which specifically say that you apply that for every damage type in the swing.

But in the "norm" ruling, you already do that.

.

You have to decide if you really want to go against the grain on this issue. Imo the unused "each swing is an instance" version is also better in terms of game design / consequences upon the system, but the "every type is an instance" ruling is very deeply ingrained in the community. And if you use Foundry, I straight up say it's not worth whatever effort would be required to alter that code.

In play, this ruling most seriously effects martials once elemental runes come online. There are a lot of opponents with wide swaths of resistance (but not resist all), and they get hella screwed by all the resistance stacking.

Even the Monk, who first has to get abnormally lucky to hit both Flurry hits, and even then, it rare for a 2d6 element to overcome 10 resist or meaningfully contribute.

I do not want to downplay that this actually does make a big difference. Basically any encounter with some uncommon crystal adjacent foes is much harder than written, as the multi-resistance stacking will cut martial hits down to way less than half their normal damage.


Trip.H wrote:

And as was pointed out in that old thread, Mark's conclusion does not match the written rules. In order to get the behavior he describes, there are one or two "missing steps" that do not exist in the RaW.

Imo, the "community norm," which is mostly due to Foundry running it w/ that old thread's stated output, does not match RaW. Imo, it's written so that each swing is one "instance" and should only apply the single highest weakness/resistance.

This is especially obvious with "combine these hits for sake of weakness/ resistance" actions like Flurry of Blows. The procedure for getting to "community norm" of both separating & combining by type is some serious nonsense in the "each type is its own instance" ruling.

.

As brief as I can, aside from the wording of the Flurry-style abilities, the main evidence against that ruling is weak/resist all text, which specifically say that you apply that for every damage type in the swing.

But in the "norm" ruling, you already do that.

.

You have to decide if you really want to go against the grain on this issue. Imo the unused "each swing is an instance" version is also better in terms of game design / consequences upon the system, but the "every type is an instance" ruling is very deeply ingrained in the community. And if you use Foundry, I straight up say it's not worth whatever effort would be required to alter that code.

In play, this ruling most seriously effects martials once elemental runes come online. There are a lot of opponents with wide swaths of resistance (but not resist all), and they get hella screwed by all the resistance stacking.

Even the Monk, who first has to get abnormally lucky to hit both Flurry hits, and even then, it rare for a 2d6 element to overcome 10 resist or meaningfully contribute.

I do not want to downplay that this actually does make a big difference. Basically any encounter with some uncommon crystal adjacent foes is much harder than written, as the multi-resistance stacking will cut martial hits down to...

Absolutely nowhere is it written that "each swing is 1 instance".

That's where this whole debacle, trailing back to the early days of pf2 release, stems from.

Apart from that place, "instance of damage" is not referenced anywhere else, leaving all of us to either make our own ruling on it, or go by the only dev input on that.

Both rulings are ok, as long as the GM communicates it, but "raw wise" there is no clear answer.

Community / Forums / Pathfinder / Pathfinder Second Edition / Rules Discussion / Weaknesses!? All Messageboards

Want to post a reply? Sign in.
Recent threads in Rules Discussion