A fan-made Banjo-Tooie PC port appeared, worked and immediately started a fight. That sequence is the whole story. The new unofficial recompilation promises widescreen, higher refresh rates and native performance, yet the people behind the celebrated Banjo: Recompiled project are furious about how it was made. Their objection is not simply that artificial intelligence touched the code. It is that years of communal work were treated as raw material for a sprint.
The dispute has been framed as another referendum on “vibe coding,” but that phrase is too blunt to explain what happened. Fan-port scenes run on trust: researchers document old hardware, volunteers reverse-engineer obscure behaviour, toolmakers publish reusable frameworks and maintainers spend months fixing edge cases. A tool can be open for reuse while the people who built it still expect credit, care and an honest account of the process.
Two projects, one very different philosophy
Banjo-Tooie: Recompiled is a separate project that uses N64Recomp to translate the original Nintendo 64 game into native code, with RT64 handling rendering. Its repository says players must provide their own legally obtained US ROM and lists the port as playable from beginning to end on Windows. The project is licensed under GPL-3.0 and credits multiple upstream projects.
Reporting by GamesRadar says its creator acknowledged that AI tools generated substantial portions of the code and assisted with engineering and review. That disclosure is the line that turned a technical achievement into a cultural flashpoint.
Darío, who led the separate Banjo: Recompiled project, stressed that his team had no connection to the Tooie release. His repository contains an unusually direct no-AI policy: the team says it has not used generative AI for any purpose and bans contributions made with GenAI tooling.
In comments reported by VGC, Darío called AI ports a “race to the bottom” and said throwing AI at human research, frameworks and renderers was disrespectful. He also said his group had already expressed interest in building its own Tooie port and would take the time required for a polished result.
Open source does not erase social obligations
Licences answer what code may legally be reused. They do not settle every question about reputation, attribution or community stewardship. That is where this argument lives. The AI-assisted project may satisfy the text of the licences while still colliding with the norms of the people whose work made the shortcut possible.
The practical concern is quality as much as principle. Banjo: Recompiled advertises accurate effects, faithful audio, broad aspect-ratio support, a dual-analogue camera and extensive mod support. Those features depend on understanding the game deeply enough to modify it without breaking the behaviours players remember. A port that boots is a milestone. A port that becomes a stable foundation for mods is a different standard.
That distinction should sound familiar to anyone following the wider AI debate in games. POPTOPIC’s look at Capcom’s supposed “AI game engine” controversy showed how quickly a compressed phrase can flatten the difference between assistance, automation and authorship. In this case, the developer’s own disclosure makes AI involvement clear; what remains contested is whether the resulting speed justifies the process.
Players should want both access and accountability
It is tempting to resolve the argument by saying players can choose whichever version runs best. That consumer answer ignores why these ports exist. Nintendo and Microsoft have made Banjo-Tooie available through official ecosystems, including Xbox, but fans pursue native ports for preservation, ultrawide support, lower latency and modding freedom. Those benefits come from a community, not from a content dispenser.
The better test is transparent provenance. Which tools were used? Whose research was incorporated? Which parts were generated, reviewed and tested by humans? What happens when an upstream project changes? An AI-assisted port that answers those questions honestly can be judged on its engineering. One that obscures them asks users to trust a black box built on visible volunteer labour.
Retro revivals already run on rumour and longing. Fans waiting on a possible Ape Escape return understand how much affection can collect around dormant characters. The Banjo dispute shows the other side of that affection: people care not only that a beloved game returns, but how it is handled.
For a wider view of modern PC presentation, our SiN: Reloaded review shows what careful restoration can preserve. Banjo-Tooie deserves the same patience. Speed may win a release race; stewardship determines which project people will still trust after the first build.
About the author
The conversation
Be the first to join the conversation.