Spell Batching Implemented Incorrectly

Mendedsoul-magtheridon · May 28, 2019, 1:05am

It’s supposed to be based off the spell, not the server ticks.

Ex, mage uses blink > Rogue gouges in X amount of time after mage pressed blink > mage instantly blinks and is also gouged.

There is a small amount of time… maybe like 4 out of 60 fps worth of time to counter such moves… it is def not server tik based or else it would be inconsistent.

Vanishing blinds is another example.

Freeish-proudmoore · May 28, 2019, 1:07am

No… thats how spellbatching works.
It still works that way in live. It was alway bassed on server ticks.
They are emulating the old crappy servers by giving spells lower priority.

Mendedsoul-magtheridon · May 28, 2019, 1:17am

Proof?

I remember the game being reactive with a 100% success to counter moves every single time… not tik based.

Even vanilla wow streamers know the spell batching is wrong on beta atm.

Freeish-proudmoore · May 28, 2019, 1:20am

Spell Batching in Classic

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.

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.

For WoW Classic, we’re moving spell casts to a low-priority loop that will cause them to be processed at the frequency that best fits how the game actually played in version 1.12. Two mages will be able to Polymorph each other somewhat reliably, resulting in two sheep nervously pacing around at range. Two warriors will be able to Charge one another, and the end result will be both warriors standing stunned in each other’s original location.

We think it’ll be fun to see those sorts of things happening again.

For a start read the post they anounced spell batching in.
Most of what streamers claim was due to spell batching actualy didn’t work because of spell batching.

Mendedsoul-magtheridon · May 28, 2019, 1:49am

I read that… they still implemented it wrong. Needs some tweaking.

Freeish-proudmoore · May 28, 2019, 1:55am

Proof?
I have been complaining about spell batching since it was called server lag. Thats how it always worked. It could get even worse when the servers were overloaded.

Eaglesgift-ravenholdt · May 28, 2019, 2:16am

It adds flavor and by knowing something about how it works, occasionally you can turn it to your advantage. Like the glitched Mage blink - it always seemed to happen at the most inopportune moments; but that was part of its charm. It shouldn’t be fixed either.

Dokta-gurubashi · May 28, 2019, 2:20am

Everything I have heard from those ‘in the know’ is that the batching is just a little loose now. I am HOPING its something that the beta players have reported a few times and that Blizzard will look into.

The issue I can imagine though is network latency. The networks of today are not the networks of 2004.