The Godot Foundation has instituted strict new guidelines on generative AI use among contributors, banning "vibe coding" and requiring disclosure of any AI-assisted submissions. The move comes after maintainers grew overwhelmed by what they termed "low-effort slop" flooding code review queues.
Godot powers titles like Slay the Spire 2 and serves thousands of indie developers worldwide. The foundation still permits AI tools for narrow tasks like find-and-replace operations, but prohibits broad code generation where developers ask chatbots to write entire functions or systems without understanding the output. Contributors must now explicitly declare any genAI involvement in pull requests.
The crackdown reflects real strain on open source maintenance. Godot's core team volunteers time reviewing submissions. AI-generated code often lacks context about the engine's architecture, performance constraints, and design patterns. Reviewers spend hours dissecting mediocre patches that could've been written by hand in less time. The foundation called this approach "demoralizing" for staff already drowning in requests.
This policy positions Godot ahead of industry conversation on AI in game development. Most studios haven't formally addressed code generation standards. The Godot Foundation essentially says AI assists, but doesn't replace understanding. You can use it to accelerate repetitive work. You cannot use it to mask laziness or dump unvetted code on volunteers.
The stance matters because Godot competes directly with Unity and Unreal for developer mindshare. Maintaining code quality builds trust. If the engine's repository filled with untested AI slop, contributors bail. Quality erosion kills open source projects faster than anything else.
Godot's transparency requirement also sets precedent. As AI penetrates development workflows, knowing which code came from a human brain versus a language model becomes a baseline expectation. It's not about banning the