Anomaly Log Connect 4 Leaderboard 9/11/22

First off, the WR has 'changed': it was never Fire Mario's run, it remains Alfygator's of 5 years ago now tied by BeetZero.

This board has been wholly mismanaged. It's a meme and a bit of fun, but mods and runners must always practice good housekeeping. Forgive me using a bit of privilege to post this in public; I am definitely not the speedrun police. SRC is the problem, not the mods who are unsure when things are mistimed - but this butchery should be kept here as an audit cleanse.

Responsible user: Cantrick

Failed to accurately retime run https://www.speedrun.com/c4pt/run/zn43l4vm , runner disadvantaged.

Responsible user: SickMyDuck

Misinput subseconds run https://www.speedrun.com/c4pt/run/z1pdw5gz , runner not at fault. Failed to accurately retime runs including: https://www.speedrun.com/c4pt/run/yv6r2pxz , runner heavily disadvantaged as this is his actual PB! https://www.speedrun.com/c4pt/run/yok7epjz , runner not at fault. https://www.speedrun.com/c4pt/run/y67j1e0m , runner disadvantaged. https://www.speedrun.com/c4pt/run/yor7qk5y , runner heavily disadvantaged by a second on PB!

SickMyDuck also self-verified a super choppy vid of his own. This is not good practice except as a last resort and the quality is so poor that a manual retiming adds half a second. As this run is at the bottom I have retained the original submitted time - a mod who can be so useless as you see above is incapable of cheating a run such as this.

Responsible user: yp General failure to maintain the board as the super.

Failed to accurately retime runs including: https://www.speedrun.com/c4pt/run/mk3q273z , which is NOT the WR. https://www.speedrun.com/c4pt/run/m3d2kggz , runner heavily advantaged, runner not at fault. https://www.speedrun.com/c4pt/run/mk30pe1z , again affecting a runner's displayed PB as above, runner not at fault.

Misinput subseconds run https://www.speedrun.com/c4pt/run/yv65vd4z , runner not at fault.

1 run had some choppy video but has a frame counter clearly displayed throughout, which made verification possible!

3 runs started from a savestate to the splash screen. It's impossible for them to have gained an advantage. No penalty.

1 run's video is no longer available. No penalty.

As a counterpoint to that, a special thankyou to JoePulito and DBcade - the only two runners on the entire board who showed a reset and the difficulty setting they played at. New runners can check their runs for excellent examples of clear videos, well done gents! Doughnuts are on me if we're ever in the same place.

Melwing's run with the start chopped off has been re-rejected as it was originally self-deleted. efhiii's run is kept as I have no reason to disbelieve the submitted time.

Runners should always be sure to submit valid videos.

Addressing points raised in another thread about specific runs:

1. "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." MortimerNova's run has a video quality issue that makes a vid-frame based verification impossible, but the run shows the mGBA frame counter. Mortimer submitted a correct time of 10.76 and the run was mistakenly marked as 10.076 - any run marked without subseconds to 3 places bugs and the site marks it with leading 0's in the wrong places. His run frame counted to 10.748 and he was innocent.

2. "And finally, 6th and 1st places started their timers when "Player 1 is on blacks" appeared." This is true but moderators are always responsible for retimes. Both runs have the start point in vid so they have been correctly timed.

3. "(also, 2nd place used save state, so he could eliminate RNG and always start with black, but I guess it's not that important)" Agreed as a principle. Runner gained no advantage except sanity but a rules edit has been added to prevent this in future as good practice.

I have now confirmed all retimes. Again, big apologies for the shift. Now we have a pretty and accurate board, so please feel free to start new runs. If anyone wants to know more about the run times, please ask. The board can be transparent because I don't want anyone doing shintysixthousand resets for this.

Runs START on the black frame after 1P start is selected, before 'black red first' screen. Runs END when Connect 4! appears. Any run from now that uses a savestate, or doesn't show a save and quit from the game, or doesn't show a start from the game choice screen, will be rejected.

Any top time ~10.1s or lower MUST have a 60fps recording and a frame counter, or be rejected. That's going to prevent this clusterfuckery recurring. You can send raw 60fps files to my Discord if YT won't encode that for you. Please don't use YT Shorts as I can't use the YT frame timer with it.

Because this game is being timed down to the frame, I have taken the run times and re-expressed them as multiples of the frame rate.

Thanks!