Hi. I have created an AutoSplitter for A Little to the Left. The AutoSplitter(.asl) file is located in Resources > TOOLS.

It automatically splits for each level and timer stops. However, timer start must be done manually.

In the Scriptable Auto Splitter under Layout Settings in LiveSplit, select Origin or Cupbouards and Drawers depending on the speedrun category. As for the game version, currently only v2.3.10 (the latest version) is supported. In the future, we will make it possible to support v2.3.10 or later and earlier versions.

I am also trying to implement Load Removal to remove time differences due to PC specs. However, the game does not have a notation such as “LOADING” or similar, and I do not know where to perform Load Removal. Therefore, we need to define where loading occurs.

Heyo, back from being in hiatus from the game, so sorry about the delay.

That's pretty cool that you managed to make an Auosplitter for the game, and I am a bit more motivated to get back to running the game. I am thinking of changing the leaderboards such that it can display both real-game time and real-game time without loads.

As for the Legacy/Current split for all the main board categories, I wonder if we should keep them separated or merge them since the autosplitter resolves the root issue of longer load times. We may still distinguish runs' versions by adding a variable after merging.

Great work. I'm already using Autosplitter and it really helps my run a lot.

I should mention something related to load-removed time (LRT): for the latest version, it is faster to turn off retry menu than turn it on in Rikyu and my environment. There's about 0.4s difference for each stage. (In my past comparison video with older version, this result is different from my old computer, so computer spec might affect with this issue)

In Rikyu's prototype load remover, we can only detect loading flag when we turn on retry menu. For current specification afaik, the flag becomes active when we click the arrow in retry menu. If we want to use the load remover in Any% without retry menu, we need to find out other flags (e.g. stars' appearance ~ transition of background color) and add information to Autosplitter too, and this may take more time. (I think Rikyu already working on to solve this issue, according to his comment on Japanese speedrun community)

To add to this, in prototype load remover, we cannot detect the loading time of the first stage. If we were competing for accuracy to the nearest tenth of a second, this issue is also worth considering. However, in the current leaderboard situation, I think just reducing the overall delay in the other stages would be sufficient.

I personally think fine about merging category and adding version variables when the load removing features becomes available. Thank you for responding to runners' requests every time.