Because I doubt you’ll read it because you don’t care about facts:
Posted by Celestalon
I don’t want to get too deep into the under-the-hood workings of WoW servers, but here’s a super short version. Any action that one unit takes on another different unit used to be processed in batches every 400ms.
I agree. It doesn’t take a hardcore player to notice the batching and that it makes the game delayed. Heck, it doesn’t take a player of WoW or games at all to notice the game as a whole has an big delay to it.
While one could make the argument that Retail has this, sure i’l believe that, infact, seldom are the moments where i’ve come across batching catching up and that’s because it’s so fast that it’s rarely noticeable. One could make the argument that taking it out would make the game worse, no, it would make the game more responsive and less delayed if it’s taken out or nerfed, which in turn leads to a better game experience in Classic. Because Classic is a good game, but this flaw in particular just makes the more intense situations of the game, which is practically 50% of them, almost unbearable at times. This reminds me not so fondly of BFA’s worst WQ, The Cycle of Life. Not only being a retread of Beachhead at a different perspective, but with an added delay that makes imputing commands which should be instant, instead feel unresponsive to control.
It’s kinda of depressing to see that even the unofficial “eviiiiiiil pirate” servers already figured out way before Blizzard did, who suppose to know their stuff cause, ya know… they made the game.
But i guess just like Bethesda, the player know more the dev’s handiwork then the dev themselves.
Yes there is actually. You would just make the console fanboys mad. /joke
As a healer I feel this is the biggest change that really needs to be made. I take great pride in keeping allies alive in both pve and pvp and it really sucks when I get the heal off in time but because of batching they still die
Yea this version of batching applies to things it really shouldn’t. LOS for example, isn’t supposed to be batched. Neither is targeting. So why can I switch targets and cast a spell, only for that spell to be applied to the previous target?
I have the most “fun” when I try to cast a judgement when the button lights up as in range, get an “out of range error,” and have already swapped to a new seal because batching didn’t notice I was in range yet despite my UI noticing it.
Then I get to burn more mana and globals to go back to the original seal to judge it.
Thank you for posting this response, this clarified what I’ve seen on this subject.
I have been dumbfounded when I use Nature’s Swiftness then emergency Healing Wave with a tank at 20-30% health just to watch him die.
another fun one is that you can’t safely precast unless you know exactly whe nsomeones gonna pull something.
Cant tell you how many times I’ve moved well more than half a second before my shadowbolt was going to go off, only to have it go off…anyway…after I moved.