They posted a short, blunt pledge: jurors would refuse to vote for any game that used generative AI. I read it and felt the room tilt—this was not a technicality but a line in the sand. You can hear the ripple already: an award season suddenly policing the faintest trace of a chatbot.
I’ve watched juries and festivals for years; I know how reputation moves faster than rules. You should know two things right away: the Independent Games Festival (IGF) matters to indies, and a narrow rule applied broadly can crush momentum as fast as it creates clarity.
19 jurors publicly declared they won’t vote for any game that used generative AI
That number landed like a headline: a public statement shared on BlueSky and other platforms, signed by developers and critics including Austin Walker and Sam Barlow. You should also know IGF rotates jurors across categories—last year 46 people judged the awards, and this year sources estimate roughly 50. Nineteen signatures are influential, even if not a majority, and several other jurors reportedly back the stance privately for fear of professional fallout.
The pledge is absolute: “no game that uses generative AI in any capacity,” and it explicitly rules out AI-generated code. The language reads like a moral line drawn around the craft of programming: coding, the signers argue, is creative labor that deserves the same respect as design, writing, or audio.
What counts as using AI in game development?
Short answer: almost anything that touches creation, from art assets to snippets of code returned by Large Language Models (LLMs). House House disclosed that an LLM suggested a fix to a Unity shadow-culling problem; they modified it heavily, and estimate well under 0.1% of Big Walk’s code was connected to that chatbot exchange.
House House quietly reported using chatbots to fix a technical bug
The studio behind Untitled Goose Game told IGF—during submission—that an LLM helped them research an elusive Unity issue. You can picture a team stuck on culling shadows, an engineer exhausted, a quick chat with ChatGPT, and a suggestion that pointed them toward a solution they otherwise could not reach.
That admission collided with the jurors’ blanket rule. House House says the AI-produced code snippets were modified and tiny in scope; the studio also apologized for not having an internal AI policy. Their candor has become the test case: is a tiny, practical use the same as wholesale reliance on AI-generated assets? The jurors said yes, and you can see why that is bitter for studios trying to be honest about tooling.
The moment feels like a splinter under a fingernail—small, but impossible to ignore.
Can games using AI still be eligible for awards?
The jurors’ statement answers that for now: no. But reality is messier. IGF uses different juries per award—audio, narrative, student, visual art—so the effect depends on who sits where. Some jurors have stayed silent publicly but support the pledge privately, which raises the specter of uneven enforcement and surprise disqualifications.
Many developers fear professional blowback for signing or opposing the pledge
At least a handful of jurors said they wouldn’t sign publicly because of career risk. You should register how intimate the ecosystem is: an off-platform comment, a tweet, a post on BlueSky or a blog can tilt hiring, partnerships, and festival invites.
Big names—Sam Barlow and Austin Walker among them—framed the pledge as a defense of labor. Others argue that training data for models often includes scraped code and artwork created without consent, and that normalizing these tools accelerates harm. The controversy is as much about ethics as about awards politics.
How common is AI use in indie games?
It’s growing. Teams use ChatGPT and other LLMs for debugging, brainstorming, and sometimes quick scripting. Platforms like Steam currently don’t require developers to disclose chatbot use or AI-generated content, so public estimates are incomplete. That opacity is precisely what scares jurors who want to protect creative labor.
Big Walk’s disclosure forced the community to pick a side
House House disclosed their use to IGF during submission but hadn’t publicly detailed it until the pledge surfaced. You should see the conflict this creates: transparency punished, silence rewarded. The indie community prizes honesty, yet public admission became a liability.
House House accepted criticism and said their lack of an internal AI policy was “a failure.” They also expressed support for limiting harm caused by generative AI to videogames. That tone—contrite, cooperative—differs from studios that hide toolchains or aggressively lean on AI-generated assets.
The debate is about more than method; it’s about precedent. A tiny patch of AI-suggested code can be treated like a smoking gun, and suddenly compliance becomes a license to police craft.
Here’s what I’m watching next: whether IGF clarifies the rulebook, how juries distribute votes across categories, and whether platforms like Steam or engines like Unity adopt disclosure standards. I’ll be paying attention to public reactions from figures like Austin Walker and Sam Barlow, and to whether other festivals mimic IGF’s stance.
If you’re a developer, you’ll need to decide how transparent you want to be—and whether that honesty will cost you recognition or protect your ethics. If you’re a player or industry observer, you’ll have to decide which kind of creativity you want awards to celebrate.
Is a single chatbot prompt enough to disqualify a game, or have we let a small technical aid become a moral test that will reshape indie culture?
