I think I'd be onboard with allowing this change seeing as we already allow some form of glide usage

Unfortunately all ONLINE runs completed during the 22 Nights of Terror Holiday Event will not be eligible for submission regardless of whether or not it has an impact on the speedruns or not, sorry for the inconvenience.

Thanks for bringing this to our attention, it has been difficult to fully verify every item - especially since some of the tools to create items have some issues with them. I'll be taking this run down for now, if you spot any others feel free to let us know by adding them to this post.

(I'm not the one creating these stashes so it's hard for me to fully verify it myself)

I didn't really test this that extensively, but basically in the new graphics you can't move your cursor even 1 pixel when doing the left click > enter sequence, so people swap to old graphics to avoid this.

I think this buying sequence is only worth it when you don't have the 3-row belt, after you get to act 2 with the 3-row belt I think filling your belt and dropping it will be faster than the other method (unless you have rejuvs on one of the lines as well)

So it would be faster for buying things like stamina, thawing, antidote. But belt drop would be faster in most other circumstances

This man is a legend^

Also after some internal discussion with the mod team we have decided to split PX/P1/P8 for the "Kill Baal" category only. Depending on how Classic and 100% perform, we may consider splitting these up in the future as well. P8 is still up in the air seeing as we only had 1 P8 submission since D2R release.

Patch 2.4 is set to release sometime on April 14th.

This leaderboard is essentially going to become a seasonal thing depending on how much they plan to patch D2R in the future.

Submissions will be allowed as long as there is no game breaking issues with the patch. The 2.4 category itself might not be ready until sometime afterwards, but we will still allow people to submit runs that are on a 2.4 patch when the category shows "2.4" in the "submit run" part.

We will be archiving 2.3 runs for now and for the foreseeable future, it's unlikely that we will be able to run using old patches so it'll be archive unless there is further development there.

What to expect for the leaderboard in 2.4?

• P1/PX/P8 will remain on the same leaderboard, but there is room for future discussion on changing this if enough runs are submit and if enough people want things separated.
• HC/SC will remain on the same leaderboard, however if you submit a SC time that is slower than your HC time the SC time will become obsolete (hidden) and vice versa. This gives people who choose to play only one core the option to compete against the other core.
• 100% category will be added for normal/hell to give people some variety in speedrunning.
• Submission guidelines for runs will be made clearer and to some extent submission rules will become a bit more lenient.
• Patching may require some runs to be removed depending on how significant the change is. But this is most likely only going to be for extreme cases.

I'm going to try and start working on fixing up the guides/resources with some of the advanced strategies that not many people are familiar with when it comes to map/tile reading specifically. As well as /pX guides. I'm hoping to create both a written and video guide that should be complete sometime during May.

(Also thank you to Indrek for helping out with preparing the leaderboards)

Happy Speedrunning!

I'll be making a post about 2.4 and what to expect very soon.

There definitely needs to be more evidence to justify a post like this, a few VODs showing good drops when someone is running for 5-10 hours per day isn't really 'evidence' in this situation. As someone who also grinds 5-10 hours per day, I've also had crazy RNG in drops before, but I've also had long dry streaks.

Also the competition is external from speedrun.com, so some of this is technically off-topic unless these runs are submitted here.

Cheating is always going to be hard to detect in this game, but right now this is pure accusation and I think I'm going to lock the thread for the sake of pointless debate since there's almost no way to prove/disprove this without doing some extensive research into the probability or something along those lines.

After doing some testing it seems like you can press and hold force move one time and continue moving during a long loading screen.

It seems like the only solution to this is to have IGT detect a click during the loading screen and resume the timer if so.

This will be something all runners will have to learn to adapt to and it will also cause some inconsistencies with IGT for people with long loading times and accidental clicks in situations where you can't move.

The other thing is that there will need to be some sort of rule enforcement about using the latest version of IGT or the timer must resume if the player has clicked/moved during a loading screen for verification purposes.

In my tests I can only seem to create distance when creating a character, returning to game from a save & exit and also when going back to town from a waypoint. I can't get movement going outside of town locations, however in some cases it seems like the game queues the movement after a certain duration of loading time?

I guess detecting clicks on the game window would be the only solution, but it would also suck to be penalized for accidental clicks during a loading screen where you can't move (i.e going from act 1 to act 2)

In my testing I noticed this was only really bad when creating a character or pressing play after save & exit. With that said I didn't do too much testing.

Would it be possible to penalize only if the player clicks during the first loading screen after a save & exit loading screen? Since the save and exit loading screen is unique compared to the others, it seems that this might be doable but a bit tricky.

P1/P8 is just PX change my mind.

But nah in all seriousness, I see where you're coming from. But this organization actually gives room for the filters section to be used the way it was intended to be used. The only reason it doesn't seem appealing at the moment is due to the fact that it hasn't been able to be used properly by the original category. I guess the only argument for everything being on the same board would be that individual profiles display incorrect ranking/placement since there is no filter in consideration there. I'm not 100% sure on what the best action is going forward either, but I think a lot of the want/need for separation comes from the whole "that's how it's always been" with the original D2 speedrun category.

I feel like this is an entry point for a lot of things we wouldn't want to see, nothing stops someone from doing this with -seed. As much as not having this feature ruins the Sorceress grind, the fastest times will have a 1-try jail setup and it's not like they don't exist at all. It's just rare.

I'd like to see it be possible, but I think it could be problematic in the future

I don't really think the original leaderboard had a place for this, but I would assume that maybe we could consider this for a category extension thing in the future? Since things are still fresh here and we're figuring things out that could be some weeks/months away though.

Yeah I'd support this, it's really annoying having to change resolutions and refresh rates every time just to speedrun D2. Probably need more input from mods and other runners.

I'd love to know whether or not the 60+ FPS thing affects the gameplay in anyway besides visually.

It looks appealing and the one thing that turns me off about glide in its current state is that mouse bug, so it would be nice to use this for that purpose even if we can rule out whether or not the other features/options are allowed or not.

Might also be worth reaching out to the developer?

Worth mentioning that FRW will probably impact when you should be reentering on your 5th second count. So I would highly suggest practicing with different common FRW values too. Anything from 0% to 65%. More would probably be for very special cases.

Also if anyone wants a nice map with a short Worldstone, the seed is here: 1207532579

There are ways to record both whilst keeping your music audio track separate, it can be a bit of a hassle to setup but honestly it shouldn't be that difficult. If there isn't a solution to the game sound + music in VODs thing soon I'll probably try to put out a setup guide for something like that in the coming weeks

@LaV In regards to the classic ban, I remember that one being relatively close and my stance on it has changed since the vote. Also what Teo mentioned is possible, we had votes but some voices were louder than others when it came to specific issues and definitely could've impacted the results of some votes especially considering this one was so close.

About mod activity: I understand and I'm grateful that you guys have done it for this long. It wouldn't hurt to reach out either directly or through forum post if you want to potentially add some new members to the moderation team though. I'd be willing to assist and I believe there's probably a few others out there who might.

It seems like a mix between Jail + Rule Changes had a negative impact overall.

Personally I'm happy with the addition/switch to IGT, there will be a 'new meta' around reloading for shrines, minor timesaves, etc. but a lot of this was commonplace in older runs too and if they get retimed then there's no issues there.

Banning of -ns is still worth it in my eyes, because most of the people who run stream their runs and for me sound is crucial for enjoyment when playing this game and IGT kind of works as the replacement for -ns anyway.

I would've like to have seen old runs retimed to the best of their ability, even if the retimed IGT result was slightly slower to be 100% safe, but I can see there being problems with that because it technically wouldn't be 100% accurate - I still think it's worth considering for the top 5 runs per class/category but we don't have the tools or very active mods (which is also a problem here)

Back when the vote happened I did vote against classic because I was persuaded by some of the arguments made there, but when I think about classic vs. TCP/IP I wonder to myself why did we ban something that is technically allowed within the singleplayer game, but allow something that is only accessible through mutliplayer? Not only that but speedrunning should be about achieving the fastest times within the limitations of the singleplayer game and classic is within that. I would also consider banning TCP/IP and while I know the Sorceress run would become a lot more grindy, that is the next step for beating the current WR and that's what the game should be about: trying to get the fastest time, not a fast time.

I believe runs with -ns shouldn't have been grandfathered in or they should've been made obsolete if that's an option.

Also I want to make a note that there's been a distinct lack of activity from the mods here, this isn't an attack or anything and I understand that people get busy during points of their life but it's probably worth considering new people to add to the team. It's taking weeks for runs to be verified and there's no motivation around retiming runs or fixing some of the issues that remain on this leaderboard.

Lastly I want to say that the resources for this game definitely need a fresh update and with the help of some others I'm slowly working on getting a guide out there to help new runners and casual runners take the next step into understanding more about Diablo II speedruns