Nobody likes having 400ms of artificial lag.
4 Likes
I didn’t even have this much lag back in vanilla…I dont understand what batching is supposed to be “simulating”
No
End thread.
1 Like
Lag? Lol are you running a comp powered by hamsters. I havent had lag since day 1.
No thank you.
1 Like
I am saying I have never seen things you know like two mages sheeping each other in vanilla. or other such silliness.
The servers back then had a tickrate for spells and abilities of 200ms the modern game is about 20ms meaning damage/effects etc were calculated every 200ms in vanilla. That’s all it’s simulating is the 200ms tickrate vanilla servers had.
It has nothing to do with the computer. Do you understand how batching works? Probably not or you wouldn’t make silly statements.
Batching is a (400ms in Classic) heartbeat on the server in which everything that has occurred must process during. If your abilities are fired before they can take place on the window they are fired during, your totally latency on said abilities actually firing are then network latency + 400ms.
For instance, let’s say that I use rend on a rogue during the end of the current batch. Let’s assume my latency is the measly 12ms it normally is. That means my rend will take roughly 412ms to apply to the rogue.
Now the super fun part about batching. Let’s say the rogue has cast vanish during the first batch window, but our rend still ends up getting applied after they vanished. Even though he got his ability off first, the rend will still be applied and pops him out of stealth. Yay batching!
Let’s say they are at 7% health and you execute. Same scenario with vanish but say you got execute off first. Only it won’t apply this time. Why? Because Blizzard implemented execute poorly in classic and it actually takes two separate batch windows for execute to fire. One to remove your rage and the next to apply damage. Which coincidentally… wasn’t how it worked in vanilla! Yay garbage implementation of batching!
But wait! There’s more! There is some further fudging that happens on the server side to try to better emulate garbage internet speeds of 2004-2006. Oh, and leeway is an entirely different topic that is horribly implemented and not vanilla like at all as well!
In summary, the current implementation of this tech is not vanilla like and causes unintended issues for several classes including rogues, hunters and warriors!
If they aren’t going to get rid of it, then they should fix it.
4 Likes
This should be reposted daily
The locals are into some weird stuff. You’ll get used to it.
This but unironically.
This impacts the gameplay of every class to greater or lesser extents, but it is most visible and obviously silly while playing a rogue in my opinion. Simultaneous double CC, autos or spells going off in between two abilities that should form a seamless CC chain, dots/damage applied post-vanish, it’s actually a joke.
I have also found a 100% reproducible way of showing batching silliness. If you CC a mob not in-combat with you with something like Blind, Polymorph, or Hibernate, and then one-shot it in melee range, it will die as expected. But if you aggro it and enter combat, then attempt the exact same thing, the mob will always get off one melee swing before dying. It SHOULD simply go seamlessly from CCed to dead without the opportunity to hit back at all.
My problem isn’t the lag, it’s the rearranging of the order in which skills “go off”. For example, I constantly switch targets to heal them, only to have my heal go off on the previous target. I have never once had this problem with healing, in the 15 years I have played this game, until Classic. I get dumb crap like, can’t cast divine shield while stunned, can’t cast divine shield: fleeing, and I am assuming that is because of batching.
I remember sheeps going off at the same time, and stuns as well, but it happens WAY more often than it used to, and it feels like the window in which it can happen is much larger because of it. Oh I also get reckoning procs if something crits as I engage the bubble.
Don’t forget ele shamans can braindead mash chain lightning + shock with elemental mastery for double crit, or holy paladin can holy light (or flash) + holy shock with illumination. Stuff like this could happen back in the day, but the window was a lot smaller, and more difficult to land. There are many other things that happen because of batching, and it needs to be fixed. Whomever designed this iteration of it, should be fired.
I played vanilla on dial up, and it was NEVER this bad.
The processing power of your computer generally has nothing to do with lag.
Your internet connection and distance from the server are what determines lag.
…of course, Classic adds artificial lag.
Yup. A lot of things that shouldn’t be part of this “batching” system are effected by it. Targeting is one of those. Even on my lock it sometimes causes problems.