We need to agree on a single event to start the timer at. I see three options right now. Unless someone knows how to create an auto splitter (I do not).

1. When you push new game. My opinion is to not use this because each computer actually loads into the game at a different speed. Grimelios mentions that his is about 10 seconds. Just tested on mine and it was closer to 16 seconds. This is too big of a gap

2. After skipping the opening cutscene. I have been starting my timer right when the black begins to fade to colour and the music begins.

3. Wait for the game screen to fully load in and start timer with your first input.

Are we sure that load times are significantly different after starting a new game? Starting the timer on new game would be consistent with most other runs I've done, but if there are differences that we can't get around, I'd agree. With Ori, I know the game took a while to load on your first new game of the day, but after loading once, it was always fast, so that could be something to investigate as well. If there really are significant differences, then I'd prefer the third option since that's pretty easy to time accurately enough.

I've written an autosplitter with help before. I'm sure I could figure out how for this game as well. That said, I don't think I want to take the time and effort at the moment with everything else I have going on.

Updating here to say that we have an auto-start and load-remover now for anyone playing on pc. (look under Resources)

For those playing on other platforms this means that the Glitchless timer will start from first input. Any% will start when the loading bar disappears (a couple seconds before you normally get control) because we have the control glitch which can allow earlier movement

Control glitch may work differently on consoles and prevent the quick start. Will need someone else to confirm as I do not have access to this.

If it is indeed different/impossible then we will switch to starting the timer at first input