fix this pos already.
Diablo 2’s garbage netcode is likely to blame, along with some packet loss and/or ping jitter between your computer and Blizzards servers. The original game and Resurrected both use the same garbage netcode, which is horrible at handling high ping jitter and ANY AMOUNT of packet loss. Symptoms include laggy movement/teleports, both your character and monsters “warping” and the familiar “Your connection has been interrupted.” screen upon random disconnection.
If you want to investigate:
Plug your regions IP into WinMTR and click Start. Let it run for a good 20 minutes, then check what IP starts lagging, and if there is any loss.
Diablo II: Resurrected server IPs:
| Region | IP Address | 2nd IP Address |
|---|---|---|
| North America | 137.221.106.88 | 137.221.106.188 |
| Europe | 37.244.28.80 | 37.244.28.180 |
| Asia | 117.52.35.79 | 117.52.35.179 |
WinMTR does have a log export option. If there is a significant amount of ping jitter and/or any packet loss on any of the connection hops, you can try forwarding the information to your ISP, they may then forward the information to whoever is responsible for the faulty hop that way the problem can be looked into.