Nineteen Jurors, Zero Exemptions
The 2027 Independent Games Festival now has a rule that nobody wrote into the rulebook. Nineteen jurors signed a public statement declaring they will not vote for any game that uses generative AI in any capacity, and they were careful to close the one loophole everyone in this industry has been hiding in for two years: the code.
The signatories are not a random sample of the internet. Austin Walker, Sam Barlow, Lena Raine, Brendon Chung and fourteen others put their names on a document that IGF leadership approved for release, while noting that other jurors stayed off it partly out of concern about "professional blowback". Which is a very 2026 reason to leave a signature off a letter about AI.
The clause that made developers sit up straight is the third one. "Programming is a creative discipline whose labour deserves the same respect we extend to any part of making a game." Translation for the people in the back: "it was only autocomplete" does not get you out of this one. For a while, the industry's quiet compromise was that AI in code was pragmatic while AI in art was a scandal. The jurors took that compromise outside and set it on fire.
Enter the Goose People
Within hours of the statement, one game kept surfacing in what the jurors described as "fairly intense discussion and disagreement" across the judge and jury pools. That game was Big Walk, from House House, the Melbourne studio behind Untitled Goose Game, and it was very much in the running for the awards conversation.
House House confirmed the reason by email to Aftermath. LLMs were used, "sparingly", in the final stretch of development, "to help work through difficult technical challenges and bugs". Their own estimate of the footprint is blunt: "well under 0.1% of Big Walk's code had anything to do with this usage".
The actual bug is almost aggressively mundane. Unity's Universal Render Pipeline only culls shadow casters by camera-forward distance, so anything behind the player was being rendered as if it sat at infinity. That made the game run 50 percent slower for roughly twenty seconds at sunrise and sunset in the game's world. The team read the URP source, then asked Unity directly. An engineer there asked around and came back with the verdict: what they wanted was not possible.
Then they asked a chatbot. After a few dead ends, it proposed a fix. They had to modify the suggestion extensively. It worked. Total contribution to the shipped game: about ten lines of code inside URP.
Ten Lines, One Existential Crisis
So the flashpoint of this awards cycle is ten lines of shadow-culling math. Ten. Fewer lines than there are jurors who signed the letter, and roughly the length of a mildly controversial pull request. The internet handled the news with its customary grace, which is to say several thousand posts appeared within the hour.
House House's statement is more thoughtful than the argument around it. The studio says plainly that this is "not an endorsement of, or argument for, the use of AI tools". It worries out loud that voluntary disclosures like theirs "might contribute to the normalisation of this technology, or its treatment as inevitable", and then apologises that Big Walk's LLM usage "may not meet their standards". A studio apologising for ten lines while shipping a game people are nominating for awards is a strange thing to witness.
They also explained the silence. Steam does not ask studios to disclose code or chatbot usage, so there was no box to tick at submission. The real admission is quieter and more useful: Big Walk shipped with no internal AI usage policy at all, and the studio calls that absence, flatly, "a failure".
That is probably the takeaway worth keeping. The interesting question was never whether ten lines make a game AI-generated, because they plainly do not. It is whether a studio has a policy in place before the ten lines happen, or only after somebody with a Bluesky account finds out. House House has one now. It cost them a disclosure longer than the patch itself.
Comments