I think they moved this to general discussion from bug report. So disregard, general discussion is absolutely not a “serious forum”
He was asking for spell batching as it was for PvP, now whether he likes what they have done I’m not sure, guess I would need to dig around and see if he has stated one way or the other since.
He clearly was arguing for spell batching though, It’s the title of the thread and the entire point of his thread. PvP was his major concern, but it also had things that popped up in PvE as well.
Spell batching is what made those things possible, it’s why you almost never see them on live. That is not opinion, that is fact stated by Blizzard themselves.
He gives this example
In vanilla it was what prevented Gouge+restealth from working. With a 5.5 second incapacitate and a 5 second combat timer, in theory it should have been possible to restealth before the target recovered. But in practice someone mashing an instant cast skill could “tag” the Rogue before/while he restealthed.
What? Lmfao. Batching is not what prevents restealthing.
Combat is what that mechanic is called
I don’t think the OP knew what he was talking about at all TBH, just some feeling like combat would somehow be “broken” if batching wasn’t there.
Combat will be just fine without it
Gouging your opponent’s kidney shot
This is a gimmick, not a combat mechanic.
frost nova and jumping your opponent’s stun
Again, what?
vanishing a death coil
This should still be possible, if anything, it should be much easier to accomplish without batching because death coil is a missile.
Seems to me like the OP is actually against spell batching in practice.
If there was an “open dialogue” somewhere about this several months ago, that was long after the current in-game mechanic had been finalized.
What little discussion there has been has mostly involved people trying to understand it at all.
If a handful of players were requesting this, it’s unlikely that would have had any influence on the devs’ decision.
My guess is that the devs decided to design it this way in order to inject a layer of rng that would increase failure and increase playtime. It fits right in there with their time played metric nonsense.
1 Like
Actually he does, there were lots of screwy things that could happen with spell batching, Blizzard has discussed them multiple times over the years.
Things like jumping a warriors charge, double sheeping, double stuns, and various other things were possible because of how the batching was done.
It was the point of the thread to point out that those things are no longer possible to see on live with the new batching that was put on in WoD and would fundamentally change the feel of Vanilla.
His individual points may not be correct, but what he was suggesting actually was, as it’s been covered by Blizzard at least 3 times that I can remember over the years ( once in Vanilla, once in WoD when it changed, and once before Classic came out ).
Actually this topic came up before Blizzard made it’s announcement about it being in. Now whether it would have mattered what players though on the subject is only something Blizzard knows, and being I don’t work for Blizzard, well I wouldn’t know.
The last statement has some serious tin foil hat stuff going on.
I’m going to go out on a limb and say breaking the game because you want to keep gimmicks in like double stuns and sheeps is bad
And turns out, it is bad
Whoever pressed the stun first should get the stun.
Whoever pressed the sheep first should get the sheep
In fact, that’s what happens 9/10 times.
I feel like the people who think it’s fine now probably played in 2005 on a potato CPU and their internet was two tin-cans connected with a long string.
When the sole net result of a feature is that players are forced to play longer to get something done, there isn’t really any difference whether it was implemented intentionally for that reason or it is some sort of happy coincidence for them.
I feel like the people who think it’s fine now are the same ones who support keeping a variety of brand new bugs in the game that never existed in vanilla, because bugs existed in vanilla, so we should keep these new ones.
Oh yeah there are loads of these people.
If I had a nickle I’ve seen someone say “no changes” and then defend something that wasn’t in vanilla I’d be rich
1 Like
I’m not sure I’ve seen too many say it’s fine now, pretty much everyone’s stance I’ve seen is that it needs to be fixed if something is broken, but there are those like me who are also trying to point out that not everything people are complaining about it is " broken ".
Some of the complaints would be seen even if Blizzard nailed it 100% correctly to Vanilla, my example has been the healing animation going off and people still dying. It was a thing and I definitely wasn’t playing on a potato or a bad internet connection ( had both cable broad band and a top notch PC at the time ).
The only other thing I’ve really been on is people that have this belief that spell batching wasn’t a thing or that some people didn’t request it.
Don’t get me wrong, I understand people wanting to point the finger at Blizzard and say they just did something because they wanted to, but believe it or not in some cases things are the way they are specifically because of player feedback. Retail and Classic have been very different in that regard.
If you spend much time in the bugs forum, you will see lots of complaints about newly introduced bugs. And there’s often posters who support leaving them unchanged.
I think most of those people are just trolls knowing that it’s an easy target since people are already annoyed at the bugs and lack of responses in blue-text.
Batching is pretty terrible. I suspect so many things acting broke due to it.
3 Likes
one thing you can count on is that none of them are being addressed
1 Like
Spell batching is getting even more annoying when you add the increasing lag on the servers with it.
2 Likes
Heres the problem.
Alot of people asked for it. These people were in a very niche community (the really serious pvpers) and they were very vocal about needing it. What they didn’t realise is that blizzard couldn’t execute it like it was with their modern tech.
However much I’d love to see it gone I think we’re stuck with it till atleast P3.
It wasn’t even all of the serious pvpers. It was pvpers maining specific classes (rogue, mostly) who wanted to be able to exploit certain situations.
You know what counter argument I always get on this? Crap like “well, I can get an extra crit on my shaman, when I shouldn’t be able to”. Then there is the rogue who thinks running at a mage while spamming gouge and praying he gets the mage during a blink is some 400 iq super pvper.
Spell batching adds nothing good to pvp or pve. Anyone arguing in favor of it is just someone playing a class that will benefit from the lag.
1 Like
It’s always Rogues.
1 Like
Spell batching is going to do more harm to classics sustainability then any other thing ie leeway and bugs.
2 Likes