"It has no place in my world": Analogue Pocket SNES emulator dev says AI-powered hack is loaded with slop code and wastes "time and brainpower"
"Do not do such a thing again"
One of the best parts of the Analogue Pocket is openFPGA – a fancy name for supporting an array of open-source, homebrew emulators. But as with seemingly every corner of the retro dev scene, the makers of these FPGA emulator cores are having to contend with low-effort, vibe-coded slop from would-be contributors. You can pencil in the dev behind the SNES emulator for Analogue Pocket as one of the many annoyed by having to deal with all this AI-generated code.
Yesterday, a contributor going by nasonliu contributed an "experimental MSU-1 streaming" feature for the Pocket SNES core. The MSU-1 is, in essence, a fictitious enhancement chip for the console. It never existed in real life, but emulator developers created it as a standard that would allow Super NES romhackers to add CD-quality audio and similar improvements to various games.
"If it works, that's pretty cool; I didn't think I would ever see this implemented," says agg23, the developer who ported the SNES FPGA core to Analogue Pocket. I think you can sense the "but" that's coming here, though. "You sent me a nearly 50k line diff, unasked for, completely LLM built, and you somehow expect me to review it," agg23 continues. "There is SO MUCH unrelated garbage here."
In other words, this MSU-1 feature consisted of 50,000 lines of machine-generated code that agg23 would've had to manually review before adding it to the emulator core.
"This kind of behavior is not acceptable," agg23 adds. "You are infringing on the time and brainpower of people by pushing 'your' content that little/no of your brainpower went into; completely unrequested. I hope for the sake of all responsible maintainers that you do not do such a thing again. Again, I think it's cool that you and your LLM supposedly got this to work. It has no place in my world."
You might recall hearing a similar sentiment from the devs behind PS3 emulator RPCS3. They begged contributors to "stop submitting AI slop code" earlier this year. RPCS3, it should be noted, does not ban contributors from using AI at all, but it does demand that devs understand the code that they make from top to bottom before submitting it.
Plenty of coders swear that AI is simply a tool that makes coding more efficient. But in fan communities creating emulators and other fresh ways to play classic games, experienced devs are now being bombarded with AI-generated code from newbie vibe coders who don't even fully understand what they're making.
Weekly digests, tales from the communities you love, and more
Dustin Bailey joined the GamesRadar team as a Staff Writer in May 2022, and is currently based in Missouri. He's been covering games (with occasional dalliances in the worlds of anime and pro wrestling) since 2015, first as a freelancer, then as a news writer at PCGamesN for nearly five years. His love for games was sparked somewhere between Metal Gear Solid 2 and Knights of the Old Republic, and these days you can usually find him splitting his entertainment time between retro gaming, the latest big action-adventure title, or a long haul in American Truck Simulator.
You must confirm your public display name before commenting
Please logout and then login again, you will then be prompted to enter your display name.