A game engine that thousands of studios rely on just banned AI-written code — because volunteers can't keep up with the flood

Gaming 4 min 80 sources

The open-source Godot engine will no longer accept AI-authored contributions. The problem wasn't the code — it was that generating it got cheap while checking it stayed expensive, and the checkers are unpaid.

Key takeaways

The Godot game engine banned AI-written code because generating it got nearly free while checking it stayed slow — and the checkers are unpaid volunteers drowning in 5,000 unreviewed submissions.
Valve's AI labels and Epic's objection to them are the same fight from another angle: when content is cheap to make, someone downstream has to decide what to trust.
Rockstar's GTA VI developers asked for union recognition right before launch — the moment a studio needs its workers most is the moment those workers can ask for the most.

The engine that said stop

On Tuesday, the team behind Godot — a free, open-source game engine used to build hits like Slay the Spire 2 and Buckshot Roulette — changed its rules to require that “all code be human-authored” [15]. Small AI helpers are still allowed for menial jobs like find-and-replace, but only with disclosure [30]. Whole chunks of bot-generated code, the practice people call “vibe coding,” are now banned outright [41].

An engine is the shared software games are built on top of — the part that handles physics, rendering, and input so each studio doesn’t rebuild it from scratch. Godot is unusual because it’s open-source and volunteer-run: anyone can submit an improvement, and unpaid maintainers review each one before it goes in. That openness is the whole point. This week it’s also the wound.

Why cheap code became an expensive problem

The trouble started months ago. Godot’s GitHub — the site where contributions are proposed and reviewed — was, in its own contributors’ words, a “shitshow” of AI-generated submissions [15]. Right now it holds over 5,000 unresolved pull requests waiting for review [15]. A pull request is just a proposed change; someone has to read it, understand it, and decide it’s safe before it ships.

Here is the mechanism that broke. Writing a plausible-looking chunk of code with an AI tool now takes seconds. Reviewing that code — checking it works, hides no bug, and its author actually understands it — takes the same careful hour it always did. When one side of that trade goes nearly free and the other doesn’t, the cheap side floods the expensive one. Godot’s maintainers said the AI submissions were not just extra work but “demoralizing” [15], and that they “can’t trust heavy users of AI to understand their code enough to fix it” when it later breaks [46].

The people paying that cost are volunteers. They can’t hire more reviewers, and they can’t refuse to look — every unreviewed request is a game studio waiting. So they changed the rule at the door instead.

A line the whole industry is drawing

Godot isn’t alone in trying to mark what a machine made. On Steam — the largest PC game storefront — Valve now asks developers to label games that used generative AI. Epic Games boss Tim Sweeney called those labels “really irresponsible of Valve” [32], arguing the line between AI-assisted and human-made is too blurry to police fairly. Both moves are the same fight underneath: when generating content gets cheap, someone downstream has to decide what to trust, and nobody agrees on who should carry that job. Godot answered by banning the flood; Valve answered by labelling it; neither has solved it.

Workers reaching for leverage before the launch

A different labour story is moving in the UK. Developers at Rockstar Games — makers of Grand Theft Auto — asked this week for their employer to voluntarily recognise their union, the IWGB Game Workers Union, before GTA VI ships in November [13][14]. The timing is deliberate. GTA VI is expected to be one of the best-selling games ever; pre-orders reportedly generated around $3 billion when they opened [19]. A studio is never more dependent on its workers than in the months before its biggest release — which is exactly when those workers have the most power to ask for something.

The fight isn’t new. It erupted last autumn after Rockstar fired more than 30 staff in a move the union called “union busting” [19]. Workers credit the company with real improvements since — including “unprecedented average pay rises” and paid incentives for crunch [13]. But recognition would give them a formal channel to bargain, not just a hope that management stays generous. If it succeeds, Rockstar would become only the second UK games studio with a recognised union [19].

The quiet one

Underneath all of it, the industry’s contraction keeps grinding. Striking developers at Quantic Dream say their game Star Wars Eclipse “literally cannot be finished” without more staff, even as the studio plans layoffs [68]. It is the same shape as the AI-review flood and the union push: work that depends on people, run by systems that keep looking for ways to need fewer of them.

02 · Lesson · why it matters

