Fixed a bug where Explosions from Armor Explosion could trigger Armor Explosion recursively.

"

Fixed a bug where Explosions from Armor Explosion could trigger Armor Explosion recursively.

What? You kept running and shouting like a mad man with screen clear, but you nerfed actual slam hits. Especially mace hits/slams? I don't get the priorities here.

You killed 1 build that look actually like something you wanted for PoE 2 and kept some PoE 1 BS? What?

Not only that, you killed hitting stuff with mace but buffed running around like a madman with stampede? What? If this a warrior class or rolling and running class?

What?

I'm not convinced that this was a bug.

Having read that patch note, I examined the Armour Explosion (AE) support gem and saw under the "Explosion" tab. "Cannot break armour"

I do not recall having seen that there prior. My guess is that it was an oversight at the time, and not intended. However, I feel that this has crippled the use of AE at any viable level.

My Warrior was capitalizing on that effect of AE to great effect with added "Damage to enemies with fully broken armour" and heaps of armour break. T6 maps were of little consequence, and now I hit a wall between T4 and T5 maps. This atop of the fact that Imploding Impacts still doesn't work correctly. I feel as though the build I put together would be eligible for more if it hadn't been so tactically hamstrung by the latest patch, and if there was a warning on the Warbringer Ascendancy stating "Still under construction"


In my opinion, this change needs to be undone immediately. Absolutely no good has come from their "fix" and a critical support gem has now been made all but useless.

GGG should be targeting every other class for fixes right now. People are blazing through endgame content on every other class. Warriors are underperforming in every metric by comparison, and we're the ones getting screwed over.