Hey, I added classic category. I copied it over from Diablo II: Resurrected. I didn't add P1, PX, P8 sub-categories so it's all PX for now. If someone is interested in running P1, P8 classic then can leave the speedun here and I'll add the categories if needed.

Would like to speedrun this game again. Been looking at ways to get the game running properly. I have bugs running this game on a 4k monitor. There's a new glide available that seems to solve the bugs: https://github.com/bolrog/d2dx

Obviously settings that give an advantage over the base game like wide screen and fps fix should't be allowed. I did a test with these settings:

[window]
scale=2			# range 1-3, an integer scale factor for the window
position=[-1,-1]	# if [-1,-1] the window will be centered, otherwise placed at the explicit position given here
frameless=true         # if true, the window frame (caption bar etc) will be removed

[game]
size=[-1,-1]		# if [-1,-1] d2dx will decide a suitable game size, otherwise will use the size given here
filtering=2             # if 0, will use high quality filtering (sharp, more pixelated)
                        #    1, will use bilinear filtering (blurry)
                        #    2, will use catmull-rom filtering (higher quality than bilinear)

[optouts]
noclipcursor=false	 # if true, will not lock the mouse cursor to the game window
nofpsfix=true		 # if true, will not apply the basic fps fix (precludes high fps support)
noresmod=true		 # if true, will not apply the built-in D2HD resolution mod (precludes widescreen support)
nowide=true		 # if true, will not choose a widescreen resolution (if noresmod is true, this does nothing)
nologo=true		 # if true, will not display the D2DX logo on the title screen
novsync=false		 # if true, will not use vertical sync
noaa=false		 # if true, will not apply anti-aliasing to jagged edges
nocompatmodefix=false	 # if true, will not block the use of "Windows XP compatibility mode"
notitlechange=true	 # if true, will not change the window title text
nomotionprediction=true # if true, will not run the game graphics at high fps

The game ran perfectly on my setup. Would love to run the game again.

Modhub used to embed the videos linked in the description. Used it for co-op run verification. It seems to be broken now, but is much needed.

Currently the profile page lists each run with different team members. It would be much better if the profile page only listed the fastest time for the user.

For example: https://www.speedrun.com/user/Jymnasium

In Jymnasium's profile the category "8 man, Hell" is listed 7 different times, because it was with different team members. It would be much more clear if the profile page only showed the fastest time for that account and obsoleted the others.

I was finding it difficult to get the timing down on left click and enter spam and found this method: hold down numpad enter while spamming enter and left mouse click.

The numpad enter being held down instantly hides the chat if you mess up the timing and the process works a lot smoother.

Latest release: https://github.com/Drelekin/d2r-reset-macro/releases AHK script link: https://raw.githubusercontent.com/Drelekin/d2r-reset-macro/main/d2r-reset-macro.ahk

https://www.autohotkey.com/ required to run the script. Not very user friendly to use currently, but hopefully it's a start to build something more user friendly together. I'll try to work on it more myself over the weekend.

Open source: https://github.com/Drelekin/d2r-reset-macro

I built a script to move the data out of global variables. This was required to make co-op (and other) categories possible.

I followed the D2R category structure. Probably good to have similar category setup for the two games anyway.

With current setup any kind of change is fairly easy and definitely possible. Adding new categories is also not an issue, because there are no global variables that get in the way.

I also already built the co-op leaderboard and would also like to add the Twink category.

Thanks

It has been difficult to admit it, but I don't like this game. Didn't seem fair to maintain a game I'm not interested in. I removed my admin status and added Kano and Mekalb as admins.

IGT tool is open source: https://github.com/DiabloRun/diablorun-igt but I'm probably not going to develop it myself anymore, sorry.

Take care and please don't let the history of runs die.

Runners have mentioned an issue that comes from being able to move during loading screens. It gives an IGT advantage with longer load screens.