When making a thing gets cheap, the cost moves to whoever has to trust it

The bill for easy creation doesn't disappear — it lands on the person who has to check the result, and they usually never agreed to receive it.

The thing that got cheap wasn’t free

A group of volunteers builds a piece of software that a lot of games are made with. Anyone can offer an improvement; a few unpaid people read each offer and decide whether it’s safe to include. For years that worked. Then a tool arrived that lets anyone produce a convincing-looking improvement in seconds, and the offers arrived faster than the volunteers could ever read them. This week they gave up trying to keep up and shut the door: no more machine-written code.

It’s tempting to read this as a story about a machine doing bad work. But the machine’s work isn’t the problem. The problem is arithmetic. One task got about a thousand times faster. The task sitting right next to it — checking whether the fast task was done right — got no faster at all.

Two jobs that used to move together

Making something and trusting something used to travel at roughly the same speed, so nobody thought of them as separate. When writing a solution took an afternoon, reading someone else’s solution also took an afternoon, and the two roughly balanced. A person who could produce a lot could also, more or less, be checked.

That balance was invisible until it broke. The moment producing got cheap and checking stayed expensive, the two jobs came apart — and you could suddenly see that they were always two different jobs done by, often, two different people. The maker gets the speed. The checker gets the flood.

This is why the volunteers used a strange word. They didn’t say the submissions were wrong. They said reviewing them was “demoralizing.” That’s not the language of a technical problem. It’s the language of someone handed an infinite pile of things to verify, who knows most of it isn’t worth the hour, and who can’t tell which part is until they’ve spent the hour.

The checker never signed up for this

Here’s the part that’s easy to miss. The person producing the cheap thing chose to. The person who has to check it didn’t choose anything. They were just standing where the output lands.

That’s the quiet injustice in the whole shape. A benefit is captured by the one who acts; a cost is paid by the one who happens to be downstream. The maker feels productive. The checker feels buried. And because the checker’s pain is slower and quieter than the maker’s speed is visible, the system keeps rewarding the thing that creates the pile and ignoring the thing that has to sort it.

You can see the same shape without any software in it. A colleague forwards you forty articles “to look at.” A relative sends a stream of forwarded claims to “verify.” Someone drafts a contract in an afternoon that takes a week to read carefully. In each case one side did the cheap thing and the expensive thing was quietly reassigned to you.

Why they closed the door instead of fixing it

The volunteers couldn’t hire more checkers — there’s no budget; it’s volunteer work. They couldn’t just stop reading, because every unread offer is a real studio waiting on a fix. Both exits were blocked. So they did the only thing left: they moved the rule to the entrance. Not “we’ll review this better” but “we won’t accept this at all.”

That’s what a rule at the door usually is — not a judgment that the thing is worthless, but a signal that the people meant to absorb it have run out of room. When you see a blanket ban, it’s worth asking who was drowning before you decide it was unreasonable. The same week, a storefront tried a softer version — asking makers to label what a machine helped build — and a rival executive called even that “irresponsible.” There’s no clean answer yet. There’s only a cost that has to land somewhere, and a fight over whose lap it lands in.

The seat you’re sitting in

It would be comfortable to side with the checkers and leave it there. But notice where you sit. Somewhere today you were the maker — you produced something quickly that someone else will have to trust, read, or clean up, and you didn’t think about the hour it would cost them because it didn’t cost you anything. And somewhere else you were the checker — buried under output someone generated cheaply and handed off without a thought.

The pattern doesn’t have a villain. It has a slope, and almost everyone is standing on it, tipping cost downhill in one place and catching it in another. The tools that make creation nearly free are genuinely useful — the same volunteers still allow them for small jobs. What’s hard isn’t the tool. It’s that no single seat can see the whole slope: the maker can’t feel the checker’s flood, and the checker can’t see how many quiet places the maker’s speed helped. Seeing that both are true at once — and that you are both — is the only view that keeps you from being smug about either.

03 · Lab · your turn

The Reviewer's Desk

Rehearse how cheap-to-make work floods the person who has to check it, and why closing the door can beat trying to keep up.

04 · Hope · carry this

The volunteers who drew that line did it to protect work they were never paid to protect — proof that the people who quietly keep the shared things running will still stand up for them, even when no one's watching and no one's paying.