It has been discovered that playing with high framerates saves a significant amount of time during the turn transitions, as demonstrated here:
Though the exact amount depends on your framerate, this can be approximated to save at least 13 seconds in a full run. After some community discussion in the Discord server we have decided that, as the amount of time saved is framerate dependant, we will be implementing a requirement to use the 'Frame Limit' option in the game menu, in order to ensure a level playing field.
We will adjust runs that were already performed without Frame Limit by adding the time they would have lost if they had Frame Limit active. As we need to double check every run on the leaderboard, this process will take some time. All 2-Island / Easy Runs in the top three of their category will receive exact frame counting to ensure the adjustment is completely accurate; for the sake of moderator sanity, we will use some approximation for runs further down in the leaderboards and in less popular categories.
To reiterate one last time, it is now mandatory to use Frame Limit during your runs.
I'd probably also say that this should be done with the All Squad% as well because this is where the most time would be saved because of this discovery, though I know it would be a lot of work to do so.
As the current All Squads record already has Frame Limit on there's little urgency there. We may get around to retiming SkipMcLazy's run as it might turn out to be slower than Zetnix's, but it is fairly low in our priority list.
Hey folks; in the interest in transparency, I can report that we've gotten enough information to make a hopefully fair adjustment to runs currently on the leaderboard that had the Frame Limit option disabled so that they are more in line with the runs with Frame Limit enabled. On average, the difference between runs with this option enabled/disabled is about 0.3 seconds per turn. So, this means adding roughly 16 seconds to 2-Island% runs with Frame Limit disabled.
Thankfully, only 22 2-Island% runs need to be adjusted, a relatively small number (and actually includes 2 of my PBs), and I have reached out to the folks with times that need to be adjusted through Discord or through speedrun.com DMs, but if anyone has any concerns, comments, questions, feedback, or just generally want to chat about this issue, you're welcome to ping me on Discord.
On a technical note, when calculating how these runs needed to be adjusted, we took both milliseconds and how many missions with one fewer turn (such as train missions) were present in those runs. If there's anyone affected that wants a more involved or granular explaination, please get in touch.
I'll be making the adjustments to the affected runs on the leaderboard over the next few days or so; thank you for your patience as we tried our best to make sure everything was fair and accurate with the adjustments.