Would be pretty nice
Thanks ! Fix it before Patch 2.4 goes live !
it has to be done now !
you cant ignore this anylonger
have a productive and successful few days before the patch goes live so it will be fixed ! : )
still not in the patch notes hmm
Clarification on the hit-registry bug:
4th and 8th frame still hit, but Whirlwind has a new minimum distance travel in D2R (maybe increased resolution caused this, or another issue?). Either which way, what happens is in D2R, itâs possible to have a Whirlwind short enough that it ends before the first hit check happens, whereas in LOD, the animation was always at least 4 frames. This is based on Whirlwind state observation (and not so much the animation itself).
everyone try to reach out to streamers etc. who actually care about the game
thanks in advance
mistakes & flaws have to be pointed out
it cant be tolerated to see a deterioration of a skill that could be fixed so easily
have a good week everyone
Thank you blizzard for including bug fixes for whirlwind in the Patch 2.4 notes! Excited to test this once the servers go live tonight
edit: Turns out hit registry is still messed up. The first attack from the sequence does not seem to be registering, so if you target right under your feet then none of the hits will ever connect.
Blizzard fix whirlwind please !!!
i havent played my barb in months thinking they would fix it by now???
INITIAL WHIRLWIND HITS NOT REGISTERING on anything ( enemies dont take DMG )
imunity upon being knocked back by LEAP is nonsense too
and that only happens vs other players
in PvM GOLDFIND BARB vs HIGH COUNCIL LEAP Knocks them back as usual : /
help pls & thanks : )
They didnât manage to fix it entirely. At least they saw somethings had to be done.
We are half way.
please guys, if you want them to fix it, you have to describe the bug. saying the initial hit is not hitting is wrong. the 4th frame still hits. the reason why you guys are experiencing a lack of hit on very small whirls is because ww in d2r can now end before it reaches the fourth frame, when it couldnt in lod. telling the devs âthe 4th frame doesnt hitâ when it does isnt how u get a bug fixed lol
Hereâs a good way to describe the bug:
Whirlwind is bugged in D2R. In LoD, the Whirlwind state always lasted at least 4 frames, ensuring that at least one hit went off. In D2R, this doesnât happen, as the Whirlwind state can be 3 or maybe even 2 frames long, meaning the state ends before the 4th frame hit can execute, causing hit-less Whirlwinds. Please force Whirlwindâs state to last for at least 4 frames.
More testing about it should be done though, itâs hard to figure out the start of Whirlwindâs animation, so I was basing it off of how long I saw the state, and the state can definitely be shorter in D2R than LOD. The action frames likely arenât based on the state but on the animation.
Agreed,.we is broken so bad Iâm waiting to fix it so I can play my only char. My we barbarian!!!
Canât believe this still isnât fixed. I donât see any whirlwind barbâs at all online anymore
Yes I am not giving up hope. All they gotta do now is fix it so the first 4-frame attack properly registers and WW is back on the menu!
Short whirlwind still not fixed, weapons swing but wont register first hits.
Please fix that and then whirlwind is fixed totally.
yes pls, still hoping they will fix the 4 frame attack which does not register
Thanks for the fix blizzard the future is bright, listening to your community feedback is a step foward <3
Thank you for the Whirlwind fix @blizzard. Barb finally feels good⌠except for the FHR change which still is a huge problem for PvP. There are so many interactions in pvp which were essential in legacy for high tier duels, such as warcry opponent with barb for swirls so that your whirlwind can lock them down and kill with a tight tri whirlwind. Now everyone escapes stun pretty much instantly, so there is no reward for this type of gameplay and our tournaments consistently lead to shooting spells blindly and running without a sensible solution for locking down the opponent.
assassin ww is still bugged with the visual desync