Hello. Most might have figured out that the In-game time counts by frames so times are accurate to .016/.017 of a second. Because of the way frames line up, 2 runs with the same amount of frames might be 1ms different because of the decimals. A run that starts at 1.000 and ends at .016 and another that starts at .033 and ends at .050 are both one frame but because of how it works one is 16ms and the other is 17. I was wondering what should be done in cases like that.Either put the 2 runs together as tied or take into account that extra ms. I personally think they should be put together since they took the same amount of frames

Times like that should count as the same time, and adjusted to any multiplication of a 1/60 frame: 0.016, 0.033, 0.050, 0.066, 0.083. I created a new version of the game with a level timer (I will properly advertise it later), so this can be used for accurate timing as well.

https://or321.github.io/noadev-mini-push/

so does it mean that the runs like mine in level 3 that have 1.917 and are in fourth place should be edited to 1.916 and put in first place tied?

That's correct. Also the 2.267 run should be retimed to 2.266. I contacted the moderator about it.

i actually didnt know that. Is that the case for the entire mini series?

all but sticky