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.
5 Likes
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.
4 Likes
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.
4 Likes
this is Spell Batching + Reckoning from VANILLA in 2006:
this is Spell Batching + Reckoning from CLASSIC in 2019:
TLDR
3 Likes
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?
2 Likes
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
1 Like
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.
2 Likes
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.
2 Likes
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.
8 Likes
But it’s already messed-up, lol.
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
3 Likes
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.
2 Likes
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.
1 Like
When you put in hundreds of days on a character, you tend to remember how things worked.
For instance my muscle-memory tells me it’s safe to bandage because my fear just landed on the mob and it’s now CC’d.
Only in current classic wow this isn’t the case and I get hit by the feared mob breaking my bandage. Classic is full of these issues.
4 Likes
And it fails in classic because it doesn’t feel like vanilla. In addition to introducing a number of bugs.
1 Like
Man you got me! You’re 100% right. Since no one can ever remember anything properly we should just make up everything as we go… oh wait lol blizzard did that already.
3 Likes
I really have to sympathize with Frostedbits here. I feel like I’m going nuts just reading these comments. It can all be simplified very easily.
Spell batching would be fine if it worked the same as it did in vanilla, but it does not and is causing bugs. That’s where the problem is.
Idk what kind of smoothbrain response “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.” is. 13 years ago wasn’t the stone age. There are plenty of resources documenting how things worked back then.
2 Likes
I DEFINITELY remember interrupting casts in vanilla at like .2s remaining, which is now literally impossible. I’ve seen my kicks fail at .4s and it’s atrocious.
It was consistent and reliable back in the day, and batch conflicts were hilarious but not terribly common except in edge cases. Now I’m seeing them everywhere.
1 Like
Careful. I made a post similar to this that started to gain a lot of traction and the forum mods deleted it and gave me a 24hr ban. These forums are run like north korea.
I wouldn’t doubt that for a second.