So, I checked first 8 runs on leaderboard.
First thing that I noticed is that time based not on frames, but timer that they put on screen.
Second thing, frame counter and timer, that guy on 5th place have, skipped like 100 frames at the end of his run, for some magical reason. And his actual time is 11 or 12 seconds.
And finally, 6th and 1st places started their timers when "Player 1 is on blacks" appeared. And everyone else started after choosing "One Player". So, based on avidemux and starting time 1 frame before black screen. 1st place has 10.000 and 6th has 11.100.
Can someone please fix that?
(also, 2nd place used save state, so he could eliminate RNG and always start with black, but I guess it's not that important)
Hi Beet! I was made a mod recently and had made a post about these issues. I got no responses until you, so now is a good time to overhaul the board. I agree that timing methods are highly inconsistent as of now. Thankyou also for pointing out about the savestate!
I will meanwhile begin retiming all runs to the same start/endpoints and spreadsheet the results. I'd welcome your input on what those should be.
I have made contact with yp and we will have the board resolved soon. If any runners have suggestions feel free to share!
I did some runs on BizHawk with inputs displayed. For starting point I used 1 frame before black screen appears (after choosing "One Player") and first frame when "Connect Four" appeared as endpoin. Those should be good enough, I guess.
Also, most runs didn't show previous attempt/reset, so we can't tell how many of them used save states.
True, we have many many runs for Perfection and I have no reason to retroactively enforce a reset because it's very obvious there was no manipping, but we can request a reset first in future.
Here are some frame times between states for future transparency. Whenever runners are curious about a run's timing, refer here.
Connect 4: Screen goes black both at 1p select, and Black/Red first, two frames after input. A connect 4 starts flashing at 16 frames after C4! appears. For C4 therefore there may be a +-1f timing discrepancy if existing runs are not recorded at 60fps. Future runners be aware!
Perfection: Screen goes black 2 frames after 1p start input, and the selector hand appears 5f after 1p input. The P for Perfection appears 5f after last move input, and the word starts dancing at 166f after last move input. This means I should be able to perfectly retime every run. (Ha, see what I did there.)
Trouble: Board appears 2f after selecting start game Hands appear 3f after
At game win, hands disappear and reappear after 16f, then at +233f the screen turns black (also marks as a lag frame).
With this in mind I'll now start retiming runs.
Hi all, just an update to affirm that I'm retiming runs at the moment, and the retimed board should be live on Friday with a post explaining the changes. Further, if anyone with experience is interested in becoming a mod for the game, or if no experience is interested in learning, please let me know below!
Changelog: 3/11/22 -Removed Cantrick as mod for inactivity. -Removed sickmyduck as mod due to many, many runs verified by him being timed completely incorrectly and inconsistently.
-Removed ms timing from all Trouble! runs as unnecessary precision for a pure RNG game. Retimed runs. -Edited ruleset: all existing board runs use Classic Game, so this has been added as a requirement.
-Edited Perfection ruleset, GCN runs pending edit for framerate. Now retiming runs. (This is the part where petaQ needs his doughnuts.)
Doughnuts acquired!
4/11/22 -Thankyou, thankyou Kapwing for being a reliable way to retime Twitch runs. -Some historical runs noted to have started from a savestate, no advantage was gained as board/pieces are frame-RNG new rule added forbidding this going forward. -All Perfection runs retimed with multiple end frames for precision.
6/11/22 -Final edit underway. -Tweaked Perfection start/end times. A sticky post will be created explaining this change. -Cross-referenced each time via Kapwing and https://slashinfty.github.io/yt-frame-timer/ -Inspecting audit log to understand submission times v board times
Perfection! board fully updated please read forum post in new thread.
8/11/22 -Connect 4 retiming in progress.
9/11/22 -All Connect 4 runs retimed. Preparing anomaly report for stickied thread, and finalising decisions on resolutions.
DONE! See new thread.
