• The Crisis: Godot maintainers are facing "draining and demoralizing" workloads due to a surge in AI-generated code submissions, or "AI slop."
  • Quality Control: Reviewers now have to second-guess every Pull Request (PR) from new contributors, checking for hallucinated code and fake test results.
  • High Stakes: Godot’s massive growth—driven by projects like Slay the Spire 2 and Battlefield 6—is being bottlenecked by low-quality LLM output.
  • The Roadmap: Lead developer Rémi Verschelde is weighing options including increased funding for more maintainers, community trust systems, or even leaving GitHub.

Godot’s Success Is Being Sabotaged by Machine Noise

Godot has spent the last decade earning its reputation as the scrappy, open-source champion for indies and AAA devs alike. But that hard-earned "welcoming" culture is under fire. Lead developer Rémi Verschelde warns that the engine's maintenance team is being buried under an avalanche of AI-generated PRs that are "increasingly draining and demoralizing."

We’ve seen Godot’s meta evolve rapidly following Unity’s recent missteps. With heavy hitters like Mega Crit moving Slay the Spire 2 to the engine and its tech powering Buckshot Roulette and even Battlefield 6's Portal map editor, the platform is more relevant than ever. However, that popularity is a double-edged sword. Every day, the team is forced to sift through "AI slop" from contributors who often don't understand the code they’re submitting.

The "AI Slop" Bottleneck

The core of the issue isn't just the code—it's the lack of transparency and the time-sink of the review process. Verschelde notes that the team is now forced to ask a series of exhausting questions for every new submission: Did the author test this? Are the test results made up? Is the code wrong because it was written by AI, or is it an honest mistake?

Adriaan de Jongh, developer of Hidden Folks, echoed these concerns, calling LLM-generated pull requests a "massive time waster," especially when users hide the fact that they used AI. Even though Godot’s guidelines require an AI-assisted declaration, Verschelde says these rules are "frequently ignored." This forces veteran maintainers to act as digital detectives instead of engine architects.

The Cost of Keeping Godot Open

We believe this is a critical junction for the engine. For years, Godot’s "low barrier to entry" has been its greatest strength, allowing anyone to contribute to the core code. Now, that openness is being weaponized by low-effort submissions. Verschelde admits he is "monitoring how the situation evolves," but the current pace is unsustainable.

The team is currently looking at three potential paths to keep the project afloat:

  • Increased Funding: Raising money to hire more dedicated maintainers specifically to filter the "slop."
  • GitHub Migration: Moving away from GitHub to a platform that doesn't "actively facilitate" AI-generated contributions, though this risks alienating genuine contributors.
  • Trust Systems: Implementing community voting or rating systems to gatekeep who can submit PRs.

Our take? Moving off GitHub feels like a "nuclear option" that could hurt the community more than the bots. However, the maintenance team can't be expected to tank this much damage forever. If the community wants Godot to remain a viable alternative to the corporate giants, it's time to stop the low-effort LLM spam and start respecting the human reviewers who keep the engine running.