the video explains almost everything. it's easier to cheat in runs like this than you think.

imo, rules regarding emulator runs need to be more strict, since timescale runs / cheated runs in goldeneye are shockingly undetectable.

i'm not a good runner, but if someone more skilled would use that technique, it would be a shame...

this is good to know, do you have a suggestion towards what should be done in making the rules more strict? I'm more than willing to change stuff around so stuff like this doesn't possibly get through.

i would suggest if someone does emulator runs, the whole frame should be visible at all times. and verify times only when you hover your mouse over the frame and /or move the whole window for some seconds

There are some potential solutions that could be a lot easier than that. First, press F3 and you'll see the frame time. At 60 frames per second, that's 16.6 milliseconds per frame. If you timescale to slow down the emulator, the frame time goes up because each frame lasts longer. So it's an easy way to tell if someone is slowing the emulator down. There are some other solutions too but nothing concrete yet.

Considering that the game naturally has a slight delay between the sound and your actions, would lining up the sound with the game post-recording still be considered cheating despite playing the game legitimately?