AI Built a Smash Bros. Port in 25 Days. Who Actually Did the Work Is Another Story.

On April 30, developer JRickey published “BattleShip” to GitHub — a native PC port of Super Smash Bros. 64, running at 60fps, built in just over 25 days. The repository lists four credited contributors: JRickey, Claude Opus 4.6, Claude Opus 4.7, and GPT-5.5. Nintendo’s lawyers are presumably in emergency sessions trying to figure out who to sue. Everyone else is arguing about what this means for gaming.

The honest description of what JRickey did: he acted as project manager for two AI models. According to WCCFTech’s primary coverage, he dispatched Claude and GPT-5.5 agents to write and test code autonomously “while he did other things.” The AI models handled the C/C++ source, managed the build pipeline, and debugged the output. That’s genuinely new — not because an AI generated code (every developer has been doing that for two years), but because an AI agent completed a multi-week, multi-file software project with minimal human input and shipped something playable. The gaming “Idea Guy” has always existed. Now he has tools that actually build the thing.

There is, however, something buried in the technical details that the “AI built this!” narrative actively obscures. The port runs on top of “ssb-decomp-re,” a human-driven decompilation project created by a community of reverse engineers — a project already 99.7% complete before JRickey was involved. The AI didn’t reverse-engineer Smash 64 from scratch. It wrote porting glue on top of years of painstaking community work done by developers whose names appear nowhere on JRickey’s contributor list. The AI didn’t reverse-engineer Smash 64. It wrote glue on top of years of human work — and the humans didn’t make the contributor list.

The legal angle is the one Nintendo’s team actually has to solve. The repository ships zero Nintendo assets. The AI wrote clean C/C++ source that uses a tool to extract proprietary data from a user-supplied ROM at build time — meaning Nintendo’s intellectual property never travels with the port itself. Nintendo has aggressively shut down emulation projects before, but they’ve always had a human developer to target with a DMCA notice. If an AI agent authors the relevant code and the human only directed the project, the traditional “who wrote this?” framework doesn’t apply cleanly. It’s the legal equivalent of suing the foreman because his crew built something without permits. You can argue the case — but it’s not the same case Nintendo has won before.

The broader implication is what studio executives are already circling. A solo developer with no coding of his own directed two AI agents to ship a playable retro PC port in under a month. That argument will appear in the next round of game studio budget meetings. Google Cloud data shows 90% of game developers are already using generative AI in their workflow as of April 2026 — this project is the first time that number produced something visible, viral, and impossible to ignore. It’s the kind of proof-of-concept that ends up in layoff announcement decks a quarter later.

JRickey built something impressive. He also built it on top of a decade of community work he didn’t acknowledge, using AI co-authors he credited over the humans who laid the foundation. That’s not a gotcha — it’s just the cleanest possible demonstration of where credit flows when AI is in the room. Toward whoever holds the GitHub account.

Sources: WCCFTech · Overclock3D · Time Extension