Before I begin, I would like to state that I appreciate all of the moderators and the work that they have to continually do to run the page. I do not mean to in any way demean any of the moderators, and I hope that everyone in the community will also follow and keep respecting the moderators.

To start this off, I believe I should give mention of the exact wording of the rules for timing runs.

“Run starts when score changes from 0 to 1. The run ends when your score changes for the last time, right before you enter the portal, which will be either 34 or 39.”

I believe there may be some discrepancies between this and how the different runs were timed. I’d like to first go to a couple runs that have been properly timed, jis024’s 10.517and eloctaviox's 10.633. An important note before I begin is that these runs were both verified by Fibbel7.

So now let’s get into kis024’s run.

Quickly before I go on, it’s important that I mention this run’s video is run at 60fps. As mentioned in the rules, “Run starts when score changes from 0 to 1.” The 227th frame of the video the score is still displayed as a 0, and the 228th frame marks when the score changed from a 0 to a 1.

If we now skip to the end of the run, we consider the run finished when the score changes to either 34 or 39 depending on whether the runner chose to grab the soda or not. In this run, the soda is grabbed, meaning timing ends on the frame when the score is displayed as 34. On frame 858, the score is at 33 and on frame 859 the score reached 34, meaning timing finished on frame 859.

If we now take those frame counts (859-228-1) (we do the -1 to account for the last frame, which doesn’t count normally) we can conclude that the run is 630 frames long, or 10.500 seconds (631/60). This time is just 1 frame off of what is said on the leaderboard, but if we count the last frame (which personally I believe we should not, and in all further provided time will take out. If the mods disagree with me on this one, then that’s all cool and just add 1 frame to all final times) is accurate.

eloctaviox’s run is next, and an important note is that the video is 30FPS. Unlike what they said, the run actually starts on frame 3 of the video. Similarly, the run then ends by reaching score 34 at frame 319. Assuming what he had said was correct, this timing would be correct. His actual time should be 10.500, meaning over a tenth of a second was added to his time from the moderators not checking his run themselves, resulting in him losing his WR tie.

PLEASE CONTINUE READING IN THE TOP COMMENT

Now I’d like to take a look at Kaitou_Yuvi’s 10.133 and my 10.100. Both of these runs were verified by Funado, who appears to have a much more consistent inaccuracy in timing.

Looking at Kaitou_Yuvi’s run, also running at 60FPS, we can see the first frame of the run is at frame 642 and ends at frame 1246. Taking the two and getting a frame count and time, we have 603 frames or 10.033 seconds.

Switching over to my run now, running at 30FPS, we have the first frame at frame 235. The run then ends on frame 535. This provides us with a total frame count of 299, or 9.966 seconds.

I think with these numbers I have proven that there certainly is at least some inaccuracy in the timing being done by the moderators. I will say that I do believe Fibbel7 has been accurately timing all runs, and that the mistake I pointed out was only because he listened to the person who submitted the run. However, I do believe that Funado has been miscalculating the times for some, if not all of the runs he has verified. I do not personally have the time to check every run he has verified nor the other categories, but it does seem that he consistently is about .133 seconds off on every run he has verified. Going forwards, I believe that all runs that have been verified by Funado should be decreased by .133 seconds, or 4 frames at 30FPS and 8 frames at 60FPS. (Likely this is due to the timing being ended when the runner enters the wormhole, not when the score reaches 34/39.) I believe this is the proper course of action to follow the rules that have been specified for us runners, and if not, then the rules should be updated and all previous runs that were verified under the old rules have their times increased.

But like I said before, please do not harass or disrespect the moderators in any way. We should all appreciate the work that they do for this game in giving their time and energy into verifying runs and such. In what I have said, I hope no offense is taken by the moderators, but that the proper course of action still comes through. As mentioned in the first run I examined, I believe we should no matter what specify in the rules whether or not the frame that the score reaches its set destination should count or not, as it does greatly change some scores.

Also massive thank you to Kaitou_Yuvi for pointing this out to me, all the credit for noticing this goes to him.

Sorry for making this two parts, it was the only way I could get speedrun.com to allow me to post this big of a thing

I’d also like to add that the timing on my WR in Spaceland is inaccurate as well. The correct time is 39.067, not 39.133. The run starts at frame 571 (0 to 1) and ends at frame 1743 (137 to 138).

Oh and before you verify my WR in desert pls note that THE RUN STARTS AT 0 TO 1, AND ENDS AT 65, ITS RIGHT THERE IN THE RULES.Because bakil333's run ln desert (15 place) that you verified, IS INNACURATE , YOU WERE 3.462 SECONDS AWAY FROM THE ACTUAL TIME. Run starts at frame no.478 and ends at the frame no.689 which equals to 211 frames, divided by 19 fps = 11.105 which moves him ALL THE WAY TO 13TH PLACE Also remember when you said that the fps is "ALWAYS AT 30"??? Well its not ALWAYS AT 30 FPS. Dmytro's WR on All Levels is 48 FPS,YOU CAN JUST CLICK STATS FOR NERDS TO CHECK THE FPS, and the run ends at SCORE 266 NOT 267, 266 IS THE LAST SCIRE IN THE LEVEL, YOU CAN JUST PAUSE THE VIDEO AT 0:58 AND COUNT. Run starts at 122 frame and ends in 2874th frame. 122-2874 = 2752, divided by 48 = 57.333, not 57.433