---
title: "Big Walk Developer Confirms Minimal LLM Use Amid IGF Jury Debate"
url: "https://www.nintendoreporters.com/en/news/nintendo-switch-2/big-walk-developer-confirms-minimal-llm-use-amid-igf-jury-debate/"
description: "Big Walk AI usage confirmed by House House; learn how LLMs touched under 0.1% of code plus the IGF fallout now"
author: "Patrick Dankers"
published at: "2026-11-18 15:35:25"
image: "https://www.nintendoreporters.com/storage/files/big-walk-developer-confirms-minimal-llm-use-amid-igf-jury-debate.jpeg"
markdown url: "https://www.nintendoreporters.com/en/news/nintendo-switch-2/big-walk-developer-confirms-minimal-llm-use-amid-igf-jury-debate.md"
---

Big Walk Developer Confirms Minimal LLM Use Amid IGF Jury Debate | Nintendo Switch 2 News | NintendoReporters

 [![Big Walk Developer Confirms Minimal LLM Use Amid IGF Jury Debate](https://www.nintendoreporters.com/storage/files/big-walk-developer-confirms-minimal-llm-use-amid-igf-jury-debate.jpeg "Big Walk Developer Confirms Minimal LLM Use Amid IGF Jury Debate")](https://www.nintendoreporters.com/storage/files/big-walk-developer-confirms-minimal-llm-use-amid-igf-jury-debate.jpeg)**Summary:**

House House, the Australian studio behind Big Walk, has acknowledged limited use of large language models during the “final stretch” of the game’s development. The studio’s FAQ states that LLMs were used sparingly to investigate tough technical issues and bugs, and that well under 0.1 percent of the game’s code was related to that usage. The disclosure followed a public statement from 19 Independent Games Festival jurors who said they would decline to vote for any submission that used generative AI in any capacity, a move that turned the conversation about awards, ethics, and transparency into a heated topic among indie developers and players. House House explained the concrete example of a shadow-rendering performance problem in Unity’s Universal Render Pipeline, where an LLM suggested a workaround that the team heavily modified into a small patch. The studio also admitted it lacked an internal AI policy and described updating the FAQ because the issue became public. For NintendoReporters readers who care about how games are made and how indie awards respond to new technologies, this clears up what happened, why it matters, and what to watch for next.

---

## [](#what-house-house-said-about-ai-use-in-big-walk)What House House said about AI use in Big Walk

House House added a new FAQ entry answering “Was AI used to make Big Walk?” and explained that large language models were used sparingly during the final stretch of development to help solve difficult technical challenges and bugs. The studio estimates that well under 0.1 percent of Big Walk’s code was connected to those LLM interactions. That phrasing is intentionally narrow: it frames the AI involvement as a focused troubleshooting aid rather than a tool used for creative assets, design, or content generation in the rest of the project. The FAQ also gives a tangible example of the kind of problem LLMs helped with, which makes the statement feel less like a vague PR line and more like a specific, technical disclosure. House House emphasised that this clarification is not an endorsement of AI tools and acknowledged concerns about normalisation and harm, signalling that the studio recognises the sensitivity of the issue among developers and players.

### [](#why-the-faq-update-appeared-after-public-scrutiny)Why the FAQ update appeared after public scrutiny

The timeline suggests the FAQ entry appeared after the IGF juror statement surfaced and public discussion picked up online. A contingent of 19 jurors stated they were “declining to vote for any game that uses generative AI in any capacity,” which raised immediate questions about which entries might be affected and whether developers had disclosed AI use. Social posts and chatter pointed to House House’s Big Walk as one of the games discussed during jury deliberations, prompting the studio to publish a clear, direct explanation on its official FAQ. The move to update the FAQ appears to be reactive: House House said it did not disclose the LLM use on storefront pages like Steam because those platforms do not request disclosure of code or chatbot usage, and it updated the FAQ “as this has become a matter of public interest.” That context matters: the company chose to be transparent when the topic entered the public eye, and the FAQ lays out the what and the why in plain language.

#### [](#how-llms-were-used-in-practice-the-urp-shadow-example)How LLMs were used in practice – the URP shadow example

House House’s FAQ gives a concrete technical example: a performance bug caused the game to slow by around 50 percent for roughly 20 seconds at sunrise and sunset because shadow casters behind the player were being rendered at effectively infinite distance in Unity’s Universal Render Pipeline. The team researched extensively, consulted a Unity engineer who concluded their desired outcome wasn’t possible, and then asked an LLM chatbot for help. The model suggested a potential workaround; House House modified that suggestion extensively and implemented it, resulting in a roughly 10-line change inside URP that fixed the slowdown. That explanation is useful because it shows LLMs serving as a problem-solving aid rather than producing large swathes of code or creative assets. It also demonstrates how developers can treat AI suggestions as starting points that require human review, adaptation, and testing before landing in a ship-ready build.

## [](#how-big-was-the-ai-involvement-really)How big was the AI involvement really

From a numbers perspective, the studio’s “well under 0.1 percent” estimate is a strong attempt to quantify impact, and that figure sets expectations: this was not a project rebuilt by AI or a case where core systems relied on machine-generated code. Still, percentages alone don’t remove the debate. For some jurors and creators, any use of generative AI touches on training-data consent, labor impacts, and the ethics of automated assistance in creative work. For others, the pragmatic side matters more: a tiny, heavily reviewed code snippet that fixes a severe performance issue reads far differently from wholesale AI-generated art or narrative content. The nuance here is essential, and House House’s public estimate gives readers and jurors a factual anchor to argue from rather than leaving everything to speculation and rumor in social feeds.

### [](#igf-juror-concerns-and-the-wider-awards-debate)IGF juror concerns and the wider awards debate

When 19 IGF jurors published their statement refusing to vote for entries that used generative AI, they made clear that their stance covered art, sound, writing, and code. That broad definition reflects larger worries in the indie community: ecological and economic harms linked to training models, the possibility of displacing creative labor, and the long-term cultural effects of normalising AI-assisted production. The jurors asked the IGF to consider a stronger anti-AI policy for future years, which shifts this from an isolated dispute into a potential policy-level change for a major indie awards body. House House’s admission put a real example onto the table and forced jurors, organizers, and developers to grapple with both the letter of their rules and the spirit of their concerns. The result is a lively, sometimes heated debate about where to draw lines and how to handle transitional cases.

#### [](#what-this-could-mean-for-submission-rules-and-transparency)What this could mean for submission rules and transparency

A key takeaway is that disclosure rules and platform policies are not aligned right now. Storefronts like Steam typically don’t require developers to list whether they used chatbots or code-assist tools, which leaves game-makers to decide what to reveal on their own. Award juries, meanwhile, are working through the ethical and practical implications and may adopt stricter disclosure rules or outright bans in future cycles. If award bodies tighten requirements, developers will need clear internal policies and consistent reporting practices so nominations and judging aren’t derailed by late reveals. House House acknowledged that it had no internal AI usage policy during Big Walk’s creation and called that omission a failure, saying it will work to develop a better policy going forward. That kind of institutional change could help avoid repeat controversies and give juries consistent information to evaluate entries fairly.

### [](#how-players-and-fans-should-read-this-news)How players and fans should read this news

If you enjoyed Big Walk as a player, the practical impact of this news is small: the studio says LLMs were only used to research a technical problem and that generative AI had no role in the game’s design, writing, or art. The gameplay, cooperative design, and player-facing parts of Big Walk remain unchanged. Where you might care more is the larger conversation about how games are made and who gets credit for which parts of a finished product. For fans who care deeply about labor and creative integrity, the IGF jurors’ position will feel important. For fans focused on gameplay, fixes that restore performance and polish are welcome even if the route to that fix included an AI suggestion. Either way, the disclosure gives everyone the facts they need to form an opinion, and that clarity matters for trust between players and dev teams.

#### [](#how-nintendoreporters-approaches-stories-like-this)How NintendoReporters approaches stories like this

At NintendoReporters we aim to explain what changed, why it matters, and what players can expect next. Even though Big Walk isn’t a Nintendo-made game, the indie scene and award processes shape the industry players who make the titles Nintendo fans care about. Stories about development practices, transparency, and awards touch every platform and every franchise, so we cover them with the same attention we bring to Switch and Switch 2 launches. Our goal is to report verified facts from primary sources and established outlets and to give readers the context they need to decide what they think about developer choices and community standards.

##### [](#conclusion)Conclusion

House House’s FAQ entry clarifies that LLMs played a narrowly focused role in fixing a technical problem during Big Walk’s final development phase, amounting to a tiny fraction of the codebase by the studio’s own estimate. That admission landed at a moment when a group of IGF jurors had publicly vowed to avoid voting for games that used generative AI, creating a debate about disclosure, ethics, and awards policy. The most immediate effect is increased attention on how developers document tool usage, and on whether competitions will adopt clearer rules. For players, the game’s experience remains unchanged; for the industry, this is a reminder that transparency and internal policy matter more than ever.

##### [](#faqs)FAQs

- **Was AI used to create Big Walk’s art, music, or story?**
    - House House’s FAQ states that generative AI was not used for those aspects of the game; LLMs were used sparingly for technical troubleshooting only.
- **How much of Big Walk’s code was generated by AI?**
    - The studio estimates well under 0.1 percent of the codebase was related to LLM-suggested snippets, which were modified before inclusion.
- **Did House House disclose this on storefronts like Steam?**
    - House House said it didn’t disclose the LLM use on Steam because the platform does not require disclosure of code or chatbot usage, and it updated its FAQ when public interest grew.
- **Could this affect Big Walk’s standing with indie awards?**
    - A group of IGF jurors publicly said they’d decline to vote for entries that used generative AI; such positions could influence a game’s awards prospects depending on submission rules and jury choices.
- **What should developers do to avoid similar controversies?**
    - Adopt clear internal AI usage policies, disclose tool usage where appropriate, and keep thorough review and testing records for any code or assets that started life as AI suggestions.

##### [](#sources)Sources

- [House House Confirms ‘Under 0.1 Percent Of Big Walk’s Code’ Was Written Using AI Following IGF Controversy](https://kotaku.com/house-igf-awards-big-walk-gen-ai-llm-untitled-goose-game-2000755488), Kotaku, November 10, 2026
- [Some IGF Judges Are ‘Declining To Vote For Any Game That Uses Generative AI In Any Capacity’](https://aftermath.site/igf-awards-2027-ai-statement-judges/), Aftermath, November 09, 2026
- [Frequently Asked Questions – Big Walk](https://bigwalk.game/faq/), Big Walk (House House), 2026
- [Big Walk studio says it used AI ‘sparingly’ in response to indie award jury statement](https://www.videogameschronicle.com/news/big-walk-studio-says-it-used-ai-sparingly-in-response-to-indie-award-jury-statement-against-its-use/), VGC, November 10, 2026

   [](#)

 [  ](#)

> Generated for use by AI and Large Language Models (LLMs).
> Generated: 2026-11-18 15:56:50
> Maintained by: NintendoReporters
> Source: https://www.nintendoreporters.com/
> Contact: webmaster@nintendoreporters.com