Didn't see any topic regarding this issue, so I will post it. In case I'm blind and retard and there's already one about it I haven't seen, just tell me.

https://us.battle.net/forums/en/bnet/topic/20764386292

Not a barb player so I haven't tested it myself, but it seems blizz did it once more. Can anyone confirm?

Well, it doesnt seem to be 100% broken, but after a quick test clearly some chained ww's arent registering server side.

Pretty significant for pvp given if you ever stop wwing the other guy will auto get away or kill you instantly (was wondering wtf was going on last night while wwing a amp'd druid in fpk lol)


https://www.twitch.tv/videos/262379013

Not bug, is feature!
Indirect buff to sorceress

Did you see the fanboy on the blizzard thread? "if whirlwind wasn't supposed to work that way it's actually a fix"

which basically plays into the "original intent" argument for blizzard to do whatever the fuck they want. even tho that intent was never stated and could just be made up by a team of young guys who didnt even design the game.

Well navigating through classic forums is always guarantee of getting severe cancer within 3-4 hours from first post you read, this is known and proven

Good part is I don't think Chandler and the rest pay too much attention to it...

Yep i can confirm WW is broken , together with walking/running desynchron

This post was edited by WhenLadderReset on May 17 2018 11:36am

if they nerf my barba i may give up on battle.net and move to private realm

The "original intent" argument makes about as much sense as arguing whether Alexander Hamilton would have supported the right of citizens to purchase an assault rifle.
None of the people who created the game even work at blizzard anymore. If original intent mattered to anyone then why would they make WW use weapon attack speed to determine hit frequency?

did they made it for ghosts too?

OFC she uses WW too

This post was edited by WhenLadderReset on May 17 2018 02:51pm