So much THIS. This set is bugged to Oblivion and should be taken off of the Live servers until it's fixed.

festegios wrote: »

I assume this is a pvp complaint?

No, it's applicable in all content, and it's more likely to be an issue in PvE now that the set's bonus damage doesn't apply to players. A single instance of Blight Seed has been able to explode multiple times simultaneously since Update 41, in contravention of the set's tooltip. (Null Arca suffers from a similar issue, where multiple simultaneous triggers proc multiple Sliver procs in violation of its cooldown.)

the issue is stacks are shared and the CD is not shared so with enough dots between everyone with it on will have it proc every second on cooldown, resulting in procs happening for everyone far faster. it should either be separate cooldowns which it currently works as but only you can contribute to your stacks resulting in a longer time to proc per person, or it should be a shared CD on proc having just 1 proc per enemy where everyone can contribute to the proc which it used to be

CameraBeardThePirate wrote: »

The set has always functioned this way by design. Blight Seed is a target debuff. Anyone can contribute to the stacks of said debuff, but each person can only cause one explosion every second. Targets will sit at 20 stacks until there is an AB user that can proc the explosion.

That doesn't mean multiple explosions can't happen simultaneously if there are multiple targets. Person A causes Target 1 to explode, and Person B causes target 2 to explode at the same time, despite both people contributing to the stacks of both targets. It's how the set has always worked. It's why it's always been extremely efficient to stack the set in your group, whether in PvP or PvE.

The set has most definitely not always functioned as it does now. There used to be quite the discussion in many of my trials about who would get to wear Azure, since more than one player wearing it reduced the efficiency noticeably. Back then, each instance of Blight Seed could only have one player build its stacks, so players effectively competed to see who would get to build stacks on each target. You could see this clearly in the logs. Each Blight Seed exploded only once.

The set underwent a major change, and there was insufficient explanation provided about exactly how it is intended to work. Kevin incidentally confirmed not too long ago that multiple players can wear it effectively now, but that doesn't resolve the contradiction between the tooltip's claim that each target gets only one instance of Blight Seed (as confirmed in the logs) and the fact that a single instance of Blight Seed on one target can explode multiple times simultaneously.

For an example from my own group from U41: we had 4 people in Azure attacking one lone target, no adds around, and the same Blight Seed instance was credited to one person but exploded three times simultaneously (same millisecond), each explosion credited to a different Azure wearer. It was definitely not a case where other targets were exploding to hit each other, as there were no other mobs around. This was reproducible across multiple logs on multiple days and in other groups' logs.

And for clarity, Azure has been *meant* to have multiple players contribute stacks to the same Seed instance since Update 24. It took a while for them to actually make that happen, but they did that before Update 41.

It was only Update 41 that brought this multiple explosion issue, iirc as a result to a Line of Sight fix that then required a cooldown fix.

The patch notes for U41 said nothing about multiple explosions being intended, even though they started to occur then. The patch notes we have from the earlier change confirm the tooltip language that there is only one instance of Blight Seed intended to be built by multiple players, not that the same instance can result in an explosion multiple times.

And since Null Arca displays the exact same behavior with violating its own cooldown due to multiple simultaneous procs, I think it’s the same issue with the coding.