My understanding is that whirlwind itself wasn't change, the way diablo 2 is handling animations, movement and syncing itself was changed. I still haven't gotten any detailed analysis on what exactly was altered, but was plainly occurring is that players are very easily getting synced on clientside to perform actions that they aren't doing on serverside, causing all further commands to be garbled until you resync. Presumably, the same issue affects whirlwind, the 'rubber banding' movement, and FHR animations going bananas. Whirlwind for example is bugged in that you can start a whirlwind on clientside that isn't actually performed on serverside, thus the further commands like movement will go through, but the whirlwind didn't, so you just walk to your target.

He probably wasnt tri whirling

lol that's your average day playing on US servers from Australia. WW barb is the only character I couldn't play to a decent level back in the day simply because it was impossible to switch to WW after any spell unless you waited a whole 5 seconds after the animation ended. Probably 1 out of 100 WW's would actually work. I then played D2 on LAN vs some friends and it felt like I was playing the game with my characters using rocket boots on 10x speed and chain locking became a joke.

This post was edited by aussiemalaka on Aug 20 2018 12:07am