Yeah just use , and . on videos to move frame by frame, if the fps were higher than 48 there might be a frame before 2.999 and the time would be lower...
damn! Nice Time! The map is starting to be somewhat optimized. Definitely harder than it looks like.
You can't have a map that doesn't allow you to move forward (you also have to press forward for the race to start) but you could have a map design that makes moving backwards the fastest but it would probably have to be short, you could also simply have rules for the level that prohibits from moving forward on the level. All we have is a way to have custom maps that are impossible to create with the editor but modifying the code of the game would be cheating
I've begin the reverse engineering of the map data.
A modified version of base64 (btoa in js) is used to encode information, basically it does a base64 then replaces "+" with "-", the "/" with "_" and removes the "=" signs (oposite order for decoding ofc)
The data works like this: -Starts with "v1n" -Number of characters composing the title of the map as a byte (encoded) -The title (not encoded only url encoded) -Information about the map (encoded)
The map information is basically numbers like the block id and block positions, I haven't yet determined how they are arranged and used I'm a bit tired but I have found the code where it is interpreted.
I'll give more details in the discord custom maps