Guild Wars 2

I’d really like it if we could have a priority list per character on which conditions should be removed first, rather than the most recently applied conditions.

I’m sure everyone has had a moment where they have multiple conditions on them and want one specific condition removed, and removed the wrong condition instead. Personally, I always want to remove Confusion first because it forces me to either do nothing or get hurt for attacking.

The priority list would simply be a list with all 11 conditions displayed in it and a field in front of it with a number. The lowest numbered conditions get highest priority for condition removal, the highest numbered conditions gets lowest priority for condition removal.
You can enter a number from 1 through 11 to set priority for condition removal to your liking per character. By default, all conditions will be set to 11.

Example of a default priority list:

• (11) Bleeding
• (11) Blind
• (11) Burning
• (11) Chilled
• (11) Confusion
• (11) Crippled
• (11) Fear
• (11) Immobilized
• (11) Poison
• (11) Vulnerability
• (11) Weakness

In this example, all conditions are set to 11 and use default condition removal rules.

Example of a modified priority list:

• (4) Bleeding
• (11) Blind
• (4) Burning
• (3) Chilled
• (1) Confusion
• (5) Crippled
• (11) Fear
• (2) Immobilized
• (4) Poison
• (5) Vulnerability
• (5) Weakness

In this example, Confusion will always be removed first if it is present.
Bleeding, Burning and Poison are all set to 4, meaning it doesn’t matter which of the three gets removed first – default condition removal rules apply to them, after higher priority conditions.
The same goes for Crippled, Vulnerability and Weakness.
Fear and Blind are set to 11, meaning they take lowest priority and use default condition removal rules after all other conditions.

What do you guys think? Do you think this would be a good or a bad addition to the game if it were added, and why?

Could become an issue when laying down cover-conditions. For example, lay 5 stacks of confusion and then hit them with a long duration single bleed/poision/etc to keep them from being able to remove the confusion. It’s a valid tactic to be honest, and considering condition builds are still rather weak in groups this would amount to a nerf of some degree which really isn’t needed.

This would be extremely bad. Covering conditions is paramount to tactical play. What you suggest would more or less remove conditions from the PVP meta.

In GW1 the same existed, where you’d try to put a worthless condition over your valuable condition, while your opponent actually tries to remove the valuable condition before the cover condition can be applied. EG blind covered by poison for warrior shutdown, or covering backfire by a worthless hex for monk shutdown.

Hmm, I hadn’t even thought of such tactics being used, I’m totally gonna try this tactic out the next time I’m playing PvP. I see it’d be a bad thing to be implemented for PvP then, as well as for WvW. ExTribble is right to say this would essentially be a nerf to conditions in PvP.

Perhaps it could be a PvE-only thing? It’s not like NPCs apply conditions in a tactical way.

PurebladeProductions.4875:

Hmm, I hadn’t even thought of such tactics being used, I’m totally gonna try this tactic out the next time I’m playing PvP. I see it’d be a bad thing to be implemented for PvP then, as well as for WvW. ExTribble is right to say this would essentially be a nerf to conditions in PvP.

Perhaps it could be a PvE-only thing? It’s not like NPCs apply conditions in a tactical way.

Most bosses only have 1 condition as a gimmick mechanic. Those can usually be avoided by proper play.