I believe moogic meant using an iPhone to record gameplay footage, which is perfectly acceptable.

Hello everyone! We've made a few adjustments to the rules:

1. Emulator runners: you must capture the entire emulator including the window border for the submitted video. An example can be seen here:

2. Your submitted video evidence must show the game being reset before the run starts. You can accomplish this using a soft reset (A + B + Start + Select) or hard reset (pressing the power or reset button on your console, or using your emulator's reset functionaility). We are adding this rule because of the recent developments in RNG manipulation. We want to make sure nobody is using save states or other artificial means to start the game on a more favorable RNG seed.

I've updated the rules in the pop-up as well.

At the risk of beating a dead horse, I'm not convinced that requiring livestreaming does anything to prevent cheating. As others have said, it would be super easy to create a TAS or spliced video, then just stream the video to Twitch.

Also, as far as I know, cheating hasn't really been much of an issue in KDL. It doesn't make sense to make rules for a problem that doesn't exist.

First off, I'm glad the KDL leaderboards are getting some much needed attention. I know that a lot of people dismiss KDL as a serious speedgame, but there are a few of us who do take it seriously and would like to compete on a level playing field.

Regarding video proof: I am for requiring video proof for all runs. In my opinion, if you want to submit a time to the leaderboard, I don't think it's too much trouble to ask you to put in a little effort to provide video proof of your time. There are plenty of free or low cost ways to record your run, including using a cheap webcam/phone camera or playing on an approved emulator (how I got started in speedrunning).

Regarding VBA runs: I think it would be best to delete existing VBA runs. It's fairly common knowledge that VBA is not allowed for GB speedruns, even if a game's rules don't explicitly ban it. For people who might get upset about having their VBA run removed, I don't think it's too much trouble to ask them to submit a run using one of the acceptable emulators. Overall though, dealing with existing VBA runs is a minor issue. If the rest of the community is against deleting them, I won't stand in the way. I think there are much bigger issues to focus our efforts on, and I don't want to see us waste too much energy arguing over VBA.

Regarding KDC/3DSVC: There's not a perfect solution here. Having played KDL1 using both GBP and KDC, I feel like the inaccuracies in emulation extend beyond load times and framerate. I know Oh_DeeR is working on getting some video examples to see how DC/VC handle lag, so we'll hopefully know something more definite soon.

I'm not a huge fan of allowing inaccurate emulators on the leaderboard, regardless of if they're official releases or not (just a thought: from a commercial standpoint, it actually makes sense for Nintendo to focus on performance over accuracy when it comes to emulating their VC titles. Most of the people who purchase VC games are playing in a casual setting and would value a smooth, lag-free playing experience over accuracy). On the other hand, I can't say that I would support an outright ban on KDC/3DSVC, and I don't really like the idea of having separate leaderboards that no one cares about. I certainly don't like the idea of leaving DC/VC times unconverted. As Oh_DeeR said in his other post, speedrunning should be about comparing skill with others, not about who is playing on the fastest platform.

Unless some profound inaccuracy is found, I think applying a conversion factor to runs on DC/VC is the fairest way to handle platform differences.

Finally, thank you Oh_DeeR, eBloodyCandy, swordsmankirby, and everyone else who is putting effort into this. If there is anything I can do to help, please let me know.