Some might embrace AI, but not everyone.
The Godot Foundation moving to ban AI-authored code from its game engine cuts straight to the flaw in every "AI removes friction" pitch we keep hearing from publishers, which is that the friction doesn't vanish, it just gets shoved onto whoever has to check the output. While companies like EA and Sony sell AI as a tool that frees creators from tedium, Godot, one of the most widely used open-source engines around, powering games like Slay the Spire 2, is saying the quiet part out loud. AI made submitting code trivially easy, and in doing so it buried the small team of volunteer humans who have to review that code under an avalanche they can't dig out from. As the Foundation put it, the effort to make a pull request has collapsed while "the amount of work to review PRs and the amount of people available to review has stayed the same." That's the whole problem in one sentence. The productivity gain is real, but it's not free, someone downstream inherits the bill.
The mechanics here are worth slowing down on, because they explain why this was inevitable. In a healthy open-source project, contributors submit code changes as pull requests, and a limited pool of experienced maintainers reviews each one before merging it into the codebase. That review is genuinely demanding work, and it was already a bottleneck before AI showed up. Then generative tools dropped the cost of producing a plausible-looking contribution to essentially zero, and the number of PRs exploded while the number of qualified reviewers stayed exactly the same. Godot maintainer Rémi Verschelde first flagged the strain back in February, calling the flood of AI slop "increasingly draining and demoralizing," and months of that pressure led straight to this policy. The Foundation was blunt about why it can't just wave the code through either, stating flatly that "AI cannot take responsibility, and we can't trust heavy users of AI to understand their code enough to fix it." When a contributor can't explain or repair their own submission because a machine wrote it, the reviewer isn't collaborating, they're doing unpaid QA on a black box.
The Part That Should Worry the Whole Industry
What makes Godot's statement land harder than a simple quality complaint is the emotional core it names, which goes to the heart of how open source actually survives. Reviewing code was never just about catching bugs, it was about mentorship, since every round of feedback on a newcomer's PR was an investment in turning that person into a future maintainer. The Foundation spelled this out precisely, noting that review is "rewarding because reviewers generally feel that their efforts are contributing to educating a new contributor who may become a future maintainer," and that "if your feedback on PRs is just being absorbed by a machine and not going towards mentoring a potential future maintainer, it becomes much harder to justify spending your free time on PR review." That's the real damage. LLMs can't learn from specific feedback the way a human junior developer does, so pouring review effort into AI submissions severs the very pipeline that produces the next generation of maintainers. For a volunteer-driven project, that mentorship cycle isn't a nice-to-have, it's the entire mechanism that keeps the thing alive, and AI contributions quietly starve it.
A Counter-Current Worth Watching
For starters Godot isn't banning AI outright, since it still permits assistance for "menial things like code completion, regex, or find and replace" as long as contributors disclose it, but it prohibits AI-generated substantial code, autonomous agents, vibe coding, and even AI-generated text in human-to-human communication, which it frames as "a basic principle of respect." There's also a smart structural fix bolted on, requiring new contributors with three or fewer merged PRs to get explicit permission before proposing major features, funnelling newcomers toward bug fixes and documentation first to rebuild trust incrementally. What makes this genuinely notable is the direction it points, running directly against the corporate current. As publishers race to embrace AI and executives insist it empowers their people, the practitioners actually maintaining critical infrastructure are reaching the opposite conclusion, and Godot isn't alone, with emulator projects and other open-source teams drawing similar lines against AI slop in recent months. It fits a broader mood, too, since surveys show developers increasingly fear generative AI will lower the quality of games rather than raise it. The split is becoming impossible to miss. On one side, boardrooms selling AI as frictionless progress, and on the other, the people doing the work saying the friction never left, it just landed on them, and it's grinding down the human systems that made these projects worth contributing to in the first place.
More:Krafton Caves and Pays the $250M Bonus It Fought for a Year
Read
Source Editing
Visual Editing
Related news
