400 MS Batching/2.5 Tick Servers

Take my timestamp and slow the video down, notice exactly when the melee swing begins:

Compare it to this timestamp:

The first video is not necessarily even at max leeway range and it’s still very close to the second video. People are really forgetting that that beta video is showing the MAXIMUM leeway range and that’s a lot harder to come across in actual PvP.

I even took a screenshot:

https://i.imgur.com/5s4Vt08.png

and from the Classic video:

https://i.imgur.com/AwTvagl.png

This alongside the confirmation from Blizzard that melee leeway is working as intended should settle this debate. It won’t though, because people can’t accept being wrong about anything.

1 Like

This was consistent with vanilla /facepalm.

Guys.

Stop it.

Seriously do you just see something that annoys you and instantly say “THIS WASNT IN VANILLA”

Seriously just stop

I posted 4 videos above showing abilities working EXACTLY like this in vanilla.

2:36

1 Like

Y’know, that’s fair. Bad memory on my end, I suppose.

1 Like

Another casualty of the intentional delay is pet pulling groups. Here’s what happens:

  1. Pet attacks monster, single monster aggros pet instantly
  2. server tic/delay
  3. rest of the group aggros pet

The problem is, if I enter proximity aggro range before server tic where the group aggros the pet, group aggro is transferred to me instead of the pet. The server prioritizes my proximity aggro over social aggro from the harmful action my pet did, which is probably a separate issue, but the slow server tic means I run into it all the time when pulling

Again, you shame the prayer.

I don’t care one way or the other, personally. It’s not my faith that’s being betrayed. That’s between you and your man and, like the Internet, he never forgets.