We Finally Figured Out Why Bosses Stop Moving

A new Diablo II Resurrected exploit has been making the rounds where simply equipping Gimmershred can cause bosses like Diablo, Baal and the Ancients to stop engaging properly. In this video I explain some of this after looking over reverse-engineered Diablo II code understand why it happens. We cover: How boss Target Scores actually work Baal's _GetTargetScore() function Diablo's _GetTargetScore() system Why maximum elemental damage matters so much Every scoring category explained Why proximity isn't enough to beat Gimmershred The AI fallback/pathing logic Why the boss never seems to recover My theory on the engagement deadlock responsible for the exploit While D2R itself is closed source, the reverse-engineered legacy Diablo II code gives us an excellent look into Blizzard North's original AI architecture and helps explain almost every part of this behaviour. If you've been wondering why this exploit actually works under the hood, hopefully this gives some insight. Sources: https://www.reddit.com/r/diablo2/comments/1u6lot3/uber_ancients_bug_reports D2MOO (Reverse Engineered Diablo II Source) https://github.com/ThePhrozenKeep/D2MOO The Phrozen Keep (Diablo II Modding Community) https://www.thephrozenkeep.com/ The Phrozen Keep GitHub https://github.com/ThePhrozenKeep PlanetDiablo AI Reverse Engineering Discussion https://www.planetdiablo.eu/forum/threads/targeting-verhalten-von-diablo.1391558/ D2Mods Knowledge Base https://d2mods.info/