Wasn’t leeway already confirmed in their not a bug bug list that it was just as inconsistent as it was in vanilla?
Oh, it’s not a bug. But any smart Melee can exploit the heck out of it, even by mistake, so ranged can never get ranged again.
Lemme put it this way. I can hamstring hunters outside their melee range, but not in range to shoot at me either.
I think why hunters are annoyed about it.
I’m well aware of what it is. It was present in vanilla and it sucks, but that’s the way it is.
Good. Payback for all the times hunters jumped my charge back in vanilla.
It wasn’t always tuned as high as it is in Classic. In Classic, it’s virtually maxed at all times.
I mean… I guess if you want to debate with the devs…
There’s been a number of inaccuracies their reference client had, actually.
Yea. To my understanding its just more noticable today. I also think it wouldnt be a hot topic if a video hadnt been made about it. It wouldve flown under the radar for the majority of players.
Overall, most people dont actually understand much of anything about the actual workings of the game and are just crying cause people gotta cry if they cant win all the time.
“I’m not a bad player so it must be someone else’s fault!”
With that said, I’m not Blizzard and I didn’t make the game and I dont have the reference client to test with so there isnt much else to say here.
Blizz says this is how it was and people need to learn to deal with it.
Tauren Warriors shouldn’t be able to charge at 40 yards. But they have with leeway.
Do you have evidence to back up your claim?
I’ve seen it happen multiple times in game, and I’ve seen videos showcasing the range extender. I’ve never bothered recording because I don’t know anyone I can test it with nor how it even happens. Just that after my trap fades and I’m at max range (41 yards) the Tauren can get a charge off without getting less than 40 yards from me.
No I mean “Do you have evidence they shouldnt be able to charge that range?”.
Charge is 8-25 yard range.
Yes? And? Were Tauren able to charge that far in Vanilla?
No? Not unless there was a massive latency discrepancy. Why are you defending what is absolutely a broken mechanic by, “do you have proof this broken mechanic ISN’T accurate to vanilla”?
As I said, leeway and batching didn’t work like this at all times. Only in some cases - and certainly not to such a degree a Tauren can increase the range on Charge by over 50%.
Because thats how it was?
Look, if you want balance, wait for BC, Wrath or Classic+. Leave the game how it is. Seriously.
Hunters really get screwed it seems. Because the game will let people melee you from that range but you still can’t shoot them either. Seems a little lose/lose - ish.
It wasn’t how it was now. It was only like this in rare circumstances. It wasn’t reliable nor common like it is in Classic. Because we have better net and machines, we’d almost never see the leeway like it is - but Blizzard artificially tuned it so it is always on.
This isn’t leaving the game like how it is, it’s wanting to fix what is broken. That includes batching affecting things it never did. You clearly don’t understand this isn’t accurate.
You have evidence of this then? Or I should say, evidence it wasnt always turned on.
…Blizzard themselves said they artificially created a leeway/batching system for Classic to try and emulate what was in vanilla. Batching was based off of server ticks (which weren’t always set in stone at like 400~500ms or whatever Classic is atm), and leeway was based on the connection of the players and not a set amount.
You really don’t know how the systems worked, do you?