"100% AI-Generated" — The Super Smash Bros PC Port Nobody Asked For Opens the Question Nobody Wants to Answer

The port exists. It runs. TheWizWiki posted the project to GitHub with a headline claim — "100% AI-Generated" — and a playable build of Super Smash Bros (N64, 1999) targeting PC hardware. Time Extension picked it up in its weekly retro recap. The scene noticed. The takes arrived fast. And almost all of them missed the actual problem.

The actual problem is not "can AI write a port." It can, approximately. The actual problem is what a project like this does to the legal and social infrastructure that decomp communities have spent a decade constructing — the infrastructure that makes projects like the Super Mario 64 PC port, the Zelda: Ocarina of Time recompilation, and the Perfect Dark decomp possible and defensible.

What decomp actually is, and why process matters

Decompilation — decomp — is the practice of taking a compiled game binary and reverse-engineering it back into human-readable source code. The goal is not piracy. The goal is understanding: producing a codebase that compiles to a byte-identical match of the original ROM but is written in clean, commented C that humans can read, modify, and port. The legal defense of decomp has always rested on a specific claim: the code is independently authored. Nobody copied Nintendo's proprietary source. Developers read the machine code, understood the logic, and re-expressed it in a new form. That distinction — between copying and re-expression — is what keeps decomp inside the Sega v. Accolade (1992) line of fair-use precedent.

The entire framework depends on process hygiene. Clean-room discipline. No leaked source mixed in. No assets shipped. No proprietary SDK headers pasted into the repo. The decomp communities that have survived takedown attempts — the SM64 project survived Nintendo's legal attention in part because the code was demonstrably clean — did so because they could show their work. Every function, hand-matched. Every commit, traceable.

"100% AI-generated" is not a process-hygiene claim. It is the absence of one.

When TheWizWiki labels a port "100% AI-generated," the immediate question for anyone who understands decomp law is: what was the AI trained on? If the model ingested leaked or decompiled Nintendo source — and large code-generation models have trained on vast GitHub corpora that include exactly this kind of material — then the output is not clean-room. It is laundered. The distinction between "I read the binary and re-expressed the logic" and "I prompted a model that may have memorized fragments of the original source" is not a technicality. It is the load-bearing wall of the legal argument.

The scene's immune system

Decomp communities have spent years building norms precisely to prevent this kind of contamination. The Ocarina of Time decomp project maintains strict contribution guidelines. The SM64 community polices its repos against leaked-source contamination with the seriousness of a biosafety lab. These are not bureaucratic reflexes. They are survival strategies. Nintendo's legal department does not need a reason to send a DMCA notice; it needs a pretext. A single contaminated repo provides one. An AI-generated port with unverifiable provenance provides a better one.

This is the vector that the "cool, it runs" takes are missing. TheWizWiki's port does not need to be legally actionable itself to cause damage. It needs only to blur the line enough that a rightsholder's attorney can gesture at it and say: "See? The decomp scene can't control its own process. The outputs are indistinguishable from copies. The clean-room claim is a fiction." That argument was already being made before AI entered the picture. AI makes it easier to make.

AI is a workflow question, not a morality play

This publication has said it before and will keep saying it: AI in games is a process problem, not a values problem. Studios are not evil for using generative tools in preproduction. They have a pipeline-hygiene failure when those tools leak into shipped content without verification. The same framework applies here, and it applies harder, because the decomp scene's entire survival depends on being able to answer the provenance question with specifics.

"The AI wrote it" is not an answer. It is a black box where an answer should be. Which model? Trained on what corpus? Can you demonstrate that the output does not reproduce memorized sequences from proprietary code? If you cannot answer those questions — and in the current state of large code models, almost nobody can — then you have not produced a clean-room decomp. You have produced something else. Something that may be technically impressive, may even be fun to play, but sits in a legal category that has not been tested and that every existing decomp project has strong incentives to stay away from.

The recomp moment

This lands at a particular moment. The N64 recompilation scene — projects that take decomped code and retarget it to modern hardware with enhanced rendering, widescreen support, and modding frameworks — is in the most productive stretch it has ever had. The tools are maturing. The communities are growing. The legal ground, while never safe, has been stable enough to build on. An AI-generated port with unverifiable provenance does not contribute to that ecosystem. It introduces a variable that the ecosystem's defenses were not designed to handle.

That does not mean AI will never have a place in decomp workflows. It almost certainly will. Automated pattern-matching for function identification, type inference on decompiled output, documentation generation — these are real use cases where AI assists human decompers without replacing the clean-room process. The difference is between AI as a tool in a verified pipeline and AI as the pipeline itself. The first is an upgrade. The second is a shortcut that skips the part that keeps the lights on.

What actually happened and what matters

TheWizWiki shipped a port. It appears to run. The "100% AI-generated" claim is, at this point, an unverified assertion about a process that is inherently difficult to verify. The scene's reaction has been a mix of curiosity and unease, and the unease is the correct instinct. Not because AI is bad. Because unverifiable provenance is bad, and the decomp scene exists in a legal environment where provenance is not optional — it is the product.

The question this port opens is not whether AI can generate playable code from a classic game's binary. The question is whether the decomp community can absorb AI-generated contributions without losing the process-hygiene guarantees that keep it legally alive. Right now the answer is no. Not because the technology isn't ready. Because the verification infrastructure doesn't exist yet. And until it does, "100% AI-generated" is not a badge of innovation. It is a warning label.