Hey there JW,

as you can see in the beginning of the run, there is a cutscene which is not timed out. Also in the past there have been cutscenes that were not possible to time out until a livesplit ingame-timer-update. Then it was possible to time out other cutscenes as well. The rule therefore means: The time is determined by the ingame-timer and cutscenes which are not timed out are part of the ingame-time. But thx for your observation. I'm gonna change the rules (or just leave this passage out) to clarify this confusion for future runners :)

Greetings qd

Even though we have a load remover that brings us equality over most of the loading times between levels, there are still situations that are influenced by the hardware setup of the player. This here apparently is another example of this, but also frame drops or frame losses, the speed with which ingame cutscenes are skipped and so on. Sorrily, it is impossible to take those really minor time differences into consideration. That mostly is the case with any other speedgame as well.

Make sure you start the timer right when you start the game so you dont lose time that way. Also have a look at our forums and discussions about technical timesaves or tricks and stuff.

Greetings qd

I'm not a programmer but I have a suspicion that this time discrepancy is a bug in the code related to trying to pause the timer during cutscenes. To change that it would be required for cutscenes to count as game time (which is not absurd) and someone programmer savy to alter the code.