Certified into the record
The exact text we saved
This is the version exactly as it was saved, character for character. The SHA-256 hash below is a 64-character code worked out from that text. Run the same text through SHA-256 and you get the same code; change a single letter and the code comes out completely different. Each version also stores the previous version’s hash, which chains them together so no version can be swapped out quietly.
TRUVACE RECORD VERSION record: TRV-2026-2478 version: 1 kind: certified reason: Certified into the record timestamp: 2026-11-12T06:01:36.555793Z status: published lens: p_space sector: entertainment headline: Big Walk used AI to fix a bug. Now the indie gaming world is having a reckoning. dek: Any amount of AI coding is too much for many Indie Game Festival judges. The last few years have seen significant debate over the widespread use of AI-powered tools in game development and the responsible disclosure of that usage to players. That debate has exploded into a full-blown controversy in the indie game developm gain_title: (none) problem_title: After House House disclosed that an LLM chatbot helped with a bug fix amounting to "well under 0.1%" of Big Walk's code, 19 Independent Games Festival jurors said they would not vote for any game using generative AI, and the game drew over 400 negative Steam reviews. trace_subject: (none) gain_reading: (none) gain_evidence: (none) problem_reading: After House House disclosed that an LLM chatbot helped with a bug fix amounting to "well under 0.1%" of Big Walk's code, 19 Independent Games Festival jurors said they would not vote for any game using generative AI, and the game drew over 400 negative Steam reviews. problem_evidence: well under 0.1% of Big Walk‘s code | declining to vote for any game that uses generative AI in any capacity | over 400 negative reviews quick_read: Big Walk developer House House said this week that LLMs were used sparingly late in development to help with technical problems and bugs. It put the AI-written share at well under 0.1% of the game's code. The disclosure came as 19 members of the 50-plus-member Independent Games Festival jury signed a statement declining to vote for any game using generative AI in any capacity. The bug involved a Unity engine problem that produced "infinite length" shadows and slowed the game. A Unity engineer told the studio a fix wasn't possible, so it asked an LLM chatbot. The studio said it modified the suggestion extensively into 10 lines of code. At least one social media user says the bug was fixable with significant human effort. The row shows how little AI use it takes to become contentious in indie games. Some judges said even minimal use outweighs their admiration for the game. Others argued that punishing a small, disclosed use discourages transparency and encourages hiding AI use. Valve's Steam rules do not require disclosure of code or chatbot use, while the IGF Awards make no such distinction. limitation: The 0.1% code share, the 10-line fix and the account of the bug come from House House's own statement, and at least one social media user says the bug was fixable with significant human effort. tag: Evidence-backed problem key_points: 19 of the 50-plus IGF jurors signed a statement declining to vote for any game using generative AI and urged the festival to adopt a policy disallowing AI-generated work. | House House said LLMs were used sparingly near the end of development and amounted to well under 0.1% of Big Walk's code. | The studio consulted an LLM after a Unity engineer said a fix for the shadow bug wasn't possible, then modified the suggestion extensively into 10 lines of code. | House House did not disclose the usage on Steam because Valve does not request disclosure of code or chatbot usage, but it mentioned it in its IGF submission. | Big Walk's Steam page received over 400 negative reviews, though Steam's anti-review-bomb tools seem to limit the impact on its overall Very Positive rating. | Judge Liz Ryerson said she did not find the use disqualifying, and curator Dominic Tarason called it a minor failing, while AI researcher Mike Cook said the action is part of the same problem as AI-driven layoffs. | Last year the Indie Game Awards rescinded awards for Clair Obscur: Expedition 33 after the developers admitted some in-game textures were made using AI. rundown: The jury statement, released Monday, cited a significant increase in submitted games developed with generative AI tools. It named ecological, economic, psychological and labor harms and called the tools' use "not a foregone conclusion in our industry." It did not name any game, but Big Walk quickly became the focus after House House gave a statement to Aftermath, later added to the game's FAQ page. House House wrote that its disclosure was not an endorsement of AI tools. It said it worried voluntary disclosures might contribute to normalizing the technology and apologized that its LLM usage may not meet the standards of those limiting generative AI's harm to games. Judges Austin Walker and Damon Reece praised the game but said minimal AI use still overrode that respect, with Reece calling it a pain that has to happen to steer the culture away from AI. Others pushed back. Ryerson said many acted as if there were no levels to AI use, and Tarason said the developers spent years on the work and asked a chatbot for two minutes how to fix a bug. Professor Brendan Keogh argued that zero tolerance is counterproductive because it encourages people to hide use, while narrative designer Hannah Nicklin called zero tolerance a viable political position aimed at a system rather than individuals. sources: - journalism | Ars Technica | https://arstechnica.com/gaming/2026/11/big-walk-used-ai-to-fix-a-bug-now-the-indie-gaming-world-is-having-a-reckoning/ | 2026-11-11 prev: 0000000000000000000000000000000000000000000000000000000000000000
- SHA-256 hash
- 04d8175d674bcee6df18771cebeb70f6db00f844a41a77facacb9ced105c3c8a
- Previous version’s hash
- 0000000000000000000000000000000000000000000000000000000000000000
How to check it yourself, without trusting this page
Download any version from /api/record/TRV-2026-2478 and hash its canonical field yourself, for example with shasum -a 256. You should get its content_hash. Each version’s text also ends with prev:and the hash of the version before it (version 1 points to 64 zeros). If anyone had changed a single character of any version after it was saved, those hashes wouldn’t line up.
ace