After looking into the game more carefully, these are the new timings for any%
- Timing starts on first frame of seeing workshop
- Timing ends on first frame of the dashboard loading screen when going into the sea cutscene
- All glitches are allowed
Retimes & Autosplitter
Since this is all about introducing milliseconds to the leaderboards, current runs will be retimed according to these new rules and future runs will be retimed if they're very close to another run. There has also been an autosplitter developed in accordance to these new rules and you're encouraged to use it.
The autosplitter has been tested on the Swedish and Finnish versions on two different systems and will be added to the Livesplit database shortly, but I can't guarantee that it will work for everyone. Using it together with Dxwnd is not a problem, but it definitely will not work with the German version as none of us have it so support has not been added at all.
If the splitter isn't working for you, please contact me and I'll work out a fix.
Starting timing on workshop instead of the intro cutscene is because at that point, the engine technically hasn't switched scenes from the main menu. Furthermore, the intro cutscene plays when loading any file regardless of it's a new game or not, and as such it is considered part of the main menu and not the game itself.
The end timing is a bit more complicated; we'd like to end timing on the first frame of seeing the sea cutscene, but as it turns out it is possible to skip seeing this screen altogether if you alt-tab during the dashboard loading screen. In order to accomodate people doing this by mistake we explored a few options that involved counting the dashboard frames, but it turned that not only is the amount of these frames displayed inconsistent on individual systems by 1-2 frames (at 60fps), it is also inconsistent across different systems. Since all of these options we could come up with depend on the dashboard loading screen anyway, we decided that this should be used for the end timing.