Ocarina of Time PC Port Team Admits Using AI for Years — Fans Are Furious

Name: Ocarina of Time PC Port Team Admits Using AI for Years — Fans Are Furious
Uploaded: 2026-09-18T04:45:48+00:00
Duration: 16 min 3 s
Channel: jamesschierer

00:00There are certain fan projects that become so well-known that they almost feel like official

00:04releases, and when it comes to Nintendo 64 PC ports, Harbor Masters has built exactly

00:10that kind of reputation.

00:11Their Ship of Harkinian project transformed The Legend of Zelda Ocarina of Time into a

00:16native PC experience, while the team has gone on to work on ports of other Nintendo 64 games.

00:23These projects have attracted a lot of attention because they can offer things that weren't

00:27possible on the original Nintendo 64 hardware, including higher resolutions, widescreen

00:32support, higher frame rates, modern controls, and additional quality-of-life features.

00:38But this week, the conversation surrounding Harbor Masters changed dramatically.

00:43The team behind these popular projects has acknowledged that some of its developers have

00:48used AI-assisted tools while working on its code, and while Harbor Masters strongly rejects

00:53the idea that its projects are simply AI-slop or vibe-coded, that omission has caused a major

00:59argument among retro-gaming fans.

01:01So what exactly happened?

01:03What did Harbor Masters actually admit to?

01:06What are fans upset about?

01:08And does using AI-assisted coding automatically mean that these projects are AI-slop?

01:13Let's break it all down.

01:15The controversy exploded on September 16th after a post on PC Gaming Wiki began circulating across

01:22social media.

01:23The post alleged that Harbor Masters had been using AI-generated code and even AI-generated

01:29assets across multiple projects.

01:31The post specifically pointed towards the team's Li-Boltra-Ship one-time component and claimed

01:37that large amounts of code have been generated or modified with AI assistance.

01:41One of the pieces of evidence that attracted attention was a GitHub comment that directly

01:46referenced Claude through a co-author credit.

01:49That doesn't automatically tell us how much of the code was generated by AI, how the AI

01:55was used, or whether the final implementation was written or substantially modified by a human,

02:00but it certainly gave people something concrete to point towards.

02:04From there, the discussion spread to ResetEra, BlueSky, Discord, and other gaming communities.

02:09And very quickly, this stopped being a technical discussion about development practices and

02:14became an argument about what AI-assisted software development actually means.

02:19Harbor Masters pushed back against the viral accusations.

02:23Members of the team described some of the claims as highly inaccurate and disputed the

02:27idea that their projects were being produced through some kind of automated generate-everything-and-ship-it

02:33process.

02:34And this is where the story gets more complicated.

02:36Because while Harbor Masters rejected the characterization of its projects as AI-slop, team members did confirm

02:43that AI tools have been used in their development process.

02:46According to the developers, AI can be used to help work through technical problems, experiment

02:51with solutions, convert code, or assist with development.

02:55But the team's position is that code still goes through human review before becoming part of the project.

03:01That's an important distinction.

03:03The developers aren't saying that an AI model is independently creating a Harbor Masters port

03:08and then uploading the finished product.

03:10They're saying that developers may use AI as one of the tools available to them, while

03:15experienced humans remain responsible for reviewing the resulting code.

03:19One of the more dramatic claims circulating online involved huge amounts of code allegedly being

03:25produced through AI.

03:27But Harbor Masters developer Malkyrian offered a different explanation for at least part of that

03:32situation.

03:33According to the explanation provided in the team's Discord, a large number of functions

03:38have been converted using a script developed with assistance from AI, with the resulting

03:43code then tested for parity.

03:45That is very different from saying that millions of lines of code were simply generated by an AI

03:51chatbot and dropped into the project without review.

03:54And that's really the central issue here.

03:56When someone says a project uses AI, that phrase can describe a huge range of activities.

04:02It could mean asking ChatGBT how a programming problem works.

04:06It could mean using GitHub Copilot for autocomplete.

04:09It could mean asking an AI model to suggest a function.

04:13It could mean using an AI-assisted script to convert or restructure existing code.

04:18Or it could mean generating huge amounts of code and barely checking it.

04:21Those aren't necessarily the same thing.

04:25Here's where things got particularly uncomfortable for some fans.

04:28Harbor Master's developers indicated that AI-assisted tools weren't necessarily something that had

04:34just been introduced this month.

04:36Some developers said they had experimented with tools such as ChatGPT, GitHub, Copilot,

04:42or other AI-assisted development systems over the years.

04:45One developer even acknowledged that they couldn't definitively identify a version of Ship of

04:51Harkinian that was completely free of AI-assisted code.

04:54That's probably one of the biggest reasons this story exploded.

04:58For some people, the issue was simply that AI had been used.

05:02It was what they believed these projects represented, a particular kind of human-made passion project,

