Cause when in game i had 9 stacks of bleed and 1 stack of vulnerability. I used shake it off thinking it would remove the 9 bleed at 90 dmg per tick, it instead removed the 1% dmg increase from invulnerability. And it really confused me. It seemed idiotic for it to work like this, but i thought maybe it was cause the vulnerability was the first in the list. But it’s happened to me another time, when the conditions were in inverse positions in the list but it was 6 stacks of bleed. It still removed the 1 stack of vulnerability.
So how does the condition removal priority really work, and does it take into account stacks of intensity and duration? Surely intensity would take priority over duration, as the DPS of a condition like burning would be static, compared to the DPS of 25 bleed or potential DPS of 25 vulnerability? As well as stacks and duration changing removal priorities of conditions, like the 9 bleed vs 1 vulnerability? Let alone the priorities of the conditions themselves at base? (eg. immobilize vs 1 bleed)
Um I always thought it worked much like it did in GW1 – that being the most recent (or last in the row/list) applied gets removed, I guess I could be wrong….
Since when did this business of being a hero become being a business?
’Conditions are a type of effect that can be inflicted on foes using of skills and related traits. Most conditions inflict damage over time and ignore armor and other effects that reduce damage, such as protection. For effect stacking, most conditions stack in duration while bleeding and confusion stack in intensity. Conditions can be removed by condition removal. For generic condition removal, the most recently applied condition or conditions will be removed first. The condition is removed independent of the intensity, so 3 stacks and 25 stacks of bleeding are equivalent when considering condition removal. ’
