Seed of Corruption is incorrectly calculating the AoE cap if the seed target does not die

Seed of Corruption’s explode component has an AoE cap of 13,570. This cap is reached by either increasing spellpower or increasing the number of mobs hit by the AoE. If the damage cap is reached by an explosion that is triggered by death, then it is correctly calculated as 13,570 total damage (before crits). But if the explosion is triggered by damage, then the cap is reduced proportionally to the number of mobs in the pull. If there are X mobs in the pull then the damage cap is lowered by (X-1)/X. It’s as if the trigger target, which correctly takes no explosion damage, is being calculated in the AoE cap as if it did take explosion damage.

I suspect this may be related to a change in beta that removed the ability for seed explosion damage to trigger other seeds. There is also a current bug that prevents other AoE damage, such as Rain of Fire and Hellfire, from triggering seed explosions.

17 Likes

Played SSC on PTR, still has the same issue
a seed of corruption hitting 11 mobs was calculating its damage towards AoE cap like if there was 12 mobs, losing 8.3% of its damage

2 Likes

Huge bug, can result in upwards to 10% loss damage in a AoE capped scenario as these comments reveal. Pls Blizz if you fix eye of kilrogg bug you gotta fix this one too q.q

1 Like

still not fixed, waiting for blizzard to do something about it

2 Likes

Please fix this. As our spellpower increase with phase, we will hit cap with fewer mobs making the bug even more penalizing.

2 Likes

Still an unfixed issue, looks like changing emotes to look less bad after the lawsuit takes priority over gameplay

2 Likes

Still a bug. Please fix

1 Like

About time we fixed this… :unamused:

1 Like

Disappointing bug.

mind boggling this hasn’t been fixed yet.

MQG change is a red herring to distract you from the fact that blizzard hates warlocks. Keep faith bretheren, seed will finally be fixed in phase 5! (and re-broken for wotlk)

so they go through the trouble of adding a male succubus to the game but they ignore an actual gameplay bug?? blizzard really has their priorities messed up nowadays

Any chance you guys correct this bug ? Its been on since release, we have made a lot of post about it.

It has to be fixed eventually…right?

Still bug. Please atleast give us feedback on the matter, been bug for way too long, unacceptable

Any word on this?

Bump for visibility

Jeez, blizz is really ignoring this one, aren’t they?

They will fix this before Sunwell for sure

Alright team it’s Phase 4 ZA release. We got a list of bugs that the patch broke. We can do it lets fix seed now. :smiley: