As a super moderator of the Diablo 2 Speedrun Community I would like to request the addition of Diablo 2: Ressurected to the Diablo 2 Series (which includes the expansion pack "Lord of Destruction"). We as a community are planning to discuss new rulesets for the remastered version. The alpha version of the game was just recently released and preorderable on https://diablo2.blizzard.com/

To do what exactly with livesplit?

The discussion ended up with the following results:

1. Should tcp/ip rolling be prohibited? And if not, should loading times be excluded from tcp/ip rolling? Consensus: No, it should be left as it is without excluding the loading times
2. Should IGT, which also serves as a kind of an anti-cheat measure against splicing, get removed? Consensus: No
3. Should the target line -ns, which serves as an anti-cheat measure as well when not used, remain prohibited? Consensus: Yes
4. Should classic remain allowed? Consensus: Yes
5. What should be the by default displayed category? Consensus: Should stay as is, because it has always been like this
6. Should RTA timed runs be treated as legacy? Consensus: RTA should stay mixed with IGT
7. Should HC runs be submittable to their corresponding SC category? Consensus: No, they shouldn't be mixed together

A reminder to everyone that the discussion will end tomorrow, so make sure to participate before it's too late. I've updated the discord link so that it doesn't expire anymore. Another discussion regarding the setup of the latest category "Any% Season" will follow up after this one.

We can add a category extension if enough people are willing to speedrun the modified version of D2. It would require a bunch of dedicated people who also are willing to verify the submitted runs. For now, you are the only one who has asked for this. Should more people respond to this thread I could give it a go for like a month or 2. And if nothing happens within the given period I will drop the category extension.

Fellow Speedrunners,

I would like to invite you to participate in the current rule discussion taking place in the following discord https://discord.gg/c8Mf7HcctY by answering the 7 questions pinned in the channel "discussion_lists". This discussion will end on December 6th resulting perhaps a rule change. We all would appreciate your individual opinions on the pinned subjects and thank you in advance for taking part.

The blackscreens we refer to are ones that occur after save/quits during fullscreen. Because this happened outside of that realm it is not considered as a reason for rejection. Due to your contribution I will now clarify the rule further more to avoid such misunderstand in the future.

In your case it is a game crash which doesn't count towards the newly added rule. If you would have had a different OBS background the screen would not have turned black. The black screen effects should only occur when playing on fullscreen and not show up if have a background image behind the game on your recording. Because the verifiers are able to see that the game closed and was continued from the point of crash without any changes or at least a slight set back as the game is notoriously known for, it should not be rejected by any means.

Since someone has recently experienced black screen effects taking place during the loading screens a new rule has been added. The game must be run in windowed mode unless the glide wrapper is used as this won't cause any black screen effects to take place during the game recording. Any blackscreens will lead to an immediate rejection. If you want to speedrun on fullscreen, please refer to Blazerflamewing's Guide in the guides' section.

As for the PreLoD category the target line -sndbkg may be skipped since Bucketandamop has discovered that it won't work on the game version 1.00. Moreover, the IGT won't work for this category and may be submitted with RTA only till we can figure out whether the livesplit extension by Wafu is patchable.

So me and sanzeau have discovered a consistent method to know which waves have been skipped so far. It is independent of difficulty, seed and pc.

Basically the waves 1+3+4 always cause a lag while the others won't. So if you wanna find out whether you've skipped the first wave, you need to experience a lag. Similar to wave 3, you have to experience a 2nd lag after the first lag to know that you are at the third wave. Getting 3 lags in total means you are at the 5th wave.

I've just found the solution which consistently made me do 3/5, 4/5 and 5/5 on every single class. Instead of counting to 9 for sorc in particular, I just wait close to the inner line(which is closest to baal) till baal almost finishes his laugh by like half a second. Then I head outside the outer line(which is furthest from baal) and count to 5(I used the 101, 102, 103, 104, 105 counting method just to give you an idea of how fast I've been counting). Right after counting to 5 I barely touch the outer line and turn back immediately. Finally, I count to 2(once again using the same method) and go back inside passing the outer line. Baal should now be laughing and you can repeat this procedure all over again up to 5 times. Sofar, It has worked out for all classes. So it's wrong that different classes have different approaches.

It works like a charm for me as long as I wait 2 ticks outside the line right after touching it before going back in. Just had my 5/5 on sorc. Now testing the other ticks suggested by blazer for the other classes.