deletepost please dddddddddddddd .
1 Like
You do realise that with the extremely slowed down FPS, those were pretty much within the same moment, right? The spell started casting well within 0.2s (which is the maximum batch window duration in Classic), from when the earth shock landed.
You got very unlucky though. The spell batching windows doesn’t “start” whenever a spell is cast. They run in a continuous loop every 0.2s, and you can cast a spell at any point during the batch windows. Meaning you can even cast a spell that lands at 199 seconds into the batching window on the server side, to then count on the server as an event 0.03s after you cast it if you give some “wiggle room” for the ping to the server.
These spell batching windows are a thing in refail too, they’re just running in different settings for priority loops while very few things are prioritized afaik on the Classic servers to replicate the Vanilla server settings.
So what happens when your spell becomes registered 199ms into the spell batching window? Well, it pretty much means that everything that happened during those 199 milliseconds before the spell is registered, counts as having occurred at the “same time” on the server side.
Your spell can also count as having occurred 0.001s into a new spell batching window, without it counting anything that happened the 200 milliseconds before it. However, it then counts whatever happens 199ms after it as occurring at the “same time”.
Get it yet?
You just need to include a small time frame when you’re hit by an interrupt, before you start casting. 0.2s, which is a 1/200th chance of you casting so it counts on the server at 199ms into a spell batching window, is rare so you can even wait less than that most of the time.
Spellbatching was a mistake, more at 11.
Omg that’s ridiculous! 
delete topic delete topic ddddddddd
They aren’t “delayed”, that’s a misconception in and of itself. It’s just hitting the entire spell batching window. So any spell cast by you in the same window as the interrupt, gets interrupted if it has a hard cast.
I am already adapting my gameplay after spellbatching. Watch the videos, Im waiting like a moron for the opponents to interrupt to accommodate. Are you saying there are windows in the spellbatch that playes have to consider too? I doub it. I think it’s more simple than that. It’s Blizzard after all. Spell hits, then it lands.
No, it’s as explained already. Think of it more like a mine, and it’ll explode if you cast something within up to 0.2s after they’ve used their interrupt, or in other words “planted the mine”. It lasts for the entire duration of the batch window.
Doesn’t mean it’s up to 0.2s every time though, because as mentioned, the batch windows runs in a neverending loop on the server side. It doesn’t “start” just because an ability is used, so it’s random where in the batch window your spell is registered.
This also makes it possible for successful casts to be interrupted, even though they go out. So your polymorph can be interrupted by the target, even though the target gets polymorphed.
The spell batching windows just counts both of them as having happened at the “same time” if they’re cast in the same window.
Which basically makes it a nightmare to try to interrupt at the last moments of casts, because even if you land the interrupt, the cast will still go out.
For the sake of comparison, these batch windows runs 5 times every second in Classic WoW. While in refail, they run 50 times every second, with different kinds of abilities on different priority loops, so some are looped faster than others.
akjudsu ui jik lo lo lk
Yeah it sucks I used to juke players in wow with heals but with classic what’s the point you can successfully juke then get kicked straight after and with the bursty damage in classic you can’t afford to stand about and wait 1 sec before casting. It sucks even more when faced with a bug abusing ele shaman doing 2 100% crits that do 90% of your health and kicks you with the earth shock even when you try to heal after the damage has taken place
That is pretty interesting then. Goes against what wowhead said:
In the past, back when servers had less computing power than phones nowadays have, these windows could be very large, with some games having up to 200ms windows of batching, including WoW. With better technology and servers, this system was improved over the years and, while it still exists, and effects from it can still be seen, the windows are much smaller, being 20ms wide for abilities in retail WoW. This means that abilities cast within 20ms of each other are considered simultaneous in the eyes of the retail WoW servers, while this window was about 200ms during Vanilla.
The blue post itself doesn’t give any specifics, but if it’s set to 400ms, then that’s messed up.
By the way, how do you know it’s set to 400ms? You’re not confusing it with the lag tolerance setting, are you?
delete topic delete topic ddddddddd
Patch 2.3.0 (13-Nov-2007):
Elemental Mastery: It is no longer possible to get two consecutive guaranteed critical strikes from using this ability
Working as intended
Still a bug, the talent is supposed to make your next spell crit, not two - it’s a glitch they are leaving in because in their view it makes the game more authentic.
Like this abomination of spell batching. My bear’s feral charge is entirely unreliable because of it. Bash is glitchy too.
1 Like
That’s not just the batch. It includes your own ping to the server, and time it takes for the server to respond, you know? Spell batching is 100% server side. Meaning it only counts messages as they reach the server.
Also, don’t confuse the in-game ping with your actual message speed to the server. Routers can be configured to prioritize ICMP packets (or to refuse to answer them), and the in-game ping display only shows a very rough median ping anyway.
Sorry but this is plain incorrect, a blue poster even confirmed that retail does not use batching. Events are processed as soon as they arrive, with a latency of 1-10 ms.
You did read the blue post linked to up above, right?
“We no longer batch them up like that. We just do it as fast as we can, which usually amounts to between 1ms and 10ms later. It took a considerable amount of work to get it working that way, but we’re very pleased with the results so far; the game feels noticeably more responsive.”
By Celestalon on 2014/06/18 at 8:30 AM (Patch 5.4.7)
Admittedly an old source, and on Wowhead, but it IS Celestalon who wrote that back when he worked there, and why would they remove batching and then bring it back? So you’ve got two Blue posts that contradict each other, one saying they had obliterated Batching back around WoD for certain in favour of a first-come-first-serve basis, and another saying they still use batching?
It’s not actually contradicting the blue post with that.
Alright, so reading his entire post, you’ve actually pointed out something more of interest. Celestalon confirmed that servers were set to 400ms back then, and thus wowhead was wrong in the text above the blue post in the post linked to earlier.
Alright, so about the way to interpret what was said:
While we never really eliminated spell batching in WoW, we did change how (and how often) we process batches of actions coming from players, so you’re less likely to notice that processing in today’s game.
That’s from the first link up above, from the blue post. It’s basically saying they changed it entirely, which the wowhead text then further clarifies (although wowhead seems to have gotten the durations of the batching windows wrong in their clarifications).
That part doesn’t actually contradict it. It’s the like that part of the text which matters there. It’s also more consistent with wowhead’s clarification about retail’s servers (even though they got the duration wrong a little bit), and the blue post above also fits in with that statement.
It’s that they changed the way it works, with priority loops and a much shorter batching window, but not that the entire function itself was removed. It was just improved over the years.
In other words, it’s not batched like that. Still batched though, in such short batch windows that it’s basically as soon as the actions reaches the server.
Thanks for the link though, I’ll hold on to that.
delete topic delete topic ddddddddd