It works okay, but it has some problems. The main one is that it doesn't stop between levels. Maybe I'm making a bad assumption here, but I don't think we should count the time in-between levels. When you step on the finish platform and the scoreboard comes up, it doesn't stop the timer, so if you are not quick enough, you can lose time there. I think the main benefit of an autosplitter would be that we can "filter out" that time, so that we can measure only the actual in-game time. It is a step in the right direction, but it still needs some work if we want to only count the in-game time.

The other smaller issue is that if you start livesplit before you start the game, the autosplitter will start the timer when you load into the main menu. This isn't a big deal because you can just reset the timer, but it's something to keep in mind when using it.

oh, nice! I haven't tried it yet, but I'll give it a shot and report back.

There isn't an auto splitter (that I know of) for the game, so it relies on the runner to split perfectly. I think any timer that is overlaid with OBS (like LiveSplit) or added after the run (like with Premiere) is fine, as long as it looks fairly accurate (or you can always just retime it from the video).

BUT if we can get an auto splitter working, then it should be required. However, that brings some other issues. If we want to have an auto splitter, then we need one specific version of the game that everyone uses, because all the pointers and offsets that the auto splitter would use could differ from one version to another.