4 HN users recommended this demo4 months2020–2025score 4.5
Years with an HN recommendation, 2007–2026
HN points to it as the standard demonstration of arbitrary code execution on a Game Boy, and of glitches and bugs being turned into a working computer.
A tool-assisted speedrun of Pokemon Yellow by MrWint that uses arbitrary code execution to push Game Boy hardware to its limits. Through crafted inputs it injects code and ends up running other programs, such as Tetris, inside the game.
“One of the crazier uses of ACE in Gameboy Pokemon games exploits” (HN, 2022)
One of the crazier uses of ACE in Gameboy Pokemon games exploits is this "speedrun", by MrWint: [this video] ([TAS] Pokémon Yellow - Arbitrary Code Execution) I've timestamped the part where the actual exploit begins, after all of thesetup. It's worth mentioning that this isn't faked or edited in any way, and it's possible to download the input data and replicate on a emulator yourself.
Genuine, unedited Pokemon Yellow exploit, replicable on an emulator.
It mentions Pokemon Yellow, but really any code run isn't really "run in the game" more so that it uses bugs to hack together alternate instructions for the game boy to execute. Good example: [this video] (skip to 1:20 for craziness)
Shows bugs hacked into alternate Game Boy instructions.
Sometimes even after you've come up with the exploit, you can create something really beautiful for the console to run afterwards. Pokemon Yellow: [this video] Super Mario World: [link]
Something beautiful running on the console after the exploit.
At the end of the day, if you look at a low enough level in the stack, there are no types. In a very concrete way, types are a high-level idea, and if the high-level stops matching the low-level, then bugs crop up. See for example Tetris implemented in Pokémon Yellow via runtime code injection: [this video] Their compiler missed that! So I think there's good reason to switch from talking about types as "assumptions", and think of them as compile time "assertions". Something lower-level in the stack could break the high-level code, but that doesn't make the high-level code useless, just imperfect.
Tetris injected into Pokemon Yellow via runtime code injection.
Arbitrary Code Execution TAS like Triforce% or this Pokemon Yellow one[1] are more or less demos that target both the console and the "host game". I would say even some non-ACE ones like this Brainage TAS[2] are demos :D [1] [this video] [2] [link]
Video list and Hacker News comment labels from HackerTube (prompted by @karpathy), released under ODC-By 1.0, built on the open-index/hacker-news archive. Hacker News data is provided by Y Combinator; comments remain the work of their authors. Video titles, channel names and thumbnails belong to their creators and are shown via YouTube. HackerTube Watch is an unofficial edition. Data export of 2026-10-31.
![Frame from [TAS] Pokémon Yellow - Arbitrary Code Execution](https://i.ytimg.com/vi/Vjm8P8utT5g/hq2.jpg)
Plays via YouTube's privacy-enhanced embed
6 Hacker News comments
From the HN archive; up to 20 kept per video, favoring different commenters. Recommendations first.
Citations, criticism and jokes