

“You'd imagine it would be stressful,” Ryan told VICE at the time, back when he was claiming everything was all a big misunderstanding, “but when you have nothing to hide you find a way to take a very diplomatic approach to it all. He was, however, allowed to stay in the community. The other conclusion: All his runs were considered tainted and thus invalid, and any future runs would require additional scrutiny. “We all hope we can move on positively from this,” concluded the moderators. “I maintain the position that I ran each of them legitimately," said Ryan, albeit while also acknowledging some technical issues, "and am more than willing to run each of them again to prove this by re-running with multiple camera setups showing either me, monitor, inputs, etc." “There is getting lucky, there is getting lucky, and there is getting lucky back to back to back.” At no point was he defensive, worried about his reputation, or concerned about his previous efforts in speedrunning.” It should be noted that the runner was 100% calm and cooperative with our questions. “Each concern was brought up to the runner one at a time for explanation.

“All parties were calm and friendly,” said the moderators, transcribing their eventual confrontation. Instead, he embraced the call for truth, and struck a shockingly conciliatory tone for someone who’d been called out for cheating. “There is getting lucky,” wrote the moderators, “there is getting lucky, and there is getting lucky back to back to back.”ĭuring his time under the microscope, Ryan did not call bullshit, or show any anger. It’s possible for a person to be blessed with the kind of run that grants favorable RNG over and over again, but what are the chances of that? For Ryan, the enemy always moved the right way.

An enemy moves in a direction that allows them to run down a faster path, for example. Will the skeleton mage attack from the left or the right? Will it be sunny or rainy when you leave the inn? Sometimes, those unpredictable things will go in the player’s favor. In speedruns, “luck” is often called “RNG,” short for “random number generator.” As most players know, video game enemies and environments often have random elements. There was also the question of Ryan’s incredible, impossible luck. But even when it was possible to hear the taps of Ryan’s fingers, they appeared to be slightly behind what was happening in the game. Weirdly-or conveniently-these taps disappeared during the world record runs. Translation: When Ryan was playing, it was often possible to hear his fingers tap the controller before it was reflected onscreen in the game. Sometimes the tap preceded the movement, and sometimes movement preceded the tap.” The inputs and movements were 1-3 frames apart, 7-8 frames apart, and sometimes 13-17 frames apart. Coupled with that, the inputs showed no consistency. One exception is found during the run in the last dungeon, where inputs suddenly appear after not being present all run. “Controller inputs can be heard on many streams of attempts, but are absent in WR runs, despite the fact that the background can be heard through the mic. They require a pixel-level expertise to observe and grasp. There were the technical questions and observations-”odd pauses in movement,” “significant ghosting and video quality differences,” “split timer starts also showed inconsistencies.” These problems would not be visible to the average person, perhaps even the average speedrunning fan. Suspicion led to investigation, and investigation led the community to draft a list of “inconsistencies,” technical issues with the video that could have reasonable explanations but weren’t readily apparent and which Ryan was asked to explain. Questions were raised about the authenticity of the run specifically because it was so much faster than the run before it-eight minutes is a really huge gap for an old video game because players have already spent years perfecting the fastest path In speedrunning, large breakthroughs are possible but uncommon speedruns are often built on one another a few seconds at a time.
