Harbour Masters Confirms Years of AI Use in Zelda Port Ports, Sparks Community Backlash

The revelation about Harbour Masters’ use of artificial intelligence tools in their reverse-engineered Nintendo 64 ports triggered significant backlash within the retro gaming community, forcing the team behind the wildly popular Ship of Harkinian port of The Legend of Zelda: Ocarina of Time to publicly defend their development practices.

How the AI Use Was Exposed

On September 16, a post on PC Gaming Wiki alleged that Harbour Masters had incorporated thousands of lines of AI-generated code across multiple ports. A user named “Slopiskillingretrogaming” presented what they characterized as extensive evidence of AI involvement in the team’s projects, singling out the runtime component libultraship as particularly affected. The post gained rapid traction across social media platforms, including ResetEra and Bluesky, catching the team unprepared for the scale of the backlash.

What the Post Claimed

The PC Gaming Wiki post contained numerous code snippets allegedly showing AI tool usage, with some directly referencing Claude. The author further claimed that Harbour Masters had deliberately obscured their use of artificial intelligence by removing co-author credits from code commits. Additional accusations extended beyond code to assets, with the post suggesting certain images in the projects were AI-generated. According to the author, these contributions came from “lead maintainers of individual ports” rather than peripheral contributors.

Community Reception

The allegations resonated strongly with longtime players of Harbour Masters’ ports. Players who had engaged with the team’s work expressed frustration that the widespread adoption of AI tools had proceeded without transparent communication. This discontent spilled into the team’s official Discord server, where members peppered developers with questions and expressed their disappointment openly.

The Team’s Response

Read also: Rare Two-Player Computer Space Cabinet Heads to Auction · 2002’s Landmark Games Redefined Open Worlds, Strategy, and Perspective · King’s Field: The Ancient City and FromSoftware’s Dark Souls Blueprint

Harbour Masters members entered damage control mode almost immediately. Developers dismissed the viral post as “total lies” and “highly untrue,” yet their subsequent explanations revealed the core truth: they do indeed use AI tools as part of their workflow.

Clarifying the AI Role

Developer Malkierian addressed one of the post’s central claims—that millions of lines of code were AI-generated—by explaining the actual process. Rather than directly generating code wholesale, Malkierian described how the team employed a script developed with AI assistance to convert existing code, with human developers verifying the results for functionality and correctness afterward. This distinction proved crucial to understanding how the team integrated AI into their pipeline.

The Long History of AI Integration

The responses from team members made clear that this practice extended far into the past. Developers had been incorporating AI tools—GitHub Copilot, ChatGPT, and other coding assistants—into their workflows for years. When asked which version of Ship of Harkinian remained untouched by AI assistance, developer Briaguya provided an honest non-answer: “I don’t know.” Briaguya elaborated that while they personally avoided GitHub Copilot (which launched in 2021, before Ship of Harkinian 1.0’s release), they had used ChatGPT as a research tool during development across multiple versions. The team could not definitively identify which builds were completely AI-free.

Defining What AI Use Actually Meant

A significant portion of the team’s defense hinged on reframing what constituted problematic AI usage versus legitimate use of productivity tools. Developer Briaguya presented a counterargument to the viral post’s implicit assumption that any AI involvement equaled substandard work, stating: “People saw Harbour Master projects being built by passionate developers in a non-slop way, and assumed that meant that none of the devs had talked to ChatGPT about a tough problem or used GitHub Copilot during the free trial time period or experimented with agentic coding harnesses as they became available. The quality of the experience didn’t feel like slop.”

The team emphasized a critical distinction: Harbour Masters had never incorporated AI-generated code directly into their projects without human review. Instead, developers used AI as a brainstorming and problem-solving resource. When code was proposed—whether AI-assisted or manually written—the team subjected every submission to thorough human review before integration.

Addressing the Policy Gap

Harbour Masters pointed to a public AI policy that had been available for months, which they indicated would be expanded in the coming period. Team member Dana the Elf repeatedly clarified the team’s actual practice: “We don’t just use generated code – our contributors have used LLM conversations to work through a technical problem, or to iterate through something and put their ideas into code that is then verified by human eyes. Nothing is just out of the AI and into the codebase.”

On the question of AI-generated imagery, all team members firmly denied using image generation tools and committed to avoiding them going forward. The confusion appeared to stem partly from the rapid evolution of tools available to developers and the lack of granular tracking regarding which specific tools were used in each commit.

Why Harbour Masters Embraced AI Tools

Developer Jeod provided perhaps the most transparent explanation for the team’s willingness to incorporate AI into their workflow. The core issue was bandwidth. Ship of Harkinian began as a passion project but had evolved dramatically over a decade, expanding to encompass numerous ports of classic Nintendo titles. As the project scope grew, the development team faced churn—some developers moved on, others lost interest in maintaining specific ports, and several struggled to balance the project with demands of their personal lives. Jeod explained: “When Ship of Harkinian began, it was apparently a dream; now, with so many ports and a decade later, devs have come and gone; some don’t have interest in specific games, others have real life to deal with. We always welcome talent, and if you’re willing to learn how things work here, then the door is open.”

Timing and Uncertainty

The controversy arrived at an awkward moment for Harbour Masters. The team released Paper Mario, their newest reverse-engineered port, on Thursday. While unclear whether this particular port utilized AI-assisted development, the timing of the release so close to the viral post cast a shadow of uncertainty over the project’s origins.

The broader question facing the retro gaming community remains unresolved: where does legitimate use of AI development tools end and corner-cutting begin? Harbour Masters maintains that rigorous human review ensures quality across their ports. The community’s acceptance of that standard will likely determine whether trust in future projects can be restored.