Guild Wars 2

Seriously, why isn’t there any priority when dealing with skills that cast a boon removal or condi removal. Most condi removals in the game remove only 1 condi, and mostly it seems they remove a kittenty filler condi like vulnerability. I’m looking specifically at immobolize. You get immobolized for 3-4 seconds (extremely easy to do now), and then get 2-3 condis put on you. Now, if you’re like me and run 3 seperate 1 condi removals, you use every single removal hoping to get rid of immobolize! Except it removes everything except immobolize! And now you’re dead from the burst dps!

So serious question, why no priorities?

I agree. Especially since Larcenous Strike only steals one boon now. It’s pretty much a bad joke. They made a skill to be effective at fighting boon bunkers, then promptly nerfed it in a way that makes it absolutely useless at killing boon bunkers. (They could have upped the initiative cost to reduce spamming it, instead they made it impotent at its utility role, encouraging users to spam it even more just to make ends meet.)

instead of priority, could we set it ourselves what conditions we want to be removed?

how about we introduce a new gui menu.
lets call it

the “Boons & Conditions Management” menu
select what boons to strip first, you set your own priority order
1. stability
2. protection
3. …
etc.

select what conditions you want to remove first,
set your own priority order
1. immobilize
2. burning
3. poison
4. bleeding
5 …

etc

otherwise, just use a

first in, last out
last in, first out

system.

Lopez.7369:

I prefer the current system. As a necromancer, it takes a lot more skill and thought to remove stability — easily the most important boon to corrupt — because it’s last on the priority list. That’s much more interesting than simply corrupting it every single time, no questions asked.

It’s good on that scenario. But on the condi removal side of things, when a typical condispam class can unload a plethora of conditions, there also has to be some sort of priority in removing the most dangerous condi first since condition removal is not that easy to get by on most builds. Because AFAIK, condi removal works on a FIFO sort of mechanic. I honestly don’t know. But if I want to use condi removal, it’s usually because I want to remove immob, chill, a minute stack of burn or 25 stacks of bleed and not Vulnerability.

Lopez.7369:

Every boon-removing ability has a priority system.

For example, Corrupt Boon prioritizes stability last, so good necromancers have to wait until someone has only five boons to corrupt.

On the other hand, Larcenous Strike prioritizes might last, so thieves have to work through a few boons before they can steal might.

I didn’t know they worked off a table, but after some digging I think I can establish that Larcenous Strike is not on the same table as Bountiful Theft. I’m saying this because when I’ve used LS on Dredge Disaggregator’s I was always stealing the Might and Swiftness instead of the Protection.

Deimos Tel Arin.7391:

instead of priority, could we set it ourselves what conditions we want to be removed?

how about we introduce a new gui menu.
lets call it

the “Boons & Conditions Management” menu
select what boons to strip first, you set your own priority order
1. stability
2. protection
3. …
etc.

select what conditions you want to remove first,
set your own priority order
1. immobilize
2. burning
3. poison
4. bleeding
5 …

etc

otherwise, just use a

first in, last out
last in, first out

system.

I’ve always wanted something like the first thing you said. currently condis work as the second way you mentiond, but it sucks.

Darek.1836:

Deimos Tel Arin.7391:

instead of priority, could we set it ourselves what conditions we want to be removed?

how about we introduce a new gui menu.
lets call it

the “Boons & Conditions Management” menu
select what boons to strip first, you set your own priority order
1. stability
2. protection
3. …
etc.

select what conditions you want to remove first,
set your own priority order
1. immobilize
2. burning
3. poison
4. bleeding
5 …

etc

otherwise, just use a

first in, last out
last in, first out

system.

I’ve always wanted something like the first thing you said. currently condis work as the second way you mentiond, but it sucks.

It does

ooo the current system is

first in, last out
last in, first out

system.

is it?