I understand your point, but there are a few things you can do to prove you didn't cheat. For level 2, if you're able to record yourself and prove that this run would be possible, it'll be more likely to be accepted. In the instance that you beat level 5, this wouldn't work because it's extremely inconsistent.

Is it possible to make a TAS Replay Code Catcher to verify runs? If we can decipher griffpatch's eerie (and complicated) code then it might be possible. Though, TASers could change it a bit so that they don't get caught.

I just noticed something about the replay code:

1. The numbers at the front seem to always start with 1234 (and a bunch of seemingly random numbers).The next part is most likely a player ID (in this case it's player1397).

2. The numbers behind the fourth LJ is the frame that Appel starts moving.

Here's some examples:

For the 1st code, the 4th LJ and the numbers behind it are LJ1, meaning Appel started moving at the frame 1 (or the first frame).

For the 3rd code, the 4th LJ and the numbers behind it are LJ1086, meaning Appel started moving at frame 1086.

Not sure if this information is useful but it's something that I found.

How interesting! The meaning behind replay codes continue to be uncovered... :) I doubt somebody will be able to read an entire replay though.

I guess we have to decipher @GriffPatch's code, what an arduous task... but hey, we might have found something!

Yeah I also noticed a few other things

Can you tell? It might be helpful to stop people from passing TAS's as their own

Here's my theory: For now I'll call the LJ and the number behind them 'LJx', x is a number.

The 4th LJx is the frame that the player clicks and the next LJx is how long the player holds the key (in frame). It could be the same for the 6th, 8th and so on.