I’ve heard reports that there is no spell batching in TBC. Just wondering if there will still be leeway.
I sure hope not
So, probably.
Nothing like a frost nova landing from two screens away
2 Likes
so far leeway seems to be a massive problem in beta. then again everything is broken in beta right now so thats not really an answer on whether they intend to fix it or not.
3 Likes
The youtuber Willie showed a video where a tauren warrior was hitting a tauren druid through a pillar in the Nagrand arena on the TBC classic beta. It’s still there but the beta is still young. I could get removed next week for all we know.
1 Like
Thanks, found the video and the point in time where it is demonstrated:
I honestly don’t remember Taurens being able to hit through pillars in TBC but it’s been such a long time. I assume it’s only possible when the race of the character being hit is Tauren too because of larger hit box?
Would be interesting if Draenei can do this too.
Blizzard is hellbent on making TBC garbage to spite us for making fun of their boss, so leeway is most likely going to stay in all of its garbage glory.
3 Likes
Melee leeway still exists in Retail, it’s just tuned for modern internet speeds. Problem on TBC Beta at the moment is they are still working off dinosaur dial-up values to calculate leeway. So getting clapped from 10 yards away is still a thing 
5 Likes
The melee leeway shown is consistant to how TBC played. It was very common for tauren to be able to hit otheir tauren through pillars.
Still kind of hoping it gets removed.
It’s strange they would consider spell batching worth changing, but not leeway.
2 Likes
They had to change spell batching, remember that Classic and thusly TBC Classic is running on a modified retail client. In retail, spell casts are on a High-priority loop. If they did not change spell batching then melee classes would not get a chance to interrupt Mages or other casters. Polymorphs would get processed before a warrior stun even though they cast them at the same time.
It would be a true mess.
OP, wowhead article on it below
P.S i dunno who this Sonii guy is but he needs a haircut :)))
1 Like
Thanks for attributing the vid, glad the streamers are testing. He uses Taurens for testing, it could be interesting if attacking around pillars is just a Tauren opportunity (or Draenei, haven’t seen a Draenei doing this yet but I would assume). But if it’s general for all warrs it could be a problem.
There’s also the question of how reliable this is now, and how reliable it was in TBC original.
1 Like
seems to be just taurens as in og tbc
1 Like
Leeway has been in the game since early 2005. It still exists to this today completely unaltered. The leeway we have in Classic and will have in BC is the exact same leeway that retail has now and has had ever since it was implemented.
Leeway is not some Classic thing. Unless you played the WoW beta back in the day, or during the first few weeks the game was out, you have never played a version of WoW without leeway in it.
Yeah, it’s been in there for all eternity. If blizz fixes it I’ll be surprised. I guess if you wanted to hump the meta in classic, now you can’t attack through pillars.
Edit:oops, meant to reply to tanglefox.
Remember the beta still in its infancy. There is plenty of time for changes to happen. I hope they take it out and have TBC play more like retail as far as leeway and lag compensation is concerned.
But it sounds like there is some tuning of leeway on classic that is distinct from what is used in retail? Although the implementation exists its parameterization is different?
That is not true. The actual leeway itself is the same. Delimicus posted the formula in the thread I linked and you can go on retail right now and test it.
The leeway feels different in Classic because of how it interacts with
A.) Tauren increased hitbox
B.) Spell batching.
For A.) The tauren hitbox and leeway together cause very large melee attack distances when combined. This is not the same as retail, because hitboxes were normalized.
B.) Imagine you’re at max melee range with the leeway mechanic currently active. You go to activate an ability that you are currently within range of. Depending where you are in the batch cycle, it could be 0-400MS until the ability actually goes off. Let’s say 200 MS for this example. Now in those 200MS additional movement has happened, but the attack has already been queued and sent to the server. In effect, spell batching is adding additional pseudo-leeway
1 Like
I thought Blizzard changed spell batching so it mimics retail’s latency compensation.
Correct, my comments on spell batching there are related to current classic. The beta and PTR are using the same batching retail has, which is approximately a 10MS batch (down from 400).
All these examples people are posting of “leeway is broken in the beta” are tauren though. Taurens had an increased hitbox until Wrath. I’m trying to point that it isn’t actually leeway people are having issues with, because the actual leeway is the same as WoW has now and has always had. They’re having issues with the tauren increased hitbox size. It is the combination of leeway and the increased tauren range that causes these extreme examples.
1 Like