I had 20-50ms on appropriate servers for almost 25 years simply because cable broadband has been available for that long, it’s nothing new to have less than 100ms. Spell batching was dragging down the whole server for a handful of people and that’s just bad.
Pservers did not have the server-side code that would process batches. They literally have 0% of original Blizzard server-side code. 0%.
1 Like
I am so excited for tbc
1 Like
Lame as ****.
Spell batching is cancer. JS
The bots on pvp servers with high pings are getting farmed lol
I’m not disagreeing that batching is bad and makes for a worse experience but…everything you said about it is incredibly incorrect.
Any hardcore player wants batching REMOVED as it will place more of an impact on player skill and reaction time.
ban the instance botters that have been here since phase 1
1 Like
This strikes me as a tremendous overreaction and mistake which fundamentally changes the game in a way that the people asking for it have never appreciated.
Here are some advanced gameplay tricks I use daily as a Rogue which depend on spell batching:
-
Vanish immuning PvE mechanics such as Nefarian’s fear
-
Batching Blade Flurry backstab procs when a mob is positioned just out of blade flurry range, by strafing into range of the 2nd mob after each Backstab.
-
Gouging Blinks in PvP
-
Vanish-immuning incoming abilities in PvP (blind, deathcoil, etc)
While so far all of this sounds like complaining about nerfs, in fact this change will be a massive PvP buff for Rogues (a class which doesn’t need it) while also significantly lowering the skillcap and eliminating the advanced techniques which keep the class fresh and challenging 16 years later.
In particular, the massive overreaction to the batching window will mean it’s possible to Restealth off of (improved) Gouge and your opponent can’t batch an attack right as they are coming out of Gouge to deny the Restealth. It’s also a large buff to Vanish by making it harder to batch a spell on Vanish and break the Rogue out.
This is a horrible mistake and I’m extremely disappointed to see Blizzard giving into the whiners and crybabies and taking us further away from authentic vanilla WoW gameplay.
There is a fundamental misunderstanding on the part of the players who are asking for this change: they think WoW is about reaction. In fact that is wrong, WoW is about prediction not reaction. WoW has always been a rather slow and not tremendously mechanically responsive game. And I hate to be the bearer of bad news, BUT, if you died because the ability that would have saved you got batched, the error that got you killed is not that you weren’t able to react fast enough, your problem is that you didn’t understand the situation well enough to see it coming and be prepared.
Fundamentally, these players have failed to understand that WoW - a game with a 1.5 second GCD for most classes - is a turn based strategy game, NOT an action game where blazing fast reaction should matter.
Please reconsider.
4 Likes
You’re hilarious, tell us another joke!
You’re complaining that they’re FIXING your abuse of BROKEN mechanics, that you use unintended tricks to abuse a system they implemented to simulate LAG. They aren’t going to undo it, they’re doing PTR to look for BUGS and screwups, not so people who abuse batching to be able to continue to do so lol
2 Likes
-
The mechanics aren’t broken, this is how the game server worked in vanilla, TBC, wrath, etc. Watch any PvP videos from that era and you will see good players taking advantage of batching and intentionally playing around it. It’s a fundamental part of the game. Batching is THE REASON that people still watch Neilyo videos over a decade later… because watching him predict the exact timing of his opponent’s Blind and Vanish-immune it is a godlike display of skill and game knowledge.
-
Batching doesn’t “simulate lag” it has nothing to do with client lag and everything to do with a server that processes events less frequently. Which is how it actually worked in vanilla, TBC, wotlk, etc.
Removing batching from WoW classic is akin to removing wave dashing from SSB, removing skiing from tribes, removing bunnyhopping from counterstrike or quake, etc etc. These mechanics weren’t originally intended but they made those games great and those games wouldn’t/don’t feel great without those mechanics. The long term effects are not going to be the positives that you all think it’s going to be… it will be a net-negative to remove the character and unique feel added by that unique mechanic… all to appease some mediocre/bad players who think they died because the game didn’t let them react fast enough, when in fact the reason they died is actually that their brain was too slow to process and understand the situation, which would have allowed them to avoid needing to react in the first place.
2 Likes
Man, keep going, you have me cracking up.
1 Like
You’re just blatantly trolling at this point, which must be all that you have left after your clueless misinformation like “batching simulates client lag” (LOL) gets exposed…
One of the worst things about the WoW community is the sheer number of people that hold strong opinions on topics that they literally don’t even understand.
2 Likes
Nice bait.
Imagine thinking that an artificial 400ms of lag is the same thing as wavedashing
lol
you are the one who is trolling m8
1 Like
Current spell batching implementation is horrible and not vanilla at all and is probably the cause of all the spell batching exploits people are talking about.
Vanilla didn’t have most the spell batching issues people are encountering in Classic due to bad implementation. Abilities like Hunter Traps, Execute, interrupts and etc were a lot more reliable in Vanilla than it is currently so people DARING to ask to keep spell batching are definitely biased and don’t care for the greater good of the game.
2 Likes
If you think a 10ms batch timer is closer to what vanilla was then you are utterly delusional. 10ms and we are playing an entirely different game on a basic mechanical level.
If batching were a more reasonable 150 or even 200 ms window this entire time I probably could have taken it for what it was. 400 feels awful with modern internet infrastructure, but I think WoD era batching is a step too far.
Still, I prefer too little over too much. Oh well.
It’s only a different game mechanically because you’re used to Classic spell batching exploits. 10ms spell batching is closer to vanilla than current spell batching by a very long shot.
I always had ~30ms even back in 2005 and never encountered any of the spell batching that I and everyone else encountered to the same extend; traps delays? nope. Execute delays? and nope again. Why? my ping has always been good and because it was well implemented.
Current implementation is too bad to have a high MS.
1 Like
You’re completely wrong. Current batching is 400ms, just like it was in Vanilla. You can see this on warcraftlogs.
It functions exactly as it did during Vanilla, and no one has ever been able to give any definitive proof that says otherwise. It’s all anecdotal: “I remember back 15 years ago I didn’t have these issues!”
Even the vendor batching is the same.
https://i.imgur.com/qnV3Ilx.png
It’s time for people to stop pretending that an archaic action processing system from 2006 would have been anything but bad for the game. They improved it for a reason, because it was awful.
I never said spell batching wasn’t there or wasn’t 400ms, it was there but implemented better and differently because it really doesn’t function EXACTLY like it did from Vanilla up to MoP, it even introduced new issues that wasn’t there before like delays on certain abilities. I’m pretty sure there’s a priority system and the problem lies there.
Also it’s not a matter of 15yo, original spell batching was there until MoP and during that time I NEVER EVER encountered any of the issues like delayed interrupts, delayed traps, delayed Execute and many others because my Ping has always been good (less than 50ms).
Do I make myself clear here? Original spell batching was there until 5.xx and never behaved exactly like it does right now in Classic. I mean both are similar but the classic version is simply a lesser implementation, it’s not an exact copy for sure.
Prove it.
Read the post I linked, particularly the last line. “and the whole game will feel more responsive too.”
You can find tons of videos on youtube of Hunter traps and Mage Blizzard spells from 2006 functioning just as poorly as they do now. Look at the delay on the Chill effect of this Blizzard. It’s at 2:36 if the timestamp isn’t working for you:
https://youtu.be/mjgdBx0YCNM?t=154
Spell batching is awful, it was always awful and it’s functioning properly in all it’s awful glory.