In the individual level practice, the time displayed after completing levels is unreliable.

Example 1: 158 frames (from start of fade-in to door entry) = 5.98 seconds

Example 2: 160 frames (from start of fade-in to door entry) = 6.66 seconds

2 frames should of course not make a 0.7 second difference. And this sort of anomaly happens very often in practice mode.

If this is only an issue that affects practice mode, it isn't a big deal. But if the actual in-game timer has the same glitch, then it is a major issue that invalidates all speedrun times.

I've never noticed that before, hopefully it isn't something that occurs in the full game. Any chance it could be different on different versions of the game? (PC vs Web for example)

Good catch! It appears this time discrepancy could be caused by a minor bug with the code that shows the timer as a string.

If the timer's leading milliseconds digits (0.XX) are zeros, then these zeros are not displayed.

So in your second video with the time displayed as 6.66 seconds, I believe the actual time is 6.066 seconds.

If this is the case, then this display issue affects times where the milliseconds part is less than 100.

@yokoboko_games could you please take a look at this timer display issue when you have a chance? Thank you!

@Protongue I just checked and you are correct. 60 ms will be shown as 0.60 and not 0.060. Ooops, sorry about this. Will upload new version asap.

Do you guys want me to nuke the speed runs?

Edit: Fixed with 0.3.1b

Thank you Yoko!

From my understanding of the issue, I think it's okay to leave the current speedruns. Fortunately, all current leaderboard times are unaffected by this timer display issue since they all have 100+ milliseconds. It is fairly easy to detect the display issue too: if there are fewer than three digits displayed in the milliseconds part, then the leading zeros are missing.

Unless there is another timer issue, I see no problem here.

In any case, I'm okay with whatever you all feel is the best decision.