Let’s try to stop spreading lies when you’re trying to make a point, it makes your side look just a tad bit better. It’s working as intended. Whether you like it or not I really don’t care, sometimes I hate it sometimes I like it. This is how it is suppose to work.
Since we first announced World of Warcraft Classic, we’ve seen questions about spell batching. 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. We’ve been working to ensure that in WoW Classic, the gameplay of activating spells and effects will not differ from the experience of playing original WoW.
It was relatively common in the original…
They changed how it works and how often. Used the term “best fits” in regards to how batching FEELS.
“we did change how (and how often) we process batches”
How that is processed has changed.
It’s not the same batching system. It’s the modern batching system prioritized and tuned for Vanilla.
Again, nearly everything in this game has bugs. This is no different.
It needs to function like it did in Vanilla - full stop.
It was relatively common in the original game to see a warrior Pummel a mage who simultaneously and successfully Polymorphed the warrior. The mage suffered Pummel damage but no spell-school lock, because the mage didn’t get interrupted. This could seem paradoxical, but it could happen because the Pummel and Polymorph were both in the same batch, and were both valid actions at the start of the batch. For the most part, things like that don’t happen in modern WoW, but they still can. We’ve made improvements to batch frequency, and the game is much more responsive than it used to be. Still, if you manage to get both a Pummel and a Polymorph into a tiny processing window in modern WoW, you’ll experience the same behavior as in original WoW.
Kevin has mentioned that he doesn’t do code. I won’t be surprised if he had gotten that wrong. Your video also doesn’t state when the special interrupt code was added so it’s possible that Kevin is 100% correct but the interrupt code was added in BC or later then removed once they got spell batching more responsive - i.e. responsive enough to match/surpass the special interrupt code.
That’s not what they said at all. You can’t just make up what you THINK it means - what Blizz meant is what they wrote. Which is the antithesis of what you are CLAIMING they said by putting your own failed attempt to ram your own wrong point by twisting words to wiggle your way out of not reading what was linked.