Guild Wars 2

I can confirm, that they said they will try to improve it. But wont hold my breath for this becoming truth

Just raising the Condi stack cap would be an extremely significant improvement… But it still would be second tier to power in pve.

Axiom.6490:

I can confirm, that they said they will try to improve it. But wont hold my breath for this becoming truth

I can confirm they have been looking into this for over a year, and commented as such, with zero movement, adjustments, or progress on the matter.

The server load can’t stand the strain of 25 extra bleeds in a PVE dungeon limited to 5 people, but it has no problem handling 25 bleeds per person in a 50 v 50 engagment in WvW.

So logical.

I just afraid the crit dmg nerf is what they think that would improve condition in pve.

Wow I wasnt even thinking about that…. You are so gonna be right…. They would think about kitten kitten backwards like that.

Keelan.7498:

Yeah.. and make it so whoever has the highest cond. damage has first priority for dealing damage. And then whenever their durations/stacks run out, the other people in the party’s conditions would then take over. But when the person with the high condition damage attacks again theirs would get bumped back to the front. I hope that made sense :x

Makes perfect sense. Basically an optimization of condi damage and stack priority. This should be done, especially if the cap is never increased.

Keelan.7498:

Yeah.. and make it so whoever has the highest cond. damage has first priority for dealing damage. And then whenever their durations/stacks run out, the other people in the party’s conditions would then take over. But when the person with the high condition damage attacks again theirs would get bumped back to the front. I hope that made sense :x

This is already the case for Burning and Poison. Maybe it will be easy for devs to apply the same feature to Bleed, Confusion and Torment.

Pregnantman.8259:

Keelan.7498:

Yeah.. and make it so whoever has the highest cond. damage has first priority for dealing damage. And then whenever their durations/stacks run out, the other people in the party’s conditions would then take over. But when the person with the high condition damage attacks again theirs would get bumped back to the front. I hope that made sense :x

This is already the case for Burning and Poison. Maybe it will be easy for devs to apply the same feature to Bleed, Confusion and Torment.

It is most certainly not the case as of today. For any conditions.

I have a video on burning if you would like proof. Single stack conditions are fist come first serve. Some 0 condition damage staff ele will have his full burn tick before mine will as long as he put the burn in first.

The wiki used to claim there was some priority, or the highest condi damage was used etc, but that is not the case.

I was able to came up with that from two threads dedicated to the issue.

https://forum-en.gw2archive.eu/forum/game/players/How-does-stacking-Burning-effect-Damage

https://forum-en.gw2archive.eu/forum/game/gw2/How-does-burn-work

These are my sources, but if you have the video I would like to see it. Visuals always beat threads :P

Pregnantman.8259:

I was able to came up with that from two threads dedicated to the issue.

https://forum-en.gw2archive.eu/forum/game/players/How-does-stacking-Burning-effect-Damage

https://forum-en.gw2archive.eu/forum/game/gw2/How-does-burn-work

These are my sources, but if you have the video I would like to see it. Visuals always beat threads :P

That is discouraging I really hoped it wasn’t like what you said. Ah well, thank you for providing the video and taking time to make it.

Pregnantman.8259:

That is discouraging I really hoped it wasn’t like what you said. Ah well, thank you for providing the video and taking time to make it.

Yes it is rather unfortunate…. Conditions are in fact in the worse spot possible for the full build condition player in dungeons and open world. Since they work so well in pvp it is hard to complain, but sometimes I like to cool off in PVE, and as a result I swap builds all the time and have a bag full of “other” gear.

The other sad thing is so many small tweaks could fix this problem, at least in 5 man groups, but rather than make those, try those, or even talk about those, they have continued to ignore the problem completely.

Such as raising the cap to 50 bleeds in dungeons only… it wouldn’t make condition builds overpowered or even desired, but at least we wouldn’t feel like we need to drop party when we run into another condition player. But again, every 6-8 months we get a red post saying they are working on it…

Rennoko.5731:

Axiom.6490:

I can confirm, that they said they will try to improve it. But wont hold my breath for this becoming truth

I can confirm they have been looking into this for over a year, and commented as such, with zero movement, adjustments, or progress on the matter.

The server load can’t stand the strain of 25 extra bleeds in a PVE dungeon limited to 5 people, but it has no problem handling 25 bleeds per person in a 50 v 50 engagment in WvW.

So logical.

They don’t you know, have a separate server for every single instance someone opens. There’s probably 100 5-man instances on one server, and then one server for a WvW map.

Use your brain first next time.