|#MakeAkkhanGreatAgain||March-8-2016 3:04 PM PST (4 years ago)|
|Patch 2.4.1 is making a ton of balance changes to sets and legendary items. However, looking at the recent PTR notes one set seems to have been overlooked, Armor of Akkhan. I believe, and most of the Crusader community would also agree, the set needs to be changed/tuned to bring it more in-line with other class sets.|
Armor of Akkhan
(2) Set: Reduce the cost of all abilities by 50% while Akarat's Champion is active.
(4) Set: Reduce the cooldown of Akarat's Champion by 50%.
(6) Set: While Akarat's Champion is active, you deal 450% increased damage.
Let's provide feedback and discuss any suggestions to help improve the set.
|#MakeAkkhanGreatAgain||March-11-2016 9:55 AM PST (4 years ago)|
|There's a lot of fantastic discussion and ideas in here, and I want folks to know that it's being passed on! Aside from being a fan of Akkhan's myself, there's always room for improvement.|
That being said, we may not make changes to Akkhan's in the immediate future. There are a lot of other changes we're focused on making in 2.4.1 (especially to Legendary Gems, Set Dungeons, and Game Performance), and we really want to take a long look at Akkhan's before we make any final decisions. That doesn't mean the discussion should stop, but I do want folks to have some context for expectations with this feedback.
|#MakeAkkhanGreatAgain||March-11-2016 10:31 AM PST (4 years ago)|
Is there any hope for getting other changes added to the PTR patch? Is this the best forum to suggest changes that might appear in the next PTR?
I feel like suggesting changes in the Items or General forum might as well be shouting in the wind. :/
We're always reading the forums (as well as other fan sites, like Reddit or Diablofans, for example) for suggestions and feedback, regardless of where we're at in development. Just bear in mind that during a PTR, we usually have a particular focus!
Many of the changes we have coming in 2.4.1 came from feedback not only from the previous PTR, but that we collected throughout and after the release of patch 2.4.0. While we don't always reply to such feedback, it is being read and passed along on a regular basis.