Guild Wars 2

The issue of condition damage is really more “overload” than anything else.
Conditions are number of conditions applied x damage vs number of conditions you can remove in a certain amount of time to avoid that damage.

Overload comes when the conditions you remove do not adequately remove damage because you removed a “cover” or “lesser priority” condition.

SOLUTION: If possible given coding, allow players to have a panel which they can set that ranks each condition in terms of removal priority. You could choose to remove torment over confusion or burning over bleeding. Of course, you wouldn’t necessarily know what characters you would face in a fight. Likewise, it wouldn’t give you more condition removal just more control over what is removed.

The system would ONLY work in WvW and PvP because you simply don’t know what to predict. In PvE (which I do little of), it may be broken because you would just reset your priorities to remove the big condition of a mob which you would know ahead of time what it is. That assumes PvE has “cover conditions” which I am not sure of the fights to know one way or another.

You would need to ensure that you couldn’t reset the priorities easily keep by keep or fight by fight (which could help make it fair I suppose for PvE too). You may have to go back to a trainer (even if it is free) in your main city to reset etc etc.

Bombsaway.7198:

The issue of condition damage is really more “overload” than anything else.
Conditions are number of conditions applied x damage vs number of conditions you can remove in a certain amount of time to avoid that damage.

Overload comes when the conditions you remove do not adequately remove damage because you removed a “cover” or “lesser priority” condition.

SOLUTION: If possible given coding, allow players to have a panel which they can set that ranks each condition in terms of removal priority. You could choose to remove torment over confusion or burning over bleeding. Of course, you wouldn’t necessarily know what characters you would face in a fight. Likewise, it wouldn’t give you more condition removal just more control over what is removed.

The system would ONLY work in WvW and PvP because you simply don’t know what to predict. In PvE (which I do little of), it may be broken because you would just reset your priorities to remove the big condition of a mob which you would know ahead of time what it is. That assumes PvE has “cover conditions” which I am not sure of the fights to know one way or another.

You would need to ensure that you couldn’t reset the priorities easily keep by keep or fight by fight (which could help make it fair I suppose for PvE too). You may have to go back to a trainer (even if it is free) in your main city to reset etc etc.

I will support this when they allow me to choose which boon to steal or burn.

This assumes all conditions are meant to be balanced, though.

What if they’re not? Then players always prioritizing the most damaging damage conditions first is a problem, because that condition is supposed to be more dangerous, not less.

In general though, interesting idea. Dunno how their database is set up, so this might be tricky.

This wouldn’t fix anything, it’d just introduce new problems. If you accidentally prioritize bleeding, for example, which generally is easy to at least apply one stack of often, all of a sudden you might not take much bleeding damage, but you are permanently affected by every other condition. Not to mention professions like Engis who can put out confusion, bleeding, and burning all at once.

Bunkers can now remove Poison constantly, which was one of their biggest counters to keep from never dying.

People who have low condition removal still have issues, because removing one condition all the time isn’t much better than what is going on now, and professions who are good against conditions become even better (Necromancers, for example, have a removal on a 10s CD that right now is weak, but the ability to remove a certain condition whenever we wanted would be really good).

It just introduces too many problems without actually fixing the ones you want. If you want certain conditions to be removed, they need to introduce more removals that are condition specific instead.