People have found many examples of batching not working as it did in vanilla.
And when you look at it it’s pretty obvious why. Batching was added very late in beta, which worked quite well before that, and was not part of the base game engine.
1 Like
So this is a massive conspiracy and not a erronous memory from 15 years ago, further skewed by false pserver mechanics? Gotcha.
It’s more that batching sucks, always did suck, and should have been left by blizzard as one of the benefits of using modern infrastructure is that awful mechanic is gone.
The conspiracy theory is that batching in any way involves skill.
1 Like
I’ve asked you to provide examples before. You’ve provided nothing as you know batching is working correctly.
Except it’s not, and should have never been added in the first place.
Beta was much better before batching was cludged in.
Actually batching can be done differently without having the feel of the delay classic currently has. Every decent Pserver managed to have batching in place while also adjusting to 2020 connections.
No, the batching here is artificially created and not like the original one. Also the timer in vanilla was “about” 200 MS according to Wowhead
Edit: https://www.wowhead.com/news=290910/spell-batching-in-classic-wow
There are a few abilities that used to seem like they went off immediately client side rather than go through batching. Like feign death, for one specific example.
Overall, batching works largely like it should. There are just a few hiccups here and there from using Legion client to simulate classic rather than using classic client.
Not client side issues, these are server side issues.
LOL? Are you serious?
https://www.wowhead.com/bluetracker?topic=13087818929
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. Some very attentive people may have noticed that healing yourself would give you the health instantly (minus client/server latency), whereas healing another unit would incur a delay of between 0ms and 400ms (again, on top of client/server latency). Same with damaging, applying auras, interrupting, knocking back, etc.
https://twitter.com/NanoNost/status/1162121167509118978
The Nost core had melee leeway and 400ms spell batching.
This is a lie. As someone who was here the whole time, we asked for batching and we got it. And we celebrated it when it happened. Ill post videos and proof from YT and Reddit if I have too.
Not sure why you new comers lie like this. The post you quoted was right. We asked for it, and we got it.
Some complained, but overall, it was something the people asked for.
That’s what most people here do, lie. They lie and lie and lie some more.
Still does not change the fact that the current batching is an emulation of the original vanilla one, and still feels different than the game you see in PvP videos made in 2006.
Go and watch pvp movies from nost then (I do not wanna link em, since this might get me banned) but a quick yt. search will suffice. If you believe the responsiveness on Nost and classic are similar I can not help you.
Classic has a sluggishness to it that popular pservers never had and that is working more akin to the 2006 version than pservers version of vanilla. A quick search history in these forums or reddit will also tell you that I am not the only one pointing it out. That said, I merely wanted to counter your argument that batching is to blame. Pserver operated with batching and did it far smoother than classic does, albeit both apparently running a 400 MS window.
It never happens to me. I think It must be your IPC, and not the game.
That’s 0.4 seconds. That is not 2-3 seconds.
Most of the posts in this thread are about combat batching (spells, pets. etc) and have nothing to do with the vendor delay OP is seeing.
It’s a valid conversation. It just doesn’t help OP much. I can’t remember the last time that I aggroed a vendor’s pet while he was casting…
You know you can simply look at logs to confirm that batching is 400ms, right? If what Nano said is true and Nost ran at 400ms batching, then explain how one could be “smoother” than the other. If they’re both 400ms, they’re both 400ms, that’s it.
Joana’s leveling guide from Vanilla.
Batching is any action that one unit takes on another different unit. This includes vendor interactions.
With what?
Whatever. I’m using this character because it has post history going before you could make classic characters. I’ve been here the whole time too.
I could post YT videos and posts of people saying how horrible the batch system was. To what end would that be? What problem do you expect to solve? It does nothing but show it was controversial, not prove anyone is right.
Just because you have a differing opinion doesn’t make what others experience a lie. Get over yourself.
I am fully aware batching never went away. There was no reason to change it. Anyone vaguely familiar with computers knows what happens when you try to fix something that isn’t broken.
Well no, its not really as easy as that. The batching used in classic now, again is forced artificially. The game does not behave like it does in vanilla and pservers. Possibly due to the client each version uses.
It just emulates batching, and operates differently than it did in vanilla and it is noticeable, albeit being a nice approach to the original game.
So its not just done with “well both work with 400ms”. The way it behaves is still different. Id advise you to watch older videos (either original vanilla or Pservers like Nost) and see how they dealt with batching. There is a tangible difference on how batches work.
Some people asked for it.
Most people realized how stupid it was and didn’t ask for it. The people actually playing in beta immediately realized how awful it was.