For example in act 5 when leveling with Pindleskin it's possible to run all the way to the red Pindleskin portal during the load screen. You can force a longer load screen by using FPS limiter or other methods.

This creates an issue where faster loads are not as good as slow loads for certain save & exit strategies.

Possible solutions:

• Wait and hope Blizzard fixes movement during loading screens
• IGT tool starts the timer if it detects a mouse click during the load screen
• IGT tool always starts the timer after a certain load threshold. For example we could set the max load to be 5 seconds and if it reaches that the timer just starts.

Any other ideas?

D2R has a new -players setting. For example setting -players 8 always starts games with players 8. This should be good for running players 8 runs, don't have to set it every time.

This could also work well for other categories. Having the default be players 8 instead of 1 might make leveling less of a pain in certain parts. Need to remember to set it back to 1 instead of 8 every time.

This does make verifying players 1/8 runs kind of a pain however.

There used to be the building blocks of 8man leaderboard here. What happened to it and are there plans to finish it?

D2R has a new target line command -resetofflinemaps. You have to make a shortcut of "D2R.exe" and add it to the target line the same way it was done in legacy.

Here's an example of how it could be used for sorceress Jail resets:

1. Start client without -resetofflinemaps
2. Get Jail waypoint, close client.
3. Open shortcut with -resetofflinemaps
4. Check Jail maps until you get leveling setup
5. Close client and open the regular client
6. Regular client will maintain the last map you had so you can keep leveling with it

The idea is to have two shortcuts and swap between them when normal map reset is needed:

Are you okay with this? Should -resetofflinemaps and client swapping be allowed in our runs?

Wafu finished the inital load removal script and it was merged into LiveSplit. You can activate it from edit splits menu. Here's a guide: https://www.speedrun.com/d2r/guide/yv0f3

When does the timer pause?

• Every screen that has the "Loading" text.
• During black screen with "Diablo II Resurrected" logo on the bottom right.

Known issues

• Script isn't fully optimized yet and can take LiveSplit 10-20 seconds to load on game launch.
• If the game crashes then so does LiveSplit.
• You can move the character during loading screens which can give an unfair advantage to people with longer loading times.

Give it a try and report bugs here or help fix them: https://github.com/WafuRuns/ASLScripts/blob/master/LiveSplit.Diablo2Resurrected.asl

#Hey I put together the initial leaderboard and theme. Currently all the players settings and cores are mixed together, because the amount of runs is very low. I'll separate them when there are more runs and people want that.

I've added 327 as a verifier, because in the past he has noticed things in runs that others haven't. Contact me if you wish to help with run verification.

#Categories and rules There's a lot to discuss. Post your ideas here and we'll go from there.

#Questions I'm looking answers to How to handle shared stash tabs? Are we going to create separate NG+ categories where using items from stash is allowed? Might be good to call it "Twinked" since that's how it was called when Ryu started it. For example "Twinked Baal" and "Twinked Hell Baal".

How to handle the loads? Time without loads for LiveSplit is being worked on and will be available soon. I think for D2R there is no fair alternative. The load times are long and vary a lot depending on the system.

One thing that complicates time without loads timer is the fact that you can control your character during the loading screen. What would be a fair solution to this problem? We run into an issue where a longer load gives an advantage, because the runner can move further while the timer is paused.

Should the timer be paused during cinematics? Currently the timer pausing script that Wafu built also pauses during cinematics. It would take extra work to fix this. Would you rather have timer be paused during them or not? I would personally be fine with timer being paused during cinematics. It would give a fair resting point for all runners. It's good for our health.

I really like this category, but the leaderboard is a mess and doesn't motivate me to run it at all.

Could we please not separate the players settings and softcore/hardcore in this category? That's how the category initially started anyway (just like pacifist for example).

The category is not ran enough to justify separating it into 100 categories. Let it be just be 14 categories.

Also what's the IGT status in here?

