Honestly, the response from you and Aggrend on this was really cool because we actually got a response and it was explained where the issue was, what happened, and why. Then on top of it, we got a solution that actually exists in putting test changes like this on PTR first.
Can maybe someone explain why a buff that ended up being overcooked (in Aggrend’s own words except on the forum nobody but Community Council can post because yknow transparency) is still in the game and not being tuned and worked upon?
The Developer admitted the buff was too large. So why the decision after lots of whining was to keep it in and not remove it and figure out some other solution to the issue it was supposed to fix?
This is an utter clown show and I’m actually amazed these people work at the same company the Retail balance team does.
Because the original tuning was exactly within the scope of what was aimed for and it actually wasn’t a problem. It appears warriors just really really got sore behinds about it.
However, it’s safe to say we definitely underestimated the level of buff this would be for top-end players, and the net effect was that this ended up being a much larger buff across all skill levels than we had intended.
It clearly was not within what they intended. Why is it still live?
Follow the link and read the post. The buff was overdone and resulted in larger increase than intended. They’re leaving it in for no reason now except for major whining.
Clown devs compared to the Retail balance team and that’s a major achievement.
Unfortunately the same post I linked and you still didn’t bother to read explains their process pretty well.
The buff was overdone, they nerfed it in a stupid way, caved in to whining and reverted the nerf and left it in.
All this when semi-competent dev teams (see: Retail balance team) would axe the buff entirely and go back to the drawing board after it turned out to be overperforming.
Or simply never get into this position by first testing the change at least internally.
This is just peak level incompetence from Aggrend and the rest of the team.
As painful as this was, this is a good reminder as to why putting these kinds of changes out for public testing before we commit to them is a good idea.
And this should be a win for mages,
Lastly, and for transparency, we wanted to let you know that we have been experimenting with some foundational adjustments to Deep Wounds and Ignite to fix the very authentic–but very frustrating–“Munching” effect that causes these spells to not stack properly when two attacks that add to their magnitude land at the exact same time. This is a tricky issue to solve as it will require completely rebuilding how these spells work, which is a risky change. Looking to the lessons above, we are going to wait until we have those adjustments fully fleshed out and can get them tested carefully on a PTR before pushing any adjustments to these spells live. Please keep an eye out for those adjustments coming to the Wrath Classic PTR over the coming weeks.
It would be awesome if blizzard would just communicate these things more directly on the forums.
Exactly. Why is the buff still in then?
Why is it not on PTR being tuned to NOT overperform since it’s THEIR team taht clearly stated it’s overperforming?
They’re just clowns. That’s all there is to it.
However, it’s safe to say we definitely underestimated the level of buff this would be for top-end players, and the net effect was that this ended up being a much larger buff across all skill levels than we had intended
By Aggrend. The buff was CLEARLY more than they intended and the nerf was to fix that issue. The nerf was stupidly done and not thought through at all (much like the buff).
So why is the buff still in and not removed and being tuned?
Yes, because it was a terrible and completely moronic way to nerf it. That is not the point.
Are you being obtuse on purpose or are you simply the dumbest druid player in existence? Sorry but I have no patience for this kind of idiocy.
Yes, it should. But then many other people might’ve read it and ask this same questions. Why was it deployed without testing? Why was it not reverted when it was acknowledged it’s over the top (by the DEVS THEMSELVES) and put back into testing?
And so on. They’re just incompetent clowns and that’s all there is to it.
I mean the feral buff you absolute buffoon because it’s now explicitly clear they didn’t test that either.
Any reasonable developer would REVERT IT ALL to the state from 2 weeks ago and work on a solution that’s acceptable for whatever internal criteria they might have, as per Aggrend’s own words the OOC buff was NOT ACCEPTABLE.