is spell batchin working correctly it feels weird
There is this thing called Punctuation, you could give that a whirl sometimes…
As to your “question” it’s in the game because it was in Vanilla.
2 Likes
Exactly that is why !
#no changes!
You think you do but you dont !
You guys actually wanted it !
I find it funny xD
it allows bullsh*t mechanics like sit forced enrage, reckoning, two people ccing eachother and makes the game feel a lot clunkier. blizzard of course making their games awesome by listening to the loudest people spouting nochanges and writing multi-page reddits about this crap
6 Likes
I love you, every time you repeat that sentence, and it works. It make people mad.
Thank you!
They cheered and asked for said how great vanilla was now they got what they wanted and i just laugh in these forums ^^
1 Like
Some people have a mother tongue other than English. How many languages can you speak, buddy?
Truly annoying are British who don’t know the difference between you’re and your.
the thing is that you play BFA, a complete diffrent game and you do not understand the magnificence of vanilla obviously
1 Like
Clearly it is you who doesn’t understand the magnificence of vanilla, as spell batching was a huge component of PvP balance in vanilla and removing it would be a huge upset to the balance of power…
1 Like
no changes is a good thing i think but there are many bugs it seems that need to be fix once again
Lol and i found 80% his posts are ignored so he repost it few times 
No it doesnt.
I’ve never seen such HEALING delays during real vanilla.
Activision just brainslessly made artificial 400ms delay for any player’s action.
3 Likes
This is so far from what spell batching does.
Spell batching compiles the events sent to the server every 200ms, i.e. every 0.2s.
Which means if you use an ability and it gets sent to the server with 1ms, i.e. 0.001s left 'til the next spell batch, it will register your ability instantly.
If your used ability gets sent to the server with 50ms left, i.e. 0.05s, then it’ll register server-side after 0.05s.
If your ability gets sent juuust after a spell batching event with 199ms left 'til the next spell batch, i.e. 0.199s, then it will register after 0.199s.
(Keep in mind, this is further affected by the time it takes for your traffic to reach the WoW server.)
Never will it take longer server-side. What you seem to be complaining about is further lag on your end. I recommend tuning your router to prioritize WoW more, or to get a new router that lets you do that.
https://www.wowhead.com/news=290910/spell-batching-in-classic-wow
As with many other areas of WoW Classic, authenticity is our primary concern. It used to be the norm that combat flow and PvP balance were defined and tuned in a game where spell messages were resolved less frequently. There was a single game loop that processed all messages sent and received every server tick. Nowadays, the game processes multiple loops for messages of differing priorities. Spell casts are high priority, and have been for a long time.
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 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.
What is Spell Batching?
For those unfamiliar, Spell Batching refers to how the WoW servers process incoming interactions. Instead of processing everything immediately, the server creates batches of actions (attacks, buffs, debuffs, etc) in order to process them all together. This is done to optimize the amount of time the server spends processing those effects. The side effect of this is that actions in the same batch are considered simultaneous and don’t affect one another.
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.
1 Like
I can think of 20 things that were in Vanilla but aren’t in Classic.
This over the top spell batching is here to make the game feel laggy and clunky compared to retail, not for authenticity.
Blizz is desperately trying to get people to play retail again and to buy the next EXP, this is just one of their many cunning strategies…
It’s there for authenticity.
Human:
English, German (my first language), and French.
Other:
C, Python, JS (and dialects), Go, bash, SQL.
And C++ when I’m really drunk.
2 Likes
I wasn’t aware the definition of “cunning” was altered to “unbelievably stupid and ineffective”.
Maybe you should Call Merriam-Webster?
Clearly you did not play back then.
Same problem is happening on melee classes, i had one instance of a mage being able to finish his polymorph while being blinded. This never occurred in vanilla, sure of it since i already played rogue back then.
The batching they implemented with classic really need tweaking, that’s all.
I mean guys they made changes to AV .
FOr me just remove this nonsense at this point.
Go all out with changes then.
1 Like
spell-patching in vanilla never allowed a mob to hit you after you stun it or complete his spell cast after you interrupt it.
spell-patching in vanilla didn’t effect mobs as what this Artificial lag doing in classic.
3 Likes