Hey guys,
just wanted to point out the problem of patches in d2r. 2.3 is a good example that killed a major bug (Mercenary bug) which makes it a lot harder to compete with already existing records.
With randomly patched stuff, there needs to be a protocol / solution for this.
We keep track of the version for each run submission. Some runners have suggested a leaderboard reset if the patch changes are big enough.
Playing older versions doesn't seem so easy for D2R, but probably possible with -direct -txt.
What are your suggestions?
From my PoV I can only see separated leaderboards (basically seasons) for this work.
The problem that I see is that it is not easily visible which patch is used, and the filter system on speedrun.com is still pretty bad:
I think this is not very intuitive, and people might never realize that different patches are on the leaderboard in the first place.
I haven't looked a speedrun.com in a while, so I don't know what is possible after this revamping that apparently happened.
regarding -direct -txt:
After the update to 2.3 my direct-txt shortcut would just not load / crash on startup, so im not sure if theres a way to downgrade trough that. Theres also the "be at least once a month online or we wont let you play SP thing", depending on possible solutions, that might be an issue
regarding patches: yeah mercbug gone and glitchy firewall fixed are pretty big gamechangers. On the other hand, we dont know how much patching will get done and how often they occur. So for now i`d suggest to keep everything on a board and decide if we need a clean up once a stable version is reached.
Tool is used to track Diblo II: Resurrected loading states with LiveSplit and LiveSplit Server Component. It captures D2R client and tracks loading screens.
Diablo.run client also gives the ability to share your character data after setting up the API key. If you have [Diablo.run armory](https://
