Guild Wars 2

i was thinking about that, and felt the need to write it down. So, at the moment, we know it’s hard to apply your full potential of bleeding stacks on one player , and that make people go for condition damage over condition duration (in pvp at least, for pve condition duration is perfectly fine as only few monsters clear conditions). what if we just made bleeding stacks harder to remove? and by that i mean once a certain cap of bleeding is reached (8/10, or more…) bleeding will start to full a new slot, till the cap is reached, so we could basically have 2 times 10 stacks of bleeding instead of 1 time 20 stacks. this idea i got it real quick, just wanted to share, feel free to criticize, after all we’re here for that ^^. (and be MEAN, i love it when you call me names)

Ya know, this is a pretty good idea. As far as it ever getting implemented, I don’t know.

Bleeding caps at 25 stacks simply because the servers have to keep track on all bleeds on every thing at once. I’m not sure if making bleeding into separate stacks would be any easier to deal with.

Just to clarify, are you suggesting that it be possible to stack more than the currently allowable number of conditions, or simply suggesting that at some point they are treated as a new “stack” as far as cleansing comes. So for example it would take 2 condition cleanses (each cleansing one condition) to clear 20 bleeds, as they are treated as two stacks of 10.

ah yeah sorry i might not have been clear enough, well the idea would’ve been to keep the max stack at 25 but for it to be trated at a new stack. (but i didn’t think about server lag limiting the bleedings actually, so i dunno if that even is possible at the moment :/ )

the problem is when there are more ppl adding bleed
on event for eg. theres always 25 stacks and we barely do any dmg to the target
not sure how this problem can be solved or atleast lowered in some way
power builds are much better unless it’s small group of ppl where cond can do something when it comes to dealing dmg

The problem about this is what Colin Johanson said once (can’t remember which post was, but it was on this official forums): they have technical reasons to cap bleeds on 25. Every bleed a player put into an enemy (being another player or a mob) have information that the server need to keep like duration and damage, so they can’t rise up the limit there.

They were, however, looking for new ways of getting rid or, at least, rising up the cap but we don’t still have a word about that.

If anyone can remember where did he say this, link the topic to us

If server traffic is really the cause of bleed cap then how does a server keep track of might stacks with all the dmg stuff it changes, wouldnt it be better if the server was keeping track of each players individual’s bleed stack and limit might to 1 stack since condition is part of the main dmg type in the game and just allow each player to build their own 25 stack.

Anyway off topic there misleading title.

You dont actually need to make it like this but could keep 25 stack cap and say that condition removal can only remove X or XX amount from a stack like max 5 bleed max 5 confusion etc.

wiazabi.2549:

You dont actually need to make it like this but could keep 25 stack cap and say that condition removal can only remove X or XX amount from a stack like max 5 bleed max 5 confusion etc.

Confusion in general needs a rework since it triggers on a lot of things that it shouldnt, most of the base durations are way too long for pvp but just meh on pve and the damage difference is quite annoying (i dont get why they didnt go with the old form of each time confusion procs one stack goes away no matter the duration and kept the old damage in pvp, but in addition made mob movement cause ticks).

well i did think about just adding a cap to condi removal too. anyway forget about this post, this wasn’t a good idea ^^