Big Walk's 10-Line AI Fix Sparks IGF Jury Revolt and Steam Review Bombing

TL;DR

Big Walk, the co-op puzzle hit from House House, took more than 400 negative Steam reviews in the days after it disclosed that chatbots touched a slice of its code. The studio's FAQ entry, posted Nov 10, says LLMs were used "sparingly" in the final stretch of development and estimates that "well under 0.1%" of the game's code had anything to do with them. The shipped artifact is about 10 lines inside Unity's render pipeline. One day earlier, 19 of the 50-plus jurors of the Independent Games Festival signed a statement refusing to vote for any game that used generative AI in any capacity. Big Walk, from the studio behind Untitled Goose Game, became the test case.

What ten lines of code did

The bug was real and expensive. Unity's Universal Render Pipeline culls shadow casters by distance only in the direction the camera faces, so shadows behind the player were being drawn at what the studio describes as an infinite distance. At sunrise and sunset, for roughly 20 seconds, the game ran 50% slower.

House House says it researched the problem and read the URP source itself. Then it put the question to an engineer at Unity, who asked around and concluded that what the studio wanted was not possible. The team then asked a chatbot, which after a few dead ends suggested a fix; the studio "had to modify the suggestion extensively," and about 10 lines inside URP made it into the shipped game. Generative AI was used nowhere else: no AI art, audio or writing.

Timing explains the shape of the disclosure. The FAQ was first written for the studio's IGF submission, because the festival's form asks about AI use. Steam got no disclosure because Steam asks for none. "We are posting this disclosure," the FAQ reads, "as it has become a matter of public interest."

Nineteen jurors refuse the whole toolbox

The jurors moved first. On Monday, Nov 9, 19 members of a jury the festival lists at more than 50 people published a signed statement: they are "declining to vote for any game that uses generative AI in any capacity." It cites what the signers describe as ecological, economic, psychological and labor harms, notes a "significant increase" in AI-made submissions, and asks the IGF to bar games containing any AI-generated work in future years.

Code got its own paragraph. Generated code is "not an exception," the signers wrote, because "Programming is a creative discipline whose labour deserves the same respect we extend to any part of making a game. This extends to the past work used to train these models without the creators' consent."

The fight had been running in private jury discussions for months, and Big Walk is what pushed it into the open. Several jurors who admired the game held the line anyway. Austin Walker called it "an achievement," "remarkable" and "beautiful." Damon Reece wrote that the game gave him "a profound and powerful emotional reaction," and still: "This is pain that has to happen to try and steer our culture away from this."

Others disagreed with the all-or-nothing reading. Juror Liz Ryerson said she did not find House House's use disqualifying, and that treating every degree of AI use as identical bothers her. Game developer and academic Brendan Keogh called zero tolerance "ultimately counterproductive now," because the anger lands on developers conflicted enough to disclose "their glorified Google search" while pushing studios that quietly replace labor with AI further underground.

Two rulebooks for the same question

The disclosure arrived months after launch because the two institutions that matter most to an indie studio ask different questions. Valve's AI disclosure form, clarified in January, covers AI-generated content that players consume: generated art, voices and text. "Efficiency gains" from development tools are explicitly out of scope. The IGF asks about AI use in development with no such carve-out, and its jurors just told the world how they weigh each answer.

Valve's form asks what is in the food. The IGF jurors asked what happened in the kitchen, and ten lines of grease were enough.

The pile-on, and the studio's answer

The public reaction ran hotter than the jury debate. Big Walk's Steam page picked up more than 400 negative reviews in the days after the FAQ went up. Steam's anti-review-bomb tooling appears to be limiting the impact on the aggregate, which still reads Very Positive.

Precedent exists for harsher outcomes. Last year the Indie Game Awards, a separate event from the IGF, rescinded the prizes it had handed Clair Obscur: Expedition 33 after the studio admitted some placeholder textures were AI-generated and later patched them out. An award can be clawed back. A review bomb eventually scrolls off the front page.

House House's FAQ is a strange document: a disclosure, an apology and a policy commitment on one page. The studio calls the absence of an internal AI usage policy "a failure" and promises a comprehensive one going forwards. It worries that voluntary disclosure "might contribute to the normalisation of this technology, or its treatment as 'inevitable,'" and closes by supporting "the work of those who are trying to limit the harm generative AI is doing to videogames and our world."

Why this matters if you ship anything

You are probably not submitting to the IGF. The mechanism still applies. Every venue you sell through, submit to or pitch has its own line on AI, and the lines disagree. A studio that never writes its own rule is letting whichever venue asks first decide the question, on the worst possible day.

The reusable part of House House's post-mortem is one sentence: develop under a written AI policy, or admit you flew without one. If your audience includes communities hostile to generative AI, and indie games are the loudest of those right now, a "we used it here and not there" line written before launch reads as discipline. The same line written after a backlash reads as damage control, and the tuition this month is 400 reviews.

Key Takeaways

• House House disclosed that LLMs touched "well under 0.1%" of Big Walk's code, all in the final stretch of development, and that generative AI was used in no other context.
• The concrete fix was about 10 lines inside Unity's URP, solving a shadow-culling bug that made the game 50% slower for roughly 20 seconds at sunrise and sunset, after a Unity engineer had said it could not be done.
• 19 of the 50-plus IGF jurors signed a statement refusing to vote for any game that uses generative AI in any capacity, code included, and asked the IGF to bar AI-generated work in future years.
• Disclosure rules diverge by venue: Valve's Steam form covers AI-generated content players see and ignores coding tools; the IGF asks about development use, which is why the FAQ existed at all.
• Big Walk took 400+ negative Steam reviews, with anti-bomb tooling limiting the damage to its Very Positive rating. Clair Obscur: Expedition 33 shows awards themselves can be rescinded over AI use.
• The reusable lesson: write your AI usage policy before you ship. House House calls its own lack of one "a failure."

Sources: Was AI used to make Big Walk?, House House FAQ (Nov 10, 2026), Ars Technica (Nov 11, 2026), PC Gamer (Nov 10, 2026), Aftermath (Nov 10, 2026), IGF jurors' signed statement (Nov 9, 2026)