Godot now requires human-authored code contributions, sharpening the debate over generative AI, maintainer workload, and trust in open source game engines.
Godot draws a firm line on contributed code
Godot has updated its contribution rules to require that code submitted to the open-source game engine be human-authored, a change meant to protect the maintainers reviewing the engine that many indie teams build on. The immediate consequence is for contributors, not players: anyone sending code to Godot’s repository now has to take responsibility for that work as human-written code, with only limited AI assistance allowed under disclosure.
What Godot is banning, and what it still allows
According to Kotaku, Godot revealed changes to its contribution policy this week after months of frustration around AI-generated pull requests. The new policy requires “all code to be human-authored,” while still allowing some AI help for menial tasks such as finding and replacing phrases or autocompleting code, provided that use is properly disclosed. Kotaku also reports that the policy reinforces Godot’s existing ban on vibe coding.
Why maintainers pushed back
The stated issue is not just code quality. Godot’s policy, as quoted by Kotaku, says AI contributions add a demoralizing burden because reviewing pull requests is volunteer work that usually doubles as mentoring a real contributor. If feedback is being absorbed by a machine rather than helping a potential future maintainer, the project argues, that time becomes harder to justify. Godot project manager Rémi Verschelde had already described AI-generated pull requests as draining for maintainers on Bluesky in February, according to Kotaku.
The bottleneck matters for small teams
For indie developers, an engine is not just a toolset. It is the floor under the whole game. Kotaku reports that Godot’s GitHub had more than 5,000 unresolved pull requests, and that developers noticed approvals taking significantly longer during the earlier wave of AI-generated submissions. If a project’s maintainers are spending more time sorting low-value submissions, fixes and improvements can slow down for everyone using the engine.
Human-authored communication is part of the policy
Godot’s stance also covers the words around the code. Kotaku reports that issue descriptions, pull request descriptions, and similar project communication must be written by humans. Godot’s policy frames that as respect for maintainers, stating that volunteers reviewing an issue, pull request, or proposal do not want to talk to a machine. That matters because open-source engine work depends on shared understanding, not just patches landing in a repository.
How this fits the open-source engine debate
The Godot AI code ban arrives as open-source engine trust is becoming a sharper industry question. In a separate report, Console Creatures wrote that Fenris Creations has made its Carbon Engine available through open-source releases covering more than two dozen modules, including physics, pathfinding, graphics, networking, UI, audio, scripting, scheduling, and tools for large online experiences. Fenris senior development director for core technology Ben Hunter described that move as a commitment to transparency, longevity, and making the technology visible, understandable, and useful to others.
Transparency is not the same as accepting everything
That is the tension indie developers should notice. Open source invites inspection, reuse, criticism, and contribution, but Godot’s new rules argue that a healthy contribution pipeline still needs authorship and accountability. The wider open source game engine AI debate is no longer only about whether generative tools can produce code. It is also about whether a project can trust the origin, intent, maintainability, and review burden of that code.
What indie developers should watch next
The most practical question is whether the Godot generative AI code policy reduces the review backlog and helps maintainers focus on meaningful contributions. Developers relying on Godot should also watch how consistently the rule is enforced, what counts as acceptable disclosed assistance, and whether other open-source engine projects adopt similar human-authored code requirements. Those are not confirmed outcomes yet, but they are the pressure points that will determine whether this becomes a one-project policy or a broader indie game engine AI policy.