The fact that we have a run that's a full minute faster than this now is insane
@TheEgglet it's easier just to have all individual runs in classic mode for the sake of simplicity.
I'll be able to add you when Mace gets online
@TheEgglet @Daewe You are both being added as moderators. You can still submit runs as a moderator, you just need another moderator to verify it for you. You both know and use YT Frame timer, that is what I would like you to use for verification.
The current frame timing rules for individual levels will now be the following:
Timing an Individual level run:
Timer starts on the first frame in which the level resets, and the yellow "START" ring first appears
All currently submitted Individual level runs should be re timed using these rules to your best ability
I believe the timing rules for the full runs are still viable
@TheEgglet If you could provide an example of an individual level timed with your criteria, that would help me understand what exactly you're recommending. If the "blue frame" after the last bubble is popped has a consistent time gap between the last bubble popped and the frame appearing, then I would gladly allow that change.
As for retiming, I would like for you to become a permanent member of the staff team, you have much more experience running flash games than I do. Plus, I dont have much time to verify this many runs constantly. If you have any questions about mod let me know, otherwise I'll give you perms
For individual levels, level 1 is going to be notoriously hard to time accurately and I dont believe there is a method that will be able to time level 1 specifically as accurately as possible
Former time was incorrectly started later than intended, time has been adjusted
Mod Message: Time starts at 2.800 and ends at 318.083 at 60 fps to get a final time of 0h 5m 15s 283ms. Retimed using yt-frame-timer
As far as your 2nd comment, I am totally open to this idea but I would require a bit of help to retime the 60-70+ individual level runs that have been submitted. Easier to start now than later. My time zone is CST Gmt-6 so any delay in response is because of that
Atleast it's supposed to. I may have messed that bit up
@TheEgglet Your wr time is started on this frame, which is the first frame that a slash from the mouse input is rendered
This didnt come across my mind, I'll be adding that to the rules
I have revised how we time our runs, all runs will now be frame timed upon verification. The current criteria is as follows:
FOR INDIVIDUAL LEVEL LEADERBOARDS:
Timer starts on the first frame in which the first slash is rendered
Timer ends when the last bubble is popped on the level
FOR FULL LENGTH any% or arcade%:
Timer starts on the first frame in which the first slash is rendered
Timer ends when the last bubble on the final level is popped
I feel this is currently the most reliable and accurate way to time runs of all categories. Any suggestions, questions or concerns can be sent in this thread. This will all be posted in the Game Rules and Category rules as well.
Mod Message: Time starts at 0.667 and ends at 6.233 at 60 fps to get a final time of 0h 0m 5s 567ms. Retimed using yt-frame-timer
Mod Message: Time starts at 0.700 and ends at 2.333 at 60 fps to get a final time of 0h 0m 1s 633ms. Retimed using yt-frame-timer
Mod Message: Time starts at 3.000 and ends at 13.900 at 60 fps to get a final time of 0h 0m 10s 900ms. Retimed using yt-frame-timer
Mod Message: Time starts at 0.950 and ends at 2.000 at 60 fps to get a final time of 0h 0m 1s 050ms. Retimed using yt-frame-timer
Mod Message: Time starts at 1.250 and ends at 5.733 at 60 fps to get a final time of 0h 0m 4s 483ms. Retimed using yt-frame-timer
