I think we need to discuss saveload timing in segmented runs. Since it appears multiple segmented runs are timing them differently. I’m fairly sure one or two used the idea of 1 saveload = 1 tick, most likely based off an assumption from RTA runs. I believe some runs used a demo based time per save load, which supposedly displayed 0 tick save-flags, though appeared greater when checking the save files themselves. Finally, other runs are using the save files as the definitive method of timing.
With at least 3 different methods of timing voidclips/saveloads all bearing different results, I think it’s important to discuss a way forward to prevent future mistimed void clips and saveloads. Hopefully this discussion would bear a definitive way for void clips and saveloads in segmented runs to be timed, and potentially retimed.