After looking around a bit it would seem to me that the way specific categories are being shown whoever setup the leaderboards was not aware of how other games use the site functions to separate categories or how they are defined. Currently the Sort functions are being used as a way to sub categorize certain options (like Softcore/Hardcore, Players 1/8/x, and Class) in an Any% run. Here are a couple of examples for how games with many options available in an Any% run setup their boards on speedrun.com: https://www.speedrun.com/mc https://www.speedrun.com/piggy https://www.speedrun.com/diablo. Even your own Misc categories have the boards setup similarly to the games above https://www.speedrun.com/d2lod#Seeded_Any_Normal https://www.speedrun.com/d2lod#Seeded_Any_Hell https://www.speedrun.com/d2lod#PreLoD. The only difference being the number of submissions to the Misc are far fewer than Any%. The tabs are the category distinction (Any% Normal and Any% Hell in the case of D2LOD) and the buttons under the tabs are used to sort the table based on the columns and the columns are options available to the runner. This way you don't have to click 5 different buttons to find a run. When I hit the Any% tab for D2LOD one would expect the fastest time to complete the game to be shown at the top of the table with what class, player setting, and core were used to achieve said time. I can see not all classes would use the exact same player setting, core or strategy to achieve the fastest result, but the times can still be compared to each other since the goal is the same — killing baal. Choosing a slower strategy for this goal shouldn't mean no comparison can be made between class or core as the times are ultimately the end all be all. As it stands the fastest run does not seem to be the focus....which is odd for a speedrun. It is of my opinion Px should just be Any% as that seems to have the lowest times across any other combinations of options available to a runner. Killing baal would be completed much faster if a sequence skip for the ancients quest were found to bypass the level requirement. Thus making how one manages experience efficiently as they progress through the run a massive factor in how fast baal dies. I'm sure there are those that will say using the player setting command is a cheat code or not intended by game devs but "Are there any single-player cheats in Diablo II? No, Diablo II does not have any cheats. While there are undoubtedly some hacks on the web that allow you to alter your character, these are neither supported nor condoned by Blizzard Entertainment." (http://classic.battle.net/diablo2exp/faq/general.shtml) would prove otherwise. It is feature that the game offers and by strategically using it you can save a lot of time in your run. Here is an old post on speedemos archive (https://forum.speeddemosarchive.com/post/questions_about_diablo_2_any__rta.html last reply by moooh) with a possible counter argument to disallowing Px based on it being a way to change difficulty in the middle of the run essentially, but if the option is available to the runner as the game devs intended it should fit under the Any % distinction. This still ignores the fact that setting the player count scales experience/loot/hp linearly so there are strategic trade offs when altering the player count. I failed to find a compelling reason to forbid the runner from strategically choosing when to raise/lower the player setting if their goal was to kill baal the fastest. Furthermore it reduces the cluttered look the leaderboard currently exists as. With that being said what to do with the P1/P8 only runs? Obviously these are slower but there are many submissions and runners for these "challenge" – for a lack of a better term – runs but you don't throw them away. That would be unfair to those who run these types of runs. Instead they should have their own sort option for the given Any% Normal/Hell category easily facilitated with a column called Player Count. This brings me to an interesting side discussion....Should a P1/8 only run be compared to a Px run on the leader board? My opinion is yes for a few reasons: first because it does seem there are competitive P1 only times to Px when you select certain options like class and core. That alone can show how good a runner is... when they are not getting easier experience gains and still keeping up its impressive regardless of other options chosen. Second the runner would then have the option to stay at p1/8 if they get an amazing start to a run or see something that gives them the opportunity to compete with Px times and change what submission type they want to pursue. Third and probably most relevant to moderators – validation.... How in the world do you verify someone didn't use the player count without going over every second of a 1+ hour long run?? If people want to try to get away with something in a run that would be quite easy to miss. Thus leaving the P1/P8 challenge type run an option left for the runner to decide as they see fit. In the same hand there is the hardcore vs softcore choice and how those options affect the final time. This distinction isn't as consistent from the available runs in determining how fast a run is as setting the player count, but as I see it hardcore should theoretically be slower than softcore because of death warping tactically in combination with portal usage to get quest items or countess loot. Any % should mean using any particular strategy or option to the runner to complete the goal (killing baal in this case) as fast as possible. That last part just doesn't seem to be the main focus and I found that odd was all. D2 is a game of decisions, game knowledge and mechanics giving runners as many chances to be flexible in an attempt to adapt to what the game gives just makes sense to me. I look forward to hearing what the logic was when first setting up the boards because a long time ago people thought Hell barb/necro just were not possible in an RTA style run and well... we know that to be wrong now. Hopefully that all made sense and I apologize for the wall of text.