564K views · Jul 3, 2022 · 1:12:43 · 2 HN recommenders · 3 mentions · discussed 2022–2025
A tool-assisted speedrun of Ocarina of Time at Summer Games Done Quick 2022, using TASBot and arbitrary code execution to reach an alternate ending in about 53 minutes. The run is introduced by its creators and followed by an interview.
Why Hacker News points people here: HN points to it as a stunning demonstration of arbitrary code execution in a console game and of what speedrunners effectively do as vulnerability researchers.
“absolutely blew me away”HN comment, 2025
“absolutely blew me away”
TASBot's arbitrary code execution alternate ending in Ocarina of Time.
I think if they're active in the speedrunning community, then they're already well aware of this! And for a fun additional example to add to this article, you can often find TAS'ers talking about arbitrary code execution. The legendary GDQ run of TASBot's alternate ending to OoT[0] utiziling an ACE exploit they found in that game absolutely blew me away. [0] this video
“a good video that makes this tech more understandable”
Explains the tech with an amazing demo at the end.
they are most likely using a controller hooked up to a bot/laptop that exploits flaws in the code with inputs at high speed (much faster than a human could) that injects code into live games a good video that makes this tech more understandable (with explanations at the beginnimg and an amazing demo at the end) this video and some background link
“Ocarina of Time total control/"Triforce%" (TAS, 2022)”
Ocarina of Time total control TAS.
Some highlights/historically significant examples of this: Super Mario World (TAS, 2014): link Super Mario Bros. 3 (TAS, 2014): link - The same run performed RTA (i.e. by a human using a real controller) at AGDQ 2015: link Super Mario World (RTA, 2015): link Super Mario World "total control" (RTA, 2015): link Pokemon Yellow total control (TAS, 2017): link The Legend of Zelda: Ocarina of Time (RTA, 2019-ish?): link Ocarina of Time total control/"Triforce%" (TAS, 2022): this video (explanation: link )
