these are tests i performed on different browsers on timing level 1 (deviations are due to user error)

firefox: 2.3-2.5 seconds edge: 1.6-1.8 seconds chrome: 1.8-2.0 seconds brave: 1.8-2.0 seconds

these tests did not seem to change based on if i was using turbowarp or not

so uhh, use edge for like, 5% faster times

Cool Maybe I'll put a suggestion for people to use edge. ether way, I have no idea why that happens.

Looked at it and the problem is purely with scratch's built in timer. So this wont be getting fixed unless scratch fixes it themselves.

yeah i assumed it was a scratch thing. thanks for responding, guys! fun little speed game you made, eevee :)

Thanks, I made it in less then a day because my Cousin made a game like it so I had to show him up. Working on a boss game that will be requested to Speedrun.com after the achievements are made. Glad you had fun playing my game :3

oh yeah i made that game

I did some tests myself (timing from start of a full-game run to the screen loading the 2nd level) and both Chrome and Edge give a time of 1.81X (without carrying over momentum) while FireFox always gives a time of 2.5XX