I have found a better way of timing the chapter and whole game category runs.
I have learned recently that the timing made for older submitted runs have been calculated incorrectly. I believe most of the runners who have submitted runs to these categories mentioned above have been not only neglecting the rule where you only need to use RTA time if you restart a level, but have also that the framerate of the game plays a big part into how the final time is calculated. Of course this is not necessary for 2.0 as milliseconds have been added at the result of my own personal request to the developers for the sake of the speedrun community as of ver.2.0.4
As a result of moderating Tezca's submissions, I have come to this realisation that we were doing it all wrong and a change has to be made. As of writing this I am currently creating a document that will soon be available in the Guides Tab to those who wish to use it as reference for runs going forward. I may also make a video about this that you could find on my yt channel @jeranuspeedruns, in which I'll post it as a comment when it releases.
And yes this does mean going back and editing all the times from older runs, which will take a while.
Hello there, and happy new year!
There has been some slowdown in speedrun verifications, and that is why I've decided today that we are opening verifier applications. If you think you know enough about Vector and its speedruns and have what it takes to regularly check runs and verify their le