Big Walk's AI Fight Is a Disclosure Lesson for Every Indie

Published .

The glowing gold Independent Games Festival atom emblem on the left casts a beam of light across a dark sunburst background toward the red, yellow and blue Big Walk logo on the right.
Image: House House and IGF.

The Big Walk fight is less about ten lines of code and more about who told players first. If you use AI anywhere in your game, even as a fancy search box, write your disclosure now. Otherwise an award jury, a store page or a stranger on social media writes it for you.

What happened

On November 9, a group of 19 jurors for the 2027 Independent Games Festival said they are “declining to vote for any game that uses generative AI in any capacity.” The statement makes no exception for code and calls programming “a creative discipline.” It also says the signers don’t speak for the IGF or for every juror, and that the IGF told jurors they may vote by their own tastes and values.

Within hours, Big Walk was named on social media as the game at the center of the jury debate. House House, the studio behind Untitled Goose Game, then added a new answer to the Big Walk FAQ. LLMs were used “sparingly” in the final stretch of development to work through hard bugs, and the studio estimates “well under 0.1%” of the game’s code had anything to do with it.

The one worked example is wonderfully specific. Unity’s URP could only cull shadow casters by distance in front of the camera, so shadows behind the player made the game run 50% slower for about 20 seconds at sunrise and sunset. The team researched it, read the URP code and asked an engineer at Unity, who concluded it wasn’t possible. A chatbot then suggested a fix that the team modified extensively. It came to about 10 lines inside URP.

The timing did the damage

House House says it wrote a version of that disclosure for its IGF submission. It made no disclosure on Steam because the platform “does not request disclosure of code or chatbot usage.” Both claims check out. Valve’s content survey says efficiency gains from AI powered tools are “not the focus” and asks about AI content “that ships with your game, and is consumed by players.”

So the studio followed each set of rules and still looked like it had hidden something. Jurors read the note in a submission form. Players read about it in headlines, months after the game launched on August 4.

The response was swift. On the day the news broke, Big Walk’s new Steam reviews were just 36% positive, with 156 negative, compared with one negative review the day before. VGC’s post about the disclosure passed 370,000 views on X.

Those ten lines of URP code have now produced several thousand times their own length in commentary. We are aware this post adds to the pile.

Both sides have a point

The jurors are judging one festival, and they want it to mean something specific. One signer said afterward that Big Walk was not the impetus but became “the tricky edge case,” and that the statement was “not a call to boycott a certain game.” A jury voting its values is a jury doing its job.

House House’s use also sits right on a line many developers have never thought about. Asking a chatbot why something breaks feels like searching a forum. Pasting its answer into your build is different, at least on itch.io. When a developer asked about debugging with ChatGPT, itch.io’s admin drew the line clearly. Asking a question “solely to inform yourself” doesn’t count, but code you “then inserted into your project” does.

By that test, snippets “copied as a starting point to be modified into game code” land on the disclose side. Small, honest and still on the list. The studio itself now calls building the game without an internal AI policy a failure.

Four places, four different questions

This is the gap most of the coverage skips. Each place you ship or enter asks something slightly different, and the answers don’t transfer.

Steam asks about AI content that ships with the game and is consumed by players, such as art, sound, narrative and localization. It splits that into pre-generated and live-generated content, and code helpers are not its focus.

itch.io asks whether your project contains the results of generative AI, with a separate AI Generated Code option next to graphics, sound and text. Answering is required for asset creators. Untagged AI assets, even if modified afterward, lose their place on browse pages.

Nexus Mods now makes authors of new uploads declare whether AI was used in their work. Mods tagged AI assisted need a public explanation of how and where, and existing mods have until January 2 to comply.

The IGF collects a disclosure with your entry. House House calls it a suggested part of the submission, while another developer posted that it was required. Either way, jurors read it, and this year some of them won’t vote for any AI use at all.

What we’d do this week

Keep a running AI log. Note the date, the tool, what you asked, and whether anything it produced went into the build. It takes a minute a day and saves a forensic dig later.

Sort every use into two buckets. Questions you asked to learn something go in one. Output that ended up in your project goes in the other. That second bucket is what most disclosure forms care about.

Write a short AI policy now. One paragraph is enough. Say which tools you use, for what, and what you won’t use them for. It also helps if a publisher or teammate asks.

Answer the strictest question you face. If you plan to enter the IGF or sell assets on itch.io, include code in your disclosure even though Steam doesn’t ask.

Publish one disclosure and reuse it. Put it in your FAQ or press kit before launch, then use the same words in store forms and festival entries. Matching answers matter more than long ones.

Read award rules before you enter. Jurors can vote by their own values. A disclosure won’t win back a vote, but it does stop the surprise.

Check what you buy. Look at the AI tags on asset packs before they go into your game, since their content becomes your content. Our guide on selling a game made with AI covers the rules by tool.

Update it when your process changes. A disclosure written at launch goes stale after a patch made with new tools. Revisit it with every major update.

QuickMatch Weekly

New and updated AI game tools, with sources, in one short email.

One email a week. New AI game tools, price changes, and deals. Unsubscribe anytime.