After venting about Diablo II earlier I went right back to it. What, I don't have a problem, I can stop any time I want!
I've been scratching my head with an issue that has plagued me the last 15 years or so; hirelings randomly freeze in place. They stop following and attacking enemies, they just go in full statue mode and the only way to unfreeze them is to use a waypoint/town portal or enter some cave or something. One user here had the same problem some time ago and apparently fixed it by limiting framerate to 25 (IIRC) with RTSS, but this doesn't work for me.
I've tested all the renderers the game supports, DirectDraw, Direct3D and Glide. DirectDraw I've tested with the original renderer and cnc-ddraw, no difference. Glide I've tested with Sven's Glide wrapper and nGlide, same problem. Also nGlide was much heavier to run than Sven's. D3D interestingly is different, hirelings don't freeze in place, instead they disappear completely but it seems to happen much less often than the spontanious statueing. Too bad D3D looks much worse than the other two renderers for some reason.
I've tried to google this problem in the past finding nothing. Except now. Why? Because Diablo II Resurrected got released and apparently it still has the same issue! Which is kinda hilarious. But the good news is someone came up with a fix: Run everywhere.
Yeah, the issue happens when the hireling lags too far behind, which they do constantly if you walk. If you run though, then they keep up just fine and the issue doesn't happen.
No wonder I couldn't find anyone complaining about it online, all the people who were still playing the game after 10+ years were running/teleporting everywhere to fit as many baal runs in an hour as they could, meanwhile the single player ARPG peasant that I am mostly walks unless needed.
So now I need to run all the time or deal with the random hireling statues. I'm not sure will I get used to running, feels a bit too ADHD for my liking. I don't remember having this issue back in the day with my Athlon XP system, but I'm starting to suspect I used the D3D renderer. I wonder would my Pentium III / Voodoo3 system have this issue..
Edit: Still same issue with the Pentium III system. Either it's been around from the start or was introduced by some patch along the way. Also 866MHz pentium 3 isn't apparently enough for stable framerate even with Glide.