for all intents and purposes the WR is 1:42 by AC: https://www.speedrun.com/ssol/run/yj69r8gz (it's using the speedrun-mod client -- the physics are the same, time is measured in ms, there's an inbuilt timer with custom splits, and more).

SSOL is a pretty harsh game wrt inefficiencies -- a small error about when to slow down can mean losing a second or two. The route that AC uses was the best route that AC and I independently found (he capitalized on it, I didn't). Is there a better route? If not, then (excluding glitches) maybe a little under 1:40 is the realistic best, but there's room for it to go lower with a better route.

AC and I used a map of the level (overhead shot via unity decompilation) to find routes -- IDK if that's still around in discord, but it should be in my strats and analysis video (tho probs always with some stuff on top of it). We used path length as a way to find shorter routes, you can use something like inkscape or illustrator to do this (this method isn't perfect -- doing a 180 in SSOL is expensive, but smaller angular changes are often okay; path length doesn't account for the change of direction).

I made this in December discussing/analysing AggressiveCombo's recent WR.

I've added a new category for the modded client. The rules read:

The modded client can be found at https://github.com/XertroV/speedy-ssol/releases

The latest version of the modded client should be used, though there is some leeway after a new version is released.

• Collect all 100 orbs in the game
• Time is measured using the in-game timer to the millisecond
• Runs are ranked according to the in-game time shown after 100 orbs are collected
• Submitted runs should should the in-game timer at all times, though some leeway is provided if you accidentally hit 'T' (just re-enable it when possible)

Videos of runs should start before the game world is loaded and should include the all-white end screen (which shows player time and world time).

Runs may be rejected for poor recording quality or excessive background noise (especially if it would make the detection of various cheating methods harder, e.g. splicing).

Runs may be rejected if the runner pauses during the run (which pauses the in-game timer, too).

I've updated the main category rules to be a bit more explicit. They now read:

Collect all 100 orbs present in the overworld. The in-game timer used to measure speed -- it starts when you first move. Runs are ranked according to the in-game time displayed upon collecting all 100 orbs.

Videos of runs should have clean in-game audio and any important details in the UI should be visible. Runs that have background audio or obscure/crop part of the game window may be rejected. A mic is okay if it doesn't interfere with the in-game audio.

The preference is for videos of runs to include:

• at least part of the loading screen (prior to the runner gaining control and starting in-game movement)
• the final end screen with an all-white background that shows both player time and world time

Currently the rules are:

Collect all 100 orbs present in the overworld. Timer starts when player enters the world, in-game timer used to measure speed. Runs ranked according to in-game time displayed upon collecting all 100 orbs.

There's one problem with them atm: the in-game timer starts when you first move, not when you enter the level. If we're using the in-game timer we should take out the part about when it starts (because the game starts it for us).

AggressiveCombo suggested some additions on Discord:

• Minimum video capture requirements of 480p and 25 fps
• No excessive stuttering or frame drops
• Upload runs to youtube, twitch, or provide a direct download link
• Runs under 3:00 need clean in-game audio to check for e.g. splicing or other manipulation
• No video of the game play should be obstructued