Yeah, I remember druids running at travel form speed in bear/cat/caster in Vanilla… Oh wait, no, that never happened. It took Blizzard 3 months to fix it in Classic, even after reported. By your logic, Vanilla=Classic… delusional, to put it mildly. If you can find an explicit record of that specific bug in the archived forum, I’ll post a video of myself eating my shoe.
Just lol at these people…spell batching was begged for by the community for years, now the retail tourists in classic don’t want it. Lol you can never satisfy people these days.
Someone just doesn’t want Ele Sham fixed before they hit level cap on their FoTM reroll, eh?
2 Likes
No changes to spell batching thanks or I quit
The day they lower spell batching is the day I resub.
Maybe the way they implemented it is correct, maybe it isn’t, but it makes the game feel terrible and was a bad idea to bring back. Stopcasting and interrupting spells but still having them go off? Getting hit after a monster is CC’d? Running through traps and aoe effects with nothing happening? Not being able to joust because you run in/out of melee range too fast? Why do you want the game like that?
7 Likes
It’s definitely not correct. Even without the simulated giant batching window, the actual way things are batched is not the same as it was.
1 Like
No changes to batch please. Close this thread.
LOL at threatening to quit over the worst aspect of classic.
2 Likes
Spell batching the the worst QoL change in classic.
4 Likes
And without spell batching you don’t need a mod to do this because the clients behave in a way that’s far more responsive. It’s ignorant comments like this that truely give you perspective. And that perspective is players asking for spell batching don’t know what it actually is, don’t understand what it actually does, and probably will never really experience many of the issues related to it leaving those of us that will holding the bad for this garbage feature.
1 Like
They didn’t feel as clunky and broken because private servers CHANGED a lot of things behind the scenes to make the experience better. Because this is 2020 and not 2004. Because we all have broadband internet and responsive computers now. It’s the day of Windows 10, not Windows XP. This is the problem with every single one of the “authentic” crowd begging for things they don’t understand. You can’t expect the client to be recreated without changes. Blizzard should have just put a bunch of fixes in for the modern era of computers, and left well enough alone past that. They should have never caved and told you whiners anything. Because when you give a load of non-technical people information, they misinterpret it and demand something that’s just ignorant, like current spell batching.
Guess what, there’s no time machine. You can’t go live in 2004 with your crappy PC and your dial up modem. You have to deal with the real world. And for those of us that aren’t absolutely insane all we wanted was the original game’s content and design philosophy back. We didn’t care about the crutches the game was stood up on to make it run on 2004 technology. As long as we got to play with our old classes, talent trees, we got to see the old content, we got to fight for those gear with the old stats. That’s what mattered. And making some concessions on technical aspects, which would have GREATLY improved the experience of playing a game, would have been amazing.
What’s exceptionally disingenuous and ridiculous from the “nochanges” crowd on this issue is that I guarantee that not a single one of you would be looking for this kind of feature and functionality in a SINGLE game outside of Classic. Because you know it’s garbage. You know for a FACT that games need to feel responsive and feel like inputs matter to be good. Early on, the “nochanges” people probably had a good stance on a lot of things. I would have sided with many of them. But this is a new low for them to sink and is beyond absurd.
5 Likes
Actually, that Vanilla mod is no longer necessary in Retail. This is because at least a decade ago, Blizzard added a spell queuing system to the game.
The way this newer system work is like this:
- You can activate a spell or ability while another was already casting.
- If you do so when the previous ability was mostly done (I think about 1 second or less on the cast bar), then the next ability you activate is put in a queue.
- When your first cast finishes, the second automatically starts with no delay. The queue is server-side rather than client-side, so no time is lost due to latency communicating with the server.
- This fixed the problem: Result is a player with 500 ms latency can now do the same dps as one with 20 ms latency. It is no longer necessary to use a mod to try to counter bad latency and improve responsiveness.
I do not know if Classic has this feature though, since the goal of Classic is to simulate Vanilla which did not.
It’s also worth noting that the effect of latency in Vanilla was not quite the same as the spell batching system. Spell batching may have aggravated it due to less frequent communication with the server, but they aren’t quite the same issue.
I don’t really understand how you’re making a counterpoint to my argument. If anything you’re just expanding on what I just said.
Guess what? Nobody likes this ! Lol who would have guessed that the novelty would wear off almost immediately and the majority of feedback about the system is that it is unwanted and negatively affects gameplay
2 Likes
This is so broken, why does anyone want this bad of spell batching? Tighten up the batching window please it is ridiculous when a mob can sprint through the entirety of my blizzard without getting slowed. Or mobs can hit you from 15 yards away.
3 Likes
I had to completely change my muscle-memory when farming those elite demons in winterspring like I used to in vanilla.
Sometimes they resist a fear and I get hit before I cast the second fear. My habit was to cast a bandage immediately once the fear landed but now I must wait because there’s a high chance that the feared mob will still somehow get a melee attack off on it’s way out and interrupt and waste my bandage.
1 Like
Commonly Reported Issues That Are Not QA Bugs
Ujumqin
Quality Assurance
2010/11/02 08:52:00 PM
“Impossible” simultaneous actions.
Examples: Rogue Vanish being broken by attacks, Two mages polymorphing each other, Paladin Divine Shield being dispelled as it is cast.
Because of the Client-Server nature of the game it is possible for two mutually exclusive actions to occur at the same time resulting in some unexpected behavior. Although efforts are made to minimize these situations they will still happen on occasion.
https://blue.mmo-champion.com/topic/4011-class-qa-series-rogue/
That’s just a few examples he gave, this obviously applies to a mob attacking you after it’s been feared as well.
Watching people cheer this before release is pretty comical in hindsight. This is the single worst decision made for wow classic and is the cause of 90% of the bugs in the game.
Sure would be nice to be able to fd/trap in combat every time like I was able to do all throughout vanilla. But no, artificial lag and my class being broken in pvp is apparently fun.
8 Likes
Just viper sting and collect HKs, you don’t have to do anything else in pvp.
Spot on. I argued against this so much on reddit and other places. It is sad seeing hundreds of replies on this praising it as some masterfully amazing move. I wish there was some way to poll all of the people posting a year ago and see what they think about spell batching now. They thought they did, but they didn’t is my guess.
2 Likes