Let me try something. You are a warlock.
Fear spam is total crap and needs to go!
How would you feel about that? I am aware that it’s a straw man argument, but my point is, where does it end with custom changes to classic gameplay?
I don’t believe it’s 0,2 sec. It feels even like close to a second in some situations.
In the past, back when servers had less computing power than phones nowadays have, these windows could be very large, with some games having up to 200ms windows of batching, including WoW. With better technology and servers, this system was improved over the years and, while it still exists, and effects from it can still be seen, the windows are much smaller, being 20ms wide for abilities in retail WoW. This means that abilities cast within 20ms of each other are considered simultaneous in the eyes of the retail WoW servers, while this window was about 200ms during Vanilla.
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.
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.
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.
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.
it ends up with removing out of date mechanic, not changing or removing class abilities. I don’t see how this relates and I see you enjoy arguing about it.
1 Like
Read the link above your post.
(Btw the spell batching in retail WoW has been messed up for years, ever since they removed battlegroups in season 14 of MoP.)
Some kind of spell batching is fine, but this is literally LAGbatching, spell batching have to be reduced 50-60%
If you want more instant effects, retail is → that way. Don’t let the door hit you on the way out.
I find amusing that every argument ends with “go to retail”. You guys are not very smart.
Well i feel that you dont make a very strong argument. Blizz have already made changes to improve the game. Adjustments to the games API for example. (Which is a good thing btw.) So it’s not unreasonable for me to ask for removal of something thats pure cancer to the game.
You ask where does it end? Thats for blizzard to decide obviously.
1 Like
If you ever played vanilla wow you should notice that this spell batching have 40-50% more delay than in original one.
When it’s about a fundamental difference between classic and retail, then yes retail is where you’ll enjoy it more if that’s what you want. No point in making classic into retail nonsense.
Cuz your argument is based on much better reasoning, right? You so smart.
I don’t think spell batching should be removed, but I do think it should be toned down a lil bit, this has been my thoughts on the subject since beta.
it just seems a lil bit overtuned is all, if it was more slight I wouldn’t have a problem with it.
1 Like
Remove spell batching or fix FD+trap Delay BUG.
What exactly is the bug then? The delay? The delay was there back then too. So what exactly is this infamous “bug” you keep complaining about?
The combat? Well, it wasn’t omnipotent back then. You could counter it back then too, you just had to be quick at targeting the hunter’s “corpse” when FD was used and get the hunter into combat again.
Not rly, i have my own Vanilla Videos where trap after FD was instant, also it shows that spell batching there wasn’t this high, Spell batching in original Vanilla was around 100ms and Classic is around 200-250. Feign Death do not drop combat in 30-40% cases, that is also bug.
Spellbatching really is not the reason why people are playing Classic, I think. Most wouldnt notice and those who would I think would be happier (except for the ridiculous #nochange cult that obviously is against everything just for the meme). There are changes in this game, it is everywhere and it is obvious. So it’s not really much of a #nochange anyway.
We obviously don’t want to go to retail because retail is not just classic minus spellbatching… So your “advice” is not really helpful. As this “go to retail” never is.
1 Like
Do I really have to do that long post again? Ok, fine. I’ll quote it all. Now learn to read.
Who cares, it do not works as intended.It need to be fixed, spell batching or FD+trap
On my restoration Druid, thanks to spellbatching I can cast a regrowth and then instantly a rejuv on a tank that has pulled and then shadowmeld and eat whilst staying out of combat.
Takes a quick hand but is possible thanks to batching. Doesn’t work if you’re already in combat ofcourse.
So you don’t even have to go to retail to have a Shadowmeld-Vanish!
1 Like