Quote (D2JSPUserII @ Nov 14 2018 09:01am)
I also want to know what was wrong with it prior to fix?
There was an attempt to force a poe-style lockstep system on d2 where the game would force synchronization between player and server any time you tried to deal damage
Besides not even working most of the time, this meant that your character could not deal damage unless you were standing in range of the enemy on both client and server.
That meant that, for example, farcast did not work.
It also meant that whirlwind (which causes desync any time you chain multiple whirls together) would miss most of the attacks because the server and client never agree on where the barb is
The reason the barb is so desynced in the first place is because the client thinks there is supposed to be a pause in between actions. The game will allow you to chain whirls together without that lengthy pause, so the server was expecting you to start whirling at a different time than you actually do.
Additionally, if you have str bugged frw items (like up'd gores) or a str bugged enigma (or frw charms) your barb is desynced non-stop which just makes more and more attacks miss. With 400+ frw your barb would miss literally 100% of your hitchecks
This post was edited by SuperButt420 on Nov 15 2018 02:46am