(edited by RaynStargaze.6510)
priority for condition cleanse
I wish people had fewer condition cleanses. Poor prioritizing is probably the only reason why a condition Necro can get any kills at all.
I wish people had less range. People standing still next to my Greatsword is the only reason why a Guardian can get any kills at all.
FIFO. First in, first out.
If you look at your row of conditions, the right-most condition is the oldest, so that one gets cleansed first.
FIFO. First in, first out.
If you look at your row of conditions, the right-most condition is the oldest, so that one gets cleansed first.
FILO. First in, last out.
LIFO. Last in, first out.
http://wiki.guildwars2.com/wiki/Condition
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.
for example my mesmer can drop 8 stacks of confusion on someone and then attempt to cover up the confusion with other conditions such as bleeding, burning, vulnerability etc.
FIFO. First in, first out.
If you look at your row of conditions, the right-most condition is the oldest, so that one gets cleansed first.
FILO. First in, last out.
LIFO. Last in, first out.http://wiki.guildwars2.com/wiki/Condition
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.
for example my mesmer can drop 8 stacks of confusion on someone and then attempt to cover up the confusion with other conditions such as bleeding, burning, vulnerability etc.
^ Quoted for accuracy. It’s amazing how much misinformation is still floating around regarding condition removal.
The present system is good because it allows for skill on both ends (a condition build must think ahead and be able to “cover” his conditions, and his opponent has to watch so he knows which condition he’s getting rid of).
In addition, the current system makes it so that large bleed stacks are almost always cleared first, since they are usually constantly being refreshed.
Hmm so do you mean that reapplying a condition will move it up to the top of the removal queue even if the previous application has not yet expired?
Interesting. I didn’t know this before.
Does the interface get updated to reflect the new ordering, by the way? In other words, is it safe to always assume that the rightmost condition on your bar will always be removed first?
Also, I’m assuming boon removal will work in a similar fashion?
(edited by Kaon.7192)
Cleansing should have been more condition specific.
For sure a much bigger divide between bleed/burn/imob and vulnerability/weakness/cripple/poison/chill.
[if they made chill movement impairing worse and poison not last so long from certain attacks or weaker but stack in intensity/healing mitigation]
That’d give melee more life as their cripples aren’t eaten up like nothing. That’d make vulnerability stacking better in PvP since it won’t disapear at the swap of an attunement, that’d make weakness and chill decently reliable conditions for drawn out fights.
Cleansing should have been mainly built into traitline minor traits or innate to classes.
Forcing every spec to sacrifice for cleansing and means to deal with CC as a necessity is just limiting in this system GW2 threw our way. Major traits and utilities should be an extra shot at some cleansing, not the barebone necessary.
(edited by garethh.3518)
^yeah. That’s one of the things that makes warrior condi builds weak, it’s constant bleed application with little else to cover them, which almost guarantees it’ll be removed first