I’m sure someone else has covered this but… Its a visual bug. You can see the damage is only coming up at the rate of the weapon speed, and the meter confirms it.
You’re right, stacking haste is neither an exploit nor a bug. It’s good that we’re not arguing against stacking haste or saying that stacking haste is an exploit or a bug. Not sure if you’re confused, and just trying to be slick with that strawman.
The hunter in the OP’s video was firing much faster than the haste effects he was under could account for. It’s like if a feral druid used manual crowd pummeler while bloodlusted and then could all of a sudden maul you 10 times a second lol. You’d be all “Hey, you shouldn’t be hitting me that quickly. There’s obviously a bug at play here” and the druid would be all “oh no that’s just haste bro don’t even worry about it dont you know that haste is supposed to make me faster bro lol”
2 Likes
This makes sense
https:// classic .warcraftlogs.com/reports/ gqc1GMFxHWPNyLah#fight=9&type=damage-done&source=20
What does this log mean then?
2 Likes
He’s using the 2.0 attack speed bow from Slabs, he gets rapid fire, lust, haste potion and drums.
Add that all up ofc he’s a machine gun, the hits aren’t really strong because he’s using a 2.0 speed base bow, oh also add in his 15% quiver.
No bug or exploit here.
There is also a haste exploit with casting allowing us to drop under the intended and specifically labeled hard cap on GCD of 1 sec.
Blizzard needs to fix this stuff.
GCD is hard coded in the game engine, and could not drop below 1 sec making this crap literally impossible. Base is 1.5 sec modified (for casters) by haste.
The GCD is the issue, it’s broken, and also obviously due to poor quality it’s allowing hunters to over perform like casters too.
There is no gcd hard cap on auto attacks and never has been
I know that, I’m taking about the GCD, the macro is basically allowing them to reset swing timer (not literally). The engine they are using here is not the same and because the values for the database were interpreted by a script there are errors in many spells that need to be hands on corrected. “Spells” in WoW are not specifically magic but all things in WoW that are abilities; it’s everything from auto attack to arcane explosions.
It’s a common tactic in novice debate to divert attention away from the main issue and shift the argument to something irrelevant. It’s often done when one side is losing the debate to delay the inevitable, IE arguing semantics. That’s why you see it so often on these forums.
1 Like
Haste is multiplicative. If you apply all those buffs it brings his speed to 0.5 second. If you watch the video he’s firing much faster than that lol
2 Likes
over 3.8k dps from autoshot only. 88 autoshots over a 20 second fight with an average attack speed of .2 seconds. SEEMS LEGIT lol
1 Like
There’s one floating around out there with 5.5k on HKM apparently?
Look at the logs-its not a visual bug, people are getting 0.2 attack speeds. No matter how much haste you stack it should never be to the point you get 4+ autoshots per second.
3 Likes
Have you read your posts?
1 Like
Too bad bears use rage. I’d love to be able to maul 5 times a second.
I would also like to autoattack 10 times per second in cat form.
Then why are you posting on it?
This is not what is happening in this case-if you were correct then the hunters attack speed/rate of autoshot would be the same whether you spam the /cast !Auto Shot macro or not.
What is happening here is that under a certain haste point, if you spam that macro you trick the game into executing an ability that should not be available at that point.
It’s fixed on next restart. /Thread
Everyone can post YouTube videos.