Guild Wars 2

There are three conditions that stack intensity.
1. Bleeding
2. Confusion
3. Vulnerability

My suggestion is this: If a group is able to maintain 25 stacks for a set amount of time the stacks get removed and replaced with another powerful debuff. For example 25 stacks of bleeding maintained for 7 seconds turns into Gash. Gash causes something like 250 damage every second for 25 seconds and doesn’t stack. While Gash is active it bleed has a 25% chance to stack. The others would work in a similar fashion.

The idea is that getting to 25 stacks should be an objective rather than being a waste.

personally I would prefer they split it to personal condition stacks so having more than 1 condition giver in a team isn’t wasted.

I would like stacks to be personal as well.

well the most confusion i have stacked on as a single mesmer by myself is 10 stacks of confusion but if i have a ranger with me i can slam on 25 with the help of TW. the enimies take close to 5k in damage from confusion. in my mind if my party is able to hold 25 stacks of conditions nothing survies from the damage out put and condition damage.
but if you want a super buff from 25 stacks of a condition then what about the dragons. players can easly get 25 stacks of a conditions and the dragons thanks to the update and guesting abuse would be just way to over powerd in my opinnion.
just my 2 cents

Kenage Achalarus.4276:

well the most confusion i have stacked on as a single mesmer by myself is 10 stacks of confusion but if i have a ranger with me i can slam on 25 with the help of TW. the enimies take close to 5k in damage from confusion. in my mind if my party is able to hold 25 stacks of conditions nothing survies from the damage out put and condition damage.
but if you want a super buff from 25 stacks of a condition then what about the dragons. players can easly get 25 stacks of a conditions and the dragons thanks to the update and guesting abuse would be just way to over powerd in my opinnion.
just my 2 cents

10 stack only? im runing a condition build focused mostly on bleeding, but if i want to do a confusion spike i can usually get at least 12 maybe 15 stacks, and i know there be ways i could get more if i alter my build, but it would suck for pve most likely

From a min max perspective personal stacks would be the way to go but I think that Anet has the right idea about promoting teamwork. In general I think if you have enough people to max out and maintain a condition on a single target that should be a bonus not a waste of a slot/trait. The debuff should be big enough that people care about keeping it up.

GummiBear.2756: 10 stack only? im runing a condition build focused mostly on bleeding, but if i want to do a confusion spike i can usually get at least 12 maybe 15 stacks, and i know there be ways i could get more if i alter my build, but it would suck for pve most likely
i dont run a confusion spike because i dont like the idea of having to hope that the enimie uses a skill especally in PvE cause AI dont spam attack skills like players do.

Im pretty sure dragons and many world bosses dont actually take condition damage (I’ve never seen any tick damage at least from my condition build characters).

The only places personal stacks would really make a big difference is in dungeons, currently if a team has 2 or more people running a condition build theres a big chance one of them is loosing a large amount of dps, and with no multi-build systems thats a big penalty for anyone who doesn’t go for a bezerker or such build. Split em so that each person can have 25 stacks and you mean all builds can be fully used in those situations, and its unlikely to become overpowered as they’d still be doing damage comparable to other DPS builds just in their chosen way (probably a little less tbh but with the flexibilty of mobility)

Kenage Achalarus.4276:

GummiBear.2756: 10 stack only? im runing a condition build focused mostly on bleeding, but if i want to do a confusion spike i can usually get at least 12 maybe 15 stacks, and i know there be ways i could get more if i alter my build, but it would suck for pve most likely
i dont run a confusion spike because i dont like the idea of having to hope that the enimie uses a skill especally in PvE cause AI dont spam attack skills like players do.

that the thing a spike is a burst of damage YOU decide when is going to come, so you can time it to hit right as the mob actually does an attack. and also im getting those 12-15 stack with the ONLY major trait that enhances confusion is Master of misdirection, which have nothing better for that slot, i can use, but need to get past it to 10pt for the extra bounce on staff. So yeah im doing 12-15 confusion stack with no sacrifice done for it

Dasorine.1964:

personally I would prefer they split it to personal condition stacks so having more than 1 condition giver in a team isn’t wasted.

interesting thing I bet, each stack of a boon or condition takes bandwidth on the servers (according to the Anet team, which I believe. If you don’t believe they stated that I’ll gladly dig in and find the moderator who said so.) Each individual stack would be a great solution, for us. For them, it would hurt. They gata be creative and efficient with how the cond stack is dealt with. I really wish it was trial and error at this point but I guess they perfer a full on fix as opposed to throwing spaghetti at the wall and seeing what sticks (with us).

I think this cond stacking issue is most noticable in pve but pvp I havn’t seen any issue. there simply arn’t enough people condition or not condition built to be stepping on one anothers’ toes (atleast that I’ve noticed.)

Yeah, having to track multiple condition stacks for each individual player would be a technical nightmare, chewing up crazy amounts of network traffic. For that reason it’s not likely to ever happen.

Not to mention a nightmare Scepeter Necros would demolish almost every player on the board with Consume conditions and with a staff the #4 mark would transfer 15 + conditions to players in pvp. In dungeons you would never need anythign else if they were personal I like the 25 stacks + time makes a beefer condition but maybe only for 5 seconds

eh I don’t think it would be all THAT hard on network and such, otherwise it would struggle when people apply conditions to a bunch of different mobs.

It would need balancing issues and what not but as it stands condition builds are fairly inferior to just basic crit damage builds due to lack of stacking and such, you loose so much if you hit the cap compared to no issues if you work on pure strike damage.

Right now you can either go Condition Damage build, do decent DPS over a period of time which gets reduced for every condition put on by anyone else (including those with no condition damage stat which replaced your strong bleeds/poisons/burns etc with ones that do only a fraction of the damage) or you can go crit/power build and do potentially more damage consistently to everything (so many things where conditions don’t hurt, dragons, items etc etc that power works on consistently) which no issue if someone else brings the same build.

Right now I really do think they need to do SOMETHING to make it so that one build doesn’t get massively weakened when someone else uses an attack (it doesnt even have to be another condition build character)

Personal stacks would be the ideal solution to having your damage effected by others but im sure if that really would utterly cripple the game somehow then they need to think up other ways.

Right now, conditions are already tracked personally. Your bleed ticks are separate from someone else’s bleed ticks.

The real problem is the 25 stack limit on conditions that stack by intensity. That is where the technical issue arises. On world bosses and the like, if that stack limit is removed there could be thousands of stacks on a single mob, that has to be displayed to every single player, which would use up insane amounts of bandwidth.

I don’t buy the balance arguments because right now there is a clear imbalance toward direct damage builds in PvE precisely because of this limit.