This marks the first “changes” thread that I’ve ever agreed with. That would be because these “changes” are actually reverse changes that shouldn’t have been here in the first place. Who’d have thought?
Batching and leeway were in vanilla, actually.
This is true. Batching was in Vanilla, however it wasn’t the batching we have today. Today’s batching is equivalent to 400ms, which is a much longer window than it was in Vanilla. Leeway seems more extreme as well.
edit: One thing to add as well - batching in vanilla was a natural byproduct of the servers capabilities being used at the time. The batching we have now has been artificially implemented to attempt to recapture said mechanic. However, it was overshot by quite a bit.
Well, if you have evidence of that, I’m sure everyone would love to see it. I want things as accurate to vanilla as possible, but “no batching” is not correct.
Personally, I think folks are experienced what those of us with decent internet always experienced.
Close enough.
The phrasing is difficult for me to ignore, but I’ll try to address the point you’re making.
Yes, Classic recreated the vanilla batching. That’s the point of Classic: to recreate vanilla. Batching is just as much “artificially implemented” as every other mechanic or feature of the game, such as energy and mana regeneration, even down to graphics.
“Graphics were the way they were in vanilla because PCs were bad and couldn’t handle it, but now we have better. We should get updated graphics!” Exact same argument and logic as “Batching was for people with bad internet back in vanilla. We don’t need it now, so it should be removed.”
If it’s inaccurate to vanilla, fine. Fix it. But to suggest Blizzard remove it completely demonstrates that those people do not actually want vanilla.
Artificial batching @~400 ms is “incorrect”, as it is a much longer window than we used to have. Retail still has batching, but it’s not 400ms, and it’d be closer to what Vanilla was than we have now. Want a source? Google it.
Once again, you are correct, however this specific mechanic is tuned improperly. It’s pretty common knowledge. As I said, retail still has batching. I can still get polymorphed with my grounding totem down in retail. It just isn’t as heavy as it is in Classic (which is too much, even for Vanilla recreation standards)
I’m not looking for Blizzard to remove batching. Blizzard has, to this day, never “removed” batcing. It still exists. I’m hoping to have this false recreation withdrawn.
Not a very compelling argument compared to:
Again, if you evidence proving this is inaccurate, please share it. We’d love to see. But I’m not about to roll over for an argument as weak as an assertion followed by “Google it.”
It’s a common belief, sure, but no one has shown any evidence of batching being inaccurate to my knowledge.
Just a bunch of people “not remembering it being this bad.”
The OP is, though:
And you agreed with it:
lol
By Celestalon on 2014/06/18 at midnight (Patch 5.4.7)
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.
Exactly the same, the formula hasn’t changed in 15 years and still exists in Retail.
The artificial batching they implemented seems to cause a ton of problems that just don’t feel good.
I’m good with warriors charging each other, double gouge etc, but it reaches much farther than that.
orly
Give an example.
Still can’t believe this thread of all threads got a blue response lmao. Like bruh, did ya’ll just come back from a 2 month vacation and click on the first thread you saw?
If we could be objective for a moment, two mages sheeping each other is random and stupid. If that is “fun” then we should double spell batching to make the game even more fun.
Spell batching isn’t “fun” it is “funny” because it is stupid.
It doesn’t reward skill, it penalizes it. And it eats 90% of my Nature’s Swiftness heals.
2 Likes
Well, given the fact that batching still exists in retail and to our knowledge cannot be removed even on the most powerful and fluent version of processing that WoW has ever ran on, one can only assume that OP means that he wants it to return to that level, rather than the current batching that is, like I said, created artificially rather than being a byproduct of the server capabilities. Pretty obvious that op is not in the classic forums suggesting that the server capabilities for classic servers should now surpass those of retail regarding batching. If you want to argue semantics why don’t you join a debate team when your high school opens back up.
That’s the thing — how will one ever prove that it’s incorrect? This is a recreation of a certain mechanic that existed in vanilla due to server capability. Any attempt to recreate that is guesswork. If the majority of people say it’s wrong, it’s very likely that it is. This is something that becomes highly noticeable in pvp environments and even extends to batching trade windows with BoP items like we’ve seen with the ZG enchants.
If you truly haven’t noticed the batching window is larger, youre likely ignorant to much more than this. Again — you seem to have a “prove it or gtfo” attitude and It’s not my job to prove it to you. Everyone has noticed that batching is too extreme - remain blissfully ignorant if you so choose
This stuff happens all the time now though, because the window is so big that I can be poly’d halfway through my fear and the cast still goes off. A near-dead mage poly’d me today while I was draining his soul and after I turned into a sheep I still got my shard.
You have no leg to stand on because you claimed 400ms batching was not in Vanilla. I then linked a 6 year old Blue post confirming that was the old batch window and you ignored it.
During the Classic Beta, the majority of people were absolutely smashing the forums with QQ threads about the damage of Elites in dungeons. I provided irrefutable evidence that the damage was correct; Blizzard also did so and then there was silence.
There’s a reason that “Not a Bug” Thread exists. People have terrible memories.
1 Like
The intention of the current batching in Classic is to recreate the batching in vanilla. This is effected by server connection as well. Batching may have been 400ms in total in Vanilla, but currently we have the response of the server time PLUS 400 ms. This is where you see the discrepancy. 400 MS artificial batching PLUS server response time.
I don’t even know why I’m arguing the point. Like I said it’s a known thing, most people complain about it. It’s not the way it was. If you haven’t noticed for yourself you probably barely even play the game. Paladins can cast Divine Intervention, die, have it go on cooldown, and watch their target die as well. Same with bubble. Same with Elemental Mastery giving 2 guaranteed crits if you spam Earth Shock. Again, things that didn’t happen in Vanilla. Whip up all the blue posts you want from this ever-so-reputable company. This isn’t how it was. Swallow the pill.
If by “everyone” you mean some people, and if by “too extreme” you mean accurate to vanilla, then sure.
An exploit that was possible back in vanilla. Not a very strong argument for 400ms being inaccurate.
False.
Try swallowing reality, dude.
I’m no fan of Blizzard, especially with all the changes they made to Classic, but, like it or not, batching is accurate to vanilla. But again… feel free to provide any evidence proving otherwise.
No, your terrible memory is not evidence.
All things that happened in Vanilla. They didn’t even attempt an Elemental Mastery fix until TBC:
Patch 2.3.0 (2007-11-13): Elemental Mastery: It is no longer possible to get two consecutive guaranteed critical strikes from using this ability.
Going to keep moving the goalposts and proving yourself wrong?
No it isnt, they literally copied it out of the vanilla code
No it isnt.
Leeway uses the same exact calc it did for the last like 15 years, it has never changed, retail has the same leeway.