05:08and discovering that AI tools had been part of the development process changed how they viewed the work.

05:13The developers have said they do not use or condone AI-generated imagery for their projects.

05:18So, while AI-assisted programming is part of the controversy, the team has pushed back against

05:24the idea that game assets are being generated by AI.

05:28That's important because AI-generated code and AI-generated artwork are often lumped together

05:34in online discussions, even though they raise different questions.

05:37The team has essentially drawn a line between using AI as a programming tool and using generative

05:43AI to create artistic assets.

05:45Whether individual fans agree with that distinction is another matter.

05:49This is where the comments become especially interesting because there isn't one universal

05:54reaction.

05:54Some people are furious, others don't really care, and some people are somewhere in the

05:59middle.

06:00One of the strongest arguments from the angry side is that the method matters even if the

06:04final product works.

06:06In other words, the argument isn't necessarily that an AI-assisted port is automatically broken.

06:11It's that some players value the human, creative, and technical process behind fan projects.

06:16For these fans, the appeal of projects like Ship of Harkinion isn't simply, I can now play

06:22Zelda on my computer.

06:23It's also the idea that passionate developers spent years understanding an old game, reverse

06:28engineering it, rebuilding systems, fixing problems, and adding new capabilities.

06:33If AI becomes part of that process, some fans feel that changes the character of the project.

06:40Other commenters have taken a very different position.

06:43One argument is essentially if the port works, performs well, and provides the features players

06:47want, why should the average player care whether an AI assistant helped write some of the code?

06:53That argument compares AI coding assistants to other programming tools.

06:57Developers have used compilers, debuggers, autocomplete systems, code libraries, stack overflow, documentation,

07:05and countless other resources for years.

07:08So from this perspective, an AI assistant is simply another tool.

07:12The more important question, according to this argument, is whether the humans working on the project

07:17understand the code and whether the final product is properly tested.

07:21And that's basically the position Harbor Masters itself is presenting.

07:25But one of the comments in this discussion raised a much larger concern.

07:29What happens if developers become so dependent on AI that they eventually lose the ability

07:34to solve programming problems themselves?

07:37That's not really a Harbor Master specific question.

07:40It's a broader question about the future of software development.

07:43If an experienced programmer uses AI to speed up repetitive work, but still understands what

07:48the code is doing, that's one scenario.

07:51If someone can't diagnose a problem without asking an AI model for the answer, that's a very

07:56different scenario.

07:57And this is one of the reasons the phrase vibe coding has become such a loaded term.

08:02The criticism is that someone might generate code without really understanding it, test it

08:07only superficially, and then move on.

08:09Harbor Masters is explicitly saying that isn't how its projects are being handled.

08:15There's also a practical reason the developers gave for being open to AI-assisted contributions.

08:20Harbor Masters is not some massive publisher with hundreds or thousands of programmers.

08:25It's a relatively small group working across multiple projects.

08:29And the scope of what they're taken on has grown considerably.

08:33What started as a project surrounding Ocarina of Time eventually expanded into a larger ecosystem

08:38of ports, tools, and related projects.

08:42One developer explained that contributors are spread thin, some developers have moved on,

08:47and others have real-life responsibilities.

08:49So from Harbor Masters' perspective, refusing every contribution simply because AI was involved

08:55could mean turning away potentially useful work.

08:58The team's argument is essentially that the important question isn't did an AI tool touch

09:02this code.

09:03The important question is, was the resulting code reviewed, understood, tested, and accepted

09:09by the humans responsible for the project?

09:12And the timing of this controversy couldn't have been stranger, because on September 17th,

09:17Harbor Masters released Paper Boat, its unofficial PC port of the original Nintendo 64 Paper Mario.

09:24The release means that this isn't just an argument about an old project.

09:28People are now immediately looking at a brand new Harbor Masters release while this controversy

09:33is happening.

09:33The official repository says Paper Boat supports Windows, Linux, and Mac OS, and requires users

09:40to provide their own supported copy of the game, rather than distributing Nintendo's copyrighted

09:45game data.

09:47So you've got a fascinating situation where a highly anticipated fan port arrives on the

09:52exact same day that people are debating the development practices of the team behind it.

09:57And understandably, that has made the conversation even louder.

10:00Now there's an important caveat here.

10:02The material we're discussing does not establish that Paper Boat itself was generated primarily

10:08through AI.

10:09The controversy concerns Harbor Masters' broader development practices and acknowledged use

10:14of AI-assisted tools.

10:16That's an important distinction to make because online discussions can very quickly turn the

10:21team uses AI into this entire game is made by AI.

10:25Those are two very different claims.

10:27At the time of this video, the most responsible thing to say is that Harbor Masters has acknowledged

10:32AI-assisted development within its broader workflow, while the specific extent of AI assistance

