Mace skills changes are troubling
With no jokes or rants, without any toxicity, i genuinely want someone from GGG balance team to come up in that thread and tell the reasoning behind current change for Shield Wall.
Why is Shield Wall nerfed to the ground and Twisters still can shotgun? Was SW some kind of meta that everybody played (like LA, LS, Ice shot) that deserve that nerf nuke? I dont even mind ~15% damage loss on SW tho.
I played mace every league from 0.1.
Non of that was even remotely addressed (to be clear feedback not about "damage bad" its about how clunky mace skills to use).
The only pure buff we have in that balance update is Earthquake with ~13% damage increase. But the problem with Earthquake not the damage. It is 4 second base delay for erruption. You need 2 additional supports and around 30 point investment (where 17-20 points only for travel nodes) to decrease that delay to 0.3 seconds. You cannot balance this skill just with damage twicks.
Supercharged Slam still unusable with 4 seconds "stay still and charge" for moderate damage. Instead of removing fixed attack time and add channel scale we have "description update".
Rolling Slam is good chage but again why not completely remove TAT and apply Sunder treatment here?
I get it that mace fantasy is not about "attacking fast" but TAT is not fun at all. It is some bandaid that solves animation breaking when reaching insane AS. But why that logic do not apply to spears and quaterstaffs then?
Animation canceling still not addressed.
- Leap Slam needs dodge rolling just after landing
- Shield Charge needs dodge rolling
- Boneshatter needs dodge rolling
It is not optional. You NEED to do that otherwise you will stack with animation wind-down for some time. And it is not only critical not to stand still in that game but it just feels weird and unpleasant.
I genuinely want that conversation open because 1.5 year we have that clunkiness with mace skills. And now that state will be frozen until 1.0 (so another 6 month) and at this point i am afraid that those problems won't be addressed in 1.0 either.