Spell batching (Devs pls)

Please remove it. We have a weird version of exaggerated spell batching, that “was suppose to simulate the old batching windows + some people’s bad connection to the server” and it makes pvp feel awful, on top of overall mostly lowering skill cap.

People should have never advocated for it, (some streamers, etc.) in the beta for Classic WoW v2 as they have, and I doubt anyone can present tons of evidence that the large batch windows we have is what everyone had in vanilla, and the patches where everyone’s connection was at best, as worse as we see now.

We have some very skillful, interesting things that benefit from smaller batch windows, (as seen on pservers using burning crusade cores, etc. and also retail, BC+wotlk) that were taken out of the game from WoTLK>cataclysm like being able to vanish absorb abilities, or use abilities to knock vanish out, and batching makes that stuff more RNG and luck based than it should be, on top of changing priority, e.g. delaying hammer of justice to hit a rogue out of vanish is a lot more in favor of the rogue than it should be, this is a priority change based on exaggerated spell batching, not something that should functionally be.

To elaborate on changing function and vanish specifically, but batching affects everything- mostly for worse;

Anyone, but certainly older players will be familiar with Neilyo, throughout the BC & WOTLK era it became imminently apparent that there was quite a bit of mind games to PvP for rogue and against rogues. Specifically regarding vanish, this was familiar to all duelist and top rogues worth their salt, with vanish you could deny, or ‘absorb’ anything, including blinds, if you timed it right, predicted it right, and similarly, you could actually delay a blind, (or other abilities, this was more relevant in WOTLK for rogues, with FoK, rocket gloves, etc.) to try to have the damage & CC apply just after the vanish, and knock out the rogue’s vanish. This back and forth for rogue pvp heavily favors the rogue vanishing anything, rather than anyone being able to push & pull and hit out the rogue vanish, unnecessarily. I’m not sure on the exact timing windows, but it’s something like this

Old timers:
Vanish protection: 0.25 sec immunity on vanish
Punish Window (to hit a player out of vanish): 0.25 sec after vanish, (up to 1 sec after vanish max due to lag, let’s say 0.5 at low ms)

New vanish windows:
Vanish protection: 0.7 seconds
Punish window: 0.10 secs

You can look at old BC/wotlk footage, videos, arena, but there was definitely more of a fair fight when it came to combating vanish, and it felt real different. Here’s an old WOTLK video with vanish properties

2 Likes

Didn’t they remove spellbatching mid way through TBC? i’m not sure using examples from TBC and Wotlk is really going to help you in your argument for how it was in vanilla.

Do you mean original TBC? No. If you mean re-vanilla 2.0 (or 2.1+, whatever you want to call the nerfed version of batching after 2019 release) then I think you’re probably right.

The spell batching window on retail only got smaller over time, not increased, using examples of these mechanics and how they interact with each other is very illustrative of the problem of nerfing spell batching.

Batching existed in various forms, I’m not sure exactly when the ‘more new batch window of 0.01s’ took form on retail. WoTLK still had batch window which made something like this more likely. Though, the possibility of them wasn’t made possible with batching (depending on how specific or technical someone wants to get get with a ‘batching technique’) since it’s dependent on properties of the abilities themselves, like vanish, which were later changed in cata+ because blizzard and the playerbase didn’t seem to care about that type of skill, which is a mistake.

Another example related to batching that changes matchup power and strategy, and makes it so difficult and unobtainable for most players, (that’s what batching nerfs do, they don’t remove batching concepts, gameplay and counterplay, they make it so your timing has to be insanely good, like the top 1% of the top 1%) is a ret paladin counter to enhancement shamans/priests dispel spamming paladins.

One of the counters that worked really well and still took timing was timing your attack until the past possible moment, (related to seal twisting, but not the same) and then activating it so you can still get a seal effect or proc chance on your attack like SoC. This was a great counter, and it was more easy to do, required less strict timing with old batching. When they nerfed new batching windows, this strategy is a lot more difficult to time and pull off, so it removed it from the top 70+%, say, of players to top 0.01% whenever they’re fighting a shaman on a good connection, with no lag, or FPS stutters, that, God forbid has a purge dispel on a macro on mouse wheel or something, 99%+ of people simply cannot ever use this technique because it was, by consequence, nerfed by the batching being vastly lowered to 0.01s.

1 Like

edit:

You necromanced this post. He was talking about the 2019 classic WoW where you could hit a tank in combat with Regrowth and Rejuv and Drink before entering combat. It has since been reduced and the big hit from its reduction was that Ele Shaman only get 1 crit with their talent ability instead of both Chain Lightning and Earth Shock.

There were a few other neat things you could do with batching on paladin but ill not spoil that just in case they give us 1.13 back, ill tell you on discord.

1 Like

Why the 6 year necro, Ny?

Fella, they won’t even maintain the version we have. There’s no way they’re ever going to spend enough effort to provide 1.13 as an alternative.

I know you and I don’t see eye to eye on the value of 1.13, but I think your only option is “other”.

1 Like

that wasn’t me necroing brooooooooooooooooo

Colour me confused?

Oh did someone necro this, you replied, then they deleted?

I thought that happened but I think it was some SOD / forum transfer jank happening

I saw this thread and the reply pop up like new in my notifications but I was looking at it and Akumetsu’s reply was 2020 hmmm

'guess it was me, sorry.

1 Like

I forgive you… but only because it was you.

I wouldn’t put it past some troll to find a new way to troll though.

1 Like