The current system lists 2 of essentially the same time. speedrun.com doesn't allow more than 3 digits except in ms and hours, so I'm displaying the actual time in converted minutes/seconds/ms as the "real-time" category and the timer time as hours/minutes in the "in-game time" category. I know it's awkward and sloppy, but I doubt the entire site with update to comply with one game. There isn't much I can do about it. If you have thoughts or objections, let me know. My problem with the in-game timer isn't so much its use; it works very well for its purpose, it's that it stands for both seconds/ms (last digit dropped) and minutes/seconds (when standing still) and varies wildly, so it's not super clear what to do. being able to compare both the timer time you actually see displayed and the equivalent in minutes/seconds was the best I could come up with. I realize it makes it look like we've played the game a lot longer than we have, so maybe I should swap the main category to be displayed to the """real-time""" conversion, but I think this is unintuitive when looking at the times. It is easy to think "hey, they got 249.22, I could beat that" while looking at the real-time equivalent requires conversion to tell exactly how impressive the feat is. This could be solved if we had more digits for minutes and seconds, but unless we do, this seems to be the only way to preserve both the actual timer and the actual time it represents. The real-time timing, of course, will not be effected.