This could be a reason it’s not as easy as trying to match old numbers without accounting for different hardware.
Bumpppping
Exactly and if you just copy / paste and expect it to be ostensibly the same you’re kinda asking for trouble.
That’s a good point and could be part of the issue. We’ll have to wait until we hear a response from the devs I suppose.
This is very frustrating to deal with in a raid environment, especially when you’re full stacked on world buffs with a lot of crit.
You’ll hit execute, get two big auto attack crits (and therefore a whole bunch of rage!) just to see all of it reduced to 0 immediately. You’re then stuck waiting for the next swings before you have a chance at rage again.
You also need to watch out for popping rage potions too quickly after casting an execute, as they’ll be eaten up and completely wasted too.
It makes the whole thing feel like a laggy mess, I can’t believe this is intentional behavior.
As weapon damage continues to scale up I think slam chaining using one of the MANY batching bugs will actually be higher DPS than execute spamming, which is a very sad state of affairs indeed.
1 Like
I think it already might not be worth it for especially horde warriors to execute due to the loss of rage in the batch windows and that including rage gains from WF.
Bump still needs fix
IMO the whole artificial batching system just needs to be deleted… Who cares if 2 mages can sheep eachother if the rest of the game plays like crap.
Leeway is just as bad too, it also needs to die in the fire; Leeway may have been an authentic back end feature for PVP to take place as melee back in 2004, but it was designed to be undetected by the end user hence why we never thought about it.
Now in 2019 the Leeway mechanic is no longer needed and because of that it’s breaking the game every bit as badly as this artificial batching mechanic that’s just not working out at all…
KILL BOTH and the game will be 20X better for it.
1 Like
It’s even more clear to see the pain of trying to execute someone in PvP when you charge to a lower health character and spam execute just for it to never go off and miss the killing blow.
Unpaid work. The type of work Blizzard thrives on
This now appears to be fixed as of the BG patch.
Bit annoying that they don’t list their bug fixes, but execute does now feel MUCH better.
More rage, more executes and BIGGER executes.
Hurrah!
I’ll have to test this tonight.
Seems like the rage dump part is fixed but the delay is still just as large. For example if your execute procs an extra swing that rage is no longer dumped and you can re-execute… However the delay to do the execute is still very long.
Doesn’t look like it’s fixed
Looks like spell batching strikes again.
So many abilities suffering timing like this, gotta love ‘fake lag’.
sadly it makes execute just feel really bad
Yea after raiding with it, it seems to be the same.
Did you end up still feeling like it was fixed?