10:38in Paper Boat isn't established by the information we're discussing here.

10:41So now we get to the phrase that has been thrown around constantly, AI-slop.

10:47Does Harbor Masters' admission automatically make Ship of Harkinian AI-slop?

10:51The answer depends on what you mean by the term.

10:53If by AI-slop you mean any project where an AI tool was involved somewhere in the development

10:59process, then the term would encompass an enormous amount of modern software.

11:03But if you're using AI-slop to describe a project that is largely generated by AI with

11:08minimal human understanding, review, or quality control, that's a much more specific claim.

11:15Harbor Masters says its development process falls into the second category of human oversight

11:20rather than the latter.

11:22Whether you personally believe that process is sufficient is ultimately a separate question.

11:27And honestly, I think transparency is one of the most interesting parts of this entire

11:31story, because some people didn't find out about Harbor Masters' AI practices until the

11:36controversy erupted.

11:38The team points out that it has had a publicly available AI policy for months, so technically

11:44the information wasn't necessarily hidden.

11:46But there's still a difference between having an AI policy buried in a GitHub repository and

11:52clearly communicating to the broader community how AI-assisted development is being used.

11:57And that's where the disagreement gets interesting.

11:59A developer might think, we have a policy, it's public, we review everything.

12:05A fan might think, I never knew AI assistance was being used in these projects, and that changes

12:10how I feel about them.

12:11Both of those perspectives help explain why the controversy has become so heated.

12:17Looking through the comments, you can basically see the entire AI debate playing out in miniature.

12:22One commenter argued that AI-assisted coding is fundamentally different from the kind of AI-generated

12:28creative content people commonly describe as slop.

12:31Another commenter pushed back and argued that AI usage matters even if the final software works

12:36perfectly.

12:37Then another person brought up the environmental impact of AI data centers and the concern that

12:42people may lose something important when creative processes are increasingly automated.

12:47And finally, there were commenters who simply didn't think the issue was worth getting worked up over.

12:52And honestly, that's probably why this debate isn't going away anytime soon.

12:56Because underneath the Harbormaster's controversy is a much bigger argument about what people

13:01actually value in fan-made projects.

13:04If you're someone who has enjoyed Harbormaster's projects, nothing about this controversy suddenly

13:09changes the facts that these projects exist, that people have spent years working on them,

13:14or that they offer features that weren't available in the original Nintendo 64 versions.

13:18At the same time, if you care strongly about how software is created, you're perfectly capable

13:23of deciding that the use of AI-assisted development changes whether you want to support or use a particular

13:29project.

13:30And I think that's a more productive way of looking at this than simply shouting AI slop

13:35at one another.

13:36The facts are that Harbormaster's has acknowledged AI-assisted development.

13:40The team says humans review the code.

13:43The team says it doesn't use or could own AI-generated artwork.

13:47And there are online claims about the scale and nature of AI usage that go beyond what the

13:52developers themselves have acknowledged.

13:54So rather than treating every accusation as proven or dismissing every concern as meaningless,

13:59it's worth separating what has actually been acknowledged from what is still being argued

14:03about.

14:04For years, projects like Ship of Harkinian have represented one of the most fascinating sides

14:09of retro gaming.

14:11Developers taking games that were designed for hardware from decades ago and figuring out

14:15how to make them work in ways that their original creators never could have imagined.

14:20Now we're seeing the reality that the tools used to create those projects are changing

14:24too.

14:24AI-assisted programming is becoming another tool developers can use and Harbormaster's

14:29has made it clear that some of its developers have been using these tools for years.

14:34Whether you see that as a useful evolution of software development, a threat to traditional

14:39programming, a transparency problem, or some combination of all three probably depends on

14:44what you value most about fan-made projects.

14:47And that's what makes this story so interesting.

14:49It's not really just about Ocarina of Time.

14:52It's about what we expect from the people keeping our favorite older games alive and

14:56how much the process behind the finished product matters to us.

15:00But what do you think about Harbormaster's acknowledging its use of AI-assisted coding?

15:04Does human review make AI-assisted code acceptable to you?

15:08Or does the use of AI itself change how you view these fan projects?

15:13Let me know in the comments below.

15:15And if you enjoyed this video, make sure to give it a thumbs up, subscribe to the channel,

15:20and ring that notification bell so you don't miss any of my upcoming videos.

15:24And if you'd like to support the channel directly and get access to my Patreon-exclusive content,

15:29check out my Patreon.

15:31The latest Patreon-exclusive video is how September became one of gaming's biggest months.

15:35Your support helps me continue making these videos,

15:39and I really appreciate everyone who chooses to support the channel.

15:42Thanks for watching, and I'll see you in the next video.

15:46Game on!

Ocarina of Time PC Port Team Admits Using AI for Years — Fans Are Furious

Category

Transcript

Comments

Recommended