Ægon Is Broken - Mystic Dispersion Triggers Off Every Hit (Video)
Qu1ckshoT32_Gaming
Member Posts: 153 ★★
Every single time you hit Ægon with a mystic champion it triggers mystic dispersion. Unless you intended for this to happen, this is one of the most broken interactions with mystic dispersion I've ever seen.
https://youtu.be/rDRvJ3L_jIc
Sincerely Not Yours;
Quickshot Gaming
https://youtu.be/rDRvJ3L_jIcSincerely Not Yours;
Quickshot Gaming
-5
Comments
It shouldn't be that way, the fury should be consumed and reapplied instead of just refreshing infinitely. This is no different then when dexterity rapidly refreshed the precision buff fueling mystic dispersion.
If it's how his design is intended to work, then it's not a bug. He's one Champ. It's possible it's the interaction with the Node in EQ as well. I suppose we need more clarification. I have no issues with pointing out bugs. I'm just not sure if it is or not. It wouldn't be out of the realm of possibility to have one Champ that interacts that way.
It's not the node it's the champ as the interaction occurs in lower difficulties as well. Kabam's new flagship original character is a complete joke to 1/6 of the game who don't even have a class advantage. This champion is broken, whether it's a bug or not we will have to wait for an official reply.
He's broken in the wrong way. Kabam has made it pretty clear that they don't care about how amazing someone is on attack, they'll just release someone even better later on, gotta milk the whales after all. But this is beyond making him useless for defensive use, it also makes him useless for attacking mystics. That one shouldn't really matter, except he isn't a cosmic champion. Make the buff passive.
In this case, Ægon is refreshing his fury buffs every time he gets hit (it's even listed on his abilities).
So I can see this being bug very easily. If it is (most likely it is) it will be fixed, so don't start saying things like he is being nerfed or whatever.
The team has investigated this and have determined that this is indeed a bug. We're working on a fix for this right now, and will likely have one ready for early next week!
Thank you for pointing this out!
In order for the game to progress, both good and bad bugs need to be pointed out.