TUNEDb894rel/engines-tools4 min read

House House estimates AI touched well under 0.1% of Big Walk code

House House says language models helped with under 0.1% of Big Walk's code, including a Unity rendering fix. The disclosure drove Steam reviews to 36% positive amid calls for clearer AI rules.

Big Walk devs admit to gen AI use, worry that they're part of the problem amid backlash on Steam
Big Walk devs admit to gen AI use, worry that they're part of the problem amid backlash on SteamPexels / pixabay

Patch notes

  • House House estimates that well under 0.1% of Big Walk's code had any connection to LLM use.

  • An AI-suggested Unity rendering fix covered about 10 lines inside URP.

  • Steam reviews stood at 36% positive with 156 negative ratings, versus one and three negative reviews on the preceding two days.

  • Big Walk had launched five months earlier, limiting most players' refund eligibility.

  • An IGF juror group said it would not vote for any game using generative AI in any capacity.

By Elena Vasquez

House House estimates that large language models touched “well under 0.1%” of Big Walk’s code, according to a public statement the studio published on the game’s FAQ page. The co-op title had entered its final development stretch when the developer used chatbots for technical research and difficult bug fixes. House House says generative AI played no part in any other part of making the game, including artwork and voice acting.

How did AI enter Big Walk’s code?

House House says developers sometimes copied snippets from model responses as a starting point and then modified them into game code. The studio labels its under-0.1% figure an estimate. Its primary use case was research into problems with third-party code through chatbots.

One example involved a significant slowdown at sunrise and sunset. The team found no solution itself or after asking an engineer who worked for Unity. It then asked an AI chatbot for help. “After a few dead ends, it suggested a possible fix, and while we had to modify the suggestion extensively, it worked,” House House said. The change covered about 10 lines of code inside Unity’s Universal Render Pipeline, or URP.

The episode had a narrow operational boundary. The chatbot supplied a possible fix. House House altered the suggestion before putting it into the game. The studio did not use AI to generate the broader game.

Why did Steam and the IGF react differently?

House House sent a version of its statement to the Independent Games Festival as a suggested part of the game’s submission. Separately, a group of IGF jurors posted on Bluesky that the number of submitted games developed with generative AI had increased significantly for the upcoming awards. The group said it did not speak for IGF leadership or every juror.

The jurors said they were declining to vote for any game that uses generative AI in any capacity. Their rule covers artwork, voice acting and code. They cited three broad concerns:

  • Ecological harms.
  • Cognitive and psychological harms to users.
  • Harms to labor and worker power in creative fields.

Steam followed a different disclosure practice, according to House House. The studio said Valve does not request disclosure of code or chatbot usage on Steam pages. Big Walk’s FAQ statement therefore went beyond what the developer described as Valve’s requirements.

This produced two standards with different reach. The jurors’ refusal applies only to their votes for the upcoming awards show. A Steam disclosure reaches buyers directly, although House House says the platform asks for neither code nor chatbot use.

What does this change for studios and players?

The immediate response came from players. At publication, Big Walk’s Steam reviews stood at 36% positive, with 156 negative ratings. The previous day had one negative review, and the day before had three. A number of negative reviewers also said they had refunded the game.

“Undisclosed use of AI to finish their game. This is a misrepresentation of the quality and effort put into an otherwise wonderful game. What a disappointment,” one Steam reviewer wrote. Another said they could no longer love the game and called the situation maddening. A third described the lack of disclosure as disturbing, upsetting and disappointing. One reviewer said they would have made a refund public if the purchase had fallen within the eligible period.

The timing limited the financial consequence. Big Walk had launched five months earlier, and GamesRadar+ argued that most players were probably past the purchase date and playtime needed for a Steam refund. That assessment explains why a large review reversal may not produce a matching wave of refunds.

For studios, House House’s response makes disclosure an operational issue. The developer acknowledges that Big Walk shipped without an internal AI usage policy and calls that absence a failure. It says it will work toward a more comprehensive policy.

The studio says its disclosure does not endorse AI, even in minimal doses. It supports work to limit generative AI’s harm to videogames and the wider world. House House also apologizes that its use may not meet those standards.

There is tension inside that position. House House worries that voluntary disclosures could normalize generative AI or make it seem inevitable, while the same disclosure now informs players, jurors and potential submitters. For an IGF game, any generative AI use can remove it from consideration for the jurors’ votes. For a Steam release, the studio’s account leaves disclosure voluntary unless developers choose to publish it.

The practical answer is straightforward: studios need a written policy that covers code and non-code uses, and they need to decide what disclosures reach players before backlash makes the decision for them. House House has committed to a policy rather than published one. The next signal to watch is whether it delivers one, and whether other developers attach similar AI statements to Steam pages or IGF submissions.

via gamesradar.com (Source)

Share this article:

More from Elena Vasquez

Elena Vasquez

Show full bio

Staff writer covering regulation, policy and their impact on video game industry at Game Dev Wire.

248 articles