IGF Jurors Reject AI-Assisted Games, Sparking Controversy Over Big Walk's Minimal LLM Use

A group of Independent Games Festival jurors has pledged to boycott games using generative AI, triggering a public debate after developer House House disclosed that it used large language models to fix a specific bug in its game Big Walk. While the studio claims the AI involvement represents less than 0.1% of the code, the disclosure has intensified industry arguments over whether any AI use should disqualify indie titles from major awards.
Key points
- Nineteen IGF jurors signed a statement refusing to vote for any game using generative AI in any capacity, urging the festival to adopt a strict anti-AI policy for future years.
- House House disclosed that it used LLMs to resolve a Unity engine bug involving infinite-length shadows, which caused performance issues during sunrise and sunset sequences in Big Walk.
- The studio estimates the AI-assisted fix accounts for well under 0.1% of the game's code, noting that the suggested solution required extensive human modification to function correctly.
- House House apologized for the lack of an internal AI policy, stating that voluntary disclosure might normalize the technology, and confirmed it had not disclosed the usage on Steam because the platform does not require it.
- The controversy has divided the industry, with some jurors expressing deep disappointment over the loss of a beloved title, while others argue that punishing minimal technical fixes is disproportionate compared to heavy AI reliance.
Background
This dispute follows a broader trend in the gaming industry regarding AI transparency. Last year, the Indie Game Awards rescinded honors for Clair Obscur: Expedition 33 after developers admitted to using AI-generated textures, which were later patched out. The current debate highlights the tension between strict ethical stances against AI and the practical realities of modern development tools.
How outlets are covering it
Ars Technica and Gizmodo emphasize the emotional impact on jurors who had praised Big Walk, highlighting the conflict between personal appreciation for the game and their professional stance against AI. Aftermath focuses on the technical specifics of the bug and the studio's admission that the lack of an internal policy was a failure. GamesIndustry.biz provides a neutral overview of the disclosure timeline, noting that submissions for the 2027 IGF closed in September. While all sources agree on the facts of the disclosure, they differ in tone: Ars and Gizmodo present a balanced view of the 'all-or-nothing' debate, whereas Aftermath leans into the studio's apology and future policy changes. Some industry voices, like developer Brendan Keogh, argue that zero tolerance is counterproductive, while others, like jurist Damon Reece, view the boycott as a necessary cultural correction.
Why it matters
The incident tests the boundaries of AI ethics in creative industries. If minimal technical fixes are deemed disqualifying, it could force studios to adopt rigid policies that may hinder efficiency. Conversely, if such usage is accepted, it may normalize AI integration in core development processes, raising concerns about labor displacement and creative integrity in the indie sector.
What to watch
House House plans to implement a comprehensive AI usage policy for future projects. The IGF is expected to decide whether to adopt a blanket ban on AI-generated work for future award cycles. The final IGF award winners will be announced in January 2027, where the impact of the juror boycott on the outcome will become clear.
- Big Walk used AI to fix a bug. Now the indie gaming world is having a reckoning. Ars Technica
- Big Walk Used AI In 'The Final Stretch' Of Development, Kicking Off Intense Awards Debate Aftermath
- Indie Game Awards AI Boycott Sparks Big Walk Controversy Gizmodo
- House House clarifies use of AI tools in Big Walk's "final stage of development" GamesIndustry.biz
- Big Walk's AI controversy is a last-minute GOTY season twist sparking a bigger debate Polygon.com
Want the full story? Read the original reporting
Read on Ars Technica