| Markus Reese |
| 1 person marked this as a favorite. |
Krispy, the part being missed is there are not three parts of damage. There are two aspects of damage and a condition applied at the time of trigger. No damage occurs from the persistent. It is [Physical damage] + [Energy damage] + [Condition]
This is verifiable RAW which explicitly state that persistent damage is a condition. The condition is applying damage, not the one who caused said condition. This is why an ability that only causes a condition cannot trigger the spell because no attack damage has occured.
The damage from the persistent only occurs at the end of the affected party's turn, not at the time of the trigger which is why resistance cannot be applied to it. It has not happened to be part of the trigger to be counted with the RAW explicit definition of what the resistance applies to, specifically the trigger damage which does not include the persistent since the persistent has not done any damage.
It isn't saying persistent damage isn't damage, but it is not attack damage.
If a bull rush is used to push somebody from a bridge, the fall damage is not attack damage. Same with persistent damage. You are not being hit with the persistent damage. You have a condition, such as you have been lit on fire. You are not receiving an attack, you are burning.
Such as if I use a match to light a fire, I am not continuing to add matches to keep it burning. When an attack is done that deals a condition damage, you are burned by that which ignites it, but not the fire which doesnt yet exist. It just has started, but has not actually harmed you yet.