Our WR history through the statistics page is useless so couple months ago I started a project and started writing down the history. Some automatically, a lot manually.

There are categories where data is incorrect from the Teo incident: https://www.speedrun.com/d2lod/thread/mankr I'm not exactly sure which categories are impacted by this.

It would be nice if we could come together as community to fix our history. Let me know if you want to help contribute to the history document. I'll use the data from the document to put together fancier history page on diablo.run as well.

Report any mistakes you see in this thread or message me on Discord.

D2 WR History: https://docs.google.com/document/d/12jo9KozhOo7nURb21DqJsxOyw3a6pg7Huus3qY94uvw/edit?usp=sharing

Every time I run P1 sorc I get reminded of the broken timing method system. Recently I did some runs and that feeling is still there.

IGT favors one particular setup way too much. "The Best" Jail setup gets even better in IGT. Here are two runs:

Both runs get the leveling setup at level 5 (9:30 RTA). • First run gets level 18 at 31:45 (RTA) 27:48 (IGT) • "The Best" setup level 18 at 31:45 (RTA) 26:00 (IGT)

57:33 (IGT) is faster than 56:35 (IGT) run, but the time doesn't reflect it well. I just got an extra 2 minutes of time save in the Jail for doing nothing.

"The Best" setup gets almost a 2 minute head start in IGT and there's nothing other setups can do to compete with that in IGT. RTA ends up much more balanced because the best setup gets longer load times which makes it more fair compared to other setups.

Basically in RTA all 5 setups are competitive, but in IGT only one works.

https://github.com/bolrog/d2dx There's an updated glide wrapper. It has some additional features that I can see are not allowed like the wide screen resolution, but they can be configured easily from the config file.

Anyway my question is if this is allowed for speedrun.com d2 submissions? One of the main reasons I'd like to use it is that they fixed the mouse bug that original wrapper has where it jumps up each time you open a menu with a scaled window.

D2DX allows you to scale the window a little bigger and not get that mouse bug.

Trying to figure out how inconsistent the load times really are between systems. Currently we assume they're inconsistent, but it would be nice to actually test and prove it.

Take part of the experiment:

1. Download the save file. Ask for the save file from my Discord if it's not working. Indrek#9137 https://www.dropbox.com/s/asqjw5mx92c6wfc/Helene.d2s?dl=0
2. Add -seed1400148573 to your target line to keep Jail spawn consistent.

Start the timer. Use Telekinesis on waypoint, walk towards the champions, cast one nova, save & exit. Repeat until level 16 and stop the timer.

My submission: My first slowest attempt was RTA: 5:53 / IGT: 4:20 Time difference: ~93 seconds

After this I did a lot more attempts and time difference was always the same ~93 seconds. Here's my fastest attempt: RTA: 5:42 / IGT: 4:07 Time difference ~93 seconds

Bonus experiment: -ns comparison RTA: 5:13. While IGT saved 90 seconds, then using -ns only saved 30 seconds.

Probably won't be the last experiment. For example should also test shrine checking load time consistency.

Speedrun.com was not built to support (at least not entirely) the hacky timing method solution we have going on here.

First issue is that RTA submissions get denied, but when you make a submission it's set as default. This also causes a problem I've noticed where verifiers don't notice and this happens: https://www.speedrun.com/d2lod/run/zxdr018y IGT run is submitted as RTA even though it's IGT and RTA submissions aren't allowed. Problems like this should be fixed early if we care about the data.

Second issue is that API doesn't list time without loads. If this was resolved we could nicely combine speedrun.com and diablo.run data. Otherwise we can't pull RTA/IGT separately since they're all the same in API.

For example here's my 48 minute sorc run https://www.speedrun.com/api/v1/runs/me683xqz and it has RTA set to 48 mins, but it's actually the IGT. API lists all IGT as "null".

API data should be cleaned up and always considered in future rule changes. We'll never be able to clean up the categories or history page if the data is broken inside.