Spell Batching, why has it not been removed yet?

[Krack-stalagg]

Are you all smoking rocks? This is not something I simply do not like. This is NOT how it was. Spell batching was not even close to as long as it is here. The window is too long (400ms) it needs to 100 or 200 ms.

Do you have proof that it wasn’t like this?

Also, where did you get your 100-200 ms number from? And how do you know that it was 100-200 ms back in 2005?

It seems to me you have little to no evidence to support your claim of

Heals didnt land while tanks died in 2005. My counter spells went off even with .1 sec left on the cast bar of my target back in 2005.

When I 100% remember seeing a heal land on me then I die but I have no ss to prove it. So who is right?

[Gingerdot-fairbanks]

Except that this is exactly how it was back then.

[Tominator-stalagg]

Here’s my favorite moment with spell batching.
I was fighting a mob and near death. So was the mob. I blinded the mob but had no potions or bandages so no way to heal so I used the blind time to regain energy. When I got enough energy I backstab crit the mob for all his health (while he was still blinded). As he is falling over dead he swings hit fist and kills me too. He killed me while he was dead.

[Kramdinh-anathema]

Except that this is exactly how it was back then.

If you really think this is how it worked in vanilla your memory is broken beyond repair.

[Sangwin-atiesh]

Your bits seem frosted.

[Perd-bloodsail-buccaneers]

@Frostedbits-blaumeux

“we feel this is adding the experience of what vanilla was like back in 2005” is not a valid reason.

But that’s the entire reason why spell batching was added to classic.

@Kaivax

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.

[Sangwin-atiesh]

Actually it’s not their memory, it’s yours. Blues have posted on it and discussed it.

[Toebytter-stormreaver (Toebytter)]

Their were odd issues back in vanilla from “spell batching” but that’s just how the game was back then. They do need to fix bugs related to it in Classic though, i do not remember trapped mobs getting a free auto attack off from 30 yards away when the trap broke. Same with stuns, gouges etc. The mobs themselves should be programmed to wipe their attack table when CCd and same with players, there are some bugs from back porting from Legion and that seems to be what the complaints are really about.

[Frostedbits-blaumeux]

The exact example that the blue post states is mages sheeping eachother and warriors charging eachother. I have no problem with that, that is how it should work. Whatever they back coded is NOT working here. Spells are now on “low priority”? That is just applying a 1 or 0 to pre existing retail code and hoping it will all work out when it is not.

If I counter a cast it should be countered, period. Not have the caster get a free .4 sec of his channel that is uninterruptible.

[Kramdinh-anathema]

The mobs themselves should be programmed to wipe their attack table when CCd and same with players, there are some bugs from back porting from Legion and that seems to be what the complaints are really about.

Exactly. Whatever they did to try and simulate how it worked in vanilla didn’t work. There are things being batched that are then executing that should have been discarded.

It’s got to be the cause of so many of the spell and ability related reports in the bug forums.

[Theloras-herod]

If you really think this is how it worked in vanilla your memory is broken beyond repair.

this is Spell Batching + Reckoning from VANILLA in 2006:

this is Spell Batching + Reckoning from CLASSIC in 2019:

TLDR

[Kramdinh-anathema]

Okay, so it works the same for your one spell. We’re discussing the other countless ways the current version of spell-batching DOESN’T work the same.

What in the hell is your comprehension problem?

[Theloras-herod]

because it has the greatest impact on dual wield Fury Warrior tanks (aka both factions Horde and Alliance) and their ability to maintain permanent Enrage/Blood Craze uptime which means +25% dps AND +25% threat and a self-heal

[Kramdinh-anathema]

If they fixed it to work properly, nothing would change, then would it?

We don’t want batching removed entirely, we just want it to work like it did back then.

[Dhalgren-blaumeux]

Time to shut up about all these little things people think should be different. We are all playing the same game. No one suffers more or less than anyone else from the game’s idiosyncrasies. It’s fine. It’s fun. Classic is way better than retail has been for 10 years. Leave it alone. Don’t mess it up.

[Sakurea-azuresong]

To be honest, I hate batching. It makes the game feel sloppy. I don’t like dying despite having activated a spell like ice block, or having melee hits land on me from frost nova’d mobs way out of range of me.

We can replicate the game without trying to replicate the crappy internet of the past.

[Kramdinh-anathema]

Leave it alone. Don’t mess it up.

But it’s already messed-up, lol.

[Chucktaurus-fairbanks]

This was a mistake to begin with.

In fact it was intentional. The idea of Classic is to recreate vanilla WoW as close to what it was as possible, for better or worse as emphasized by Ian Hazzikostas.

From
https://www.pcgamer.com/world-of-warcrafts-game-director-on-why-classic-isnt-just-a-flash-in-the-pan/

Just as importantly, Hazzikostas says, is that Classic “is what it is” and that players have to take “the bad with the good”—even if that means missing a boat because a priest mind controlled you. "There is no lobbying the developer to change that because the game is what it was in 2005," he adds. “It has to be accepted, which then frees everybody to find all the positive aspects, all the upsides of that friction and those inconveniences because there’s a certain acceptance of the downsides.”

Classic is meat to be what it is. It is meant to be vanilla for better or worse. Like it or not that’s how it’ll be.

#nochanges

[Frostedbits-blaumeux]

Unreal. Please read before you reply. We want spell batching to work how it did in 2005. NOT how it is currently behaving.

Get this through your heads. I want the game how it was back then. How spell batching behaves now is WRONG, it is not because I Am not used to or don’t want it. It is flat out not working even close to how it did.

[Chucktaurus-fairbanks]

We want spell batching to work how it did in 2005.

You must be the first person in the history of the planet Earth that remembers perfectly how a game’s netcode worked from ~13 years ago.