Big Walk's AI Disclosure Debate Intensifies as Steam Reviews Recover

Big Walk has become the latest game caught in the increasingly heated debate over generative AI in game development. The co-op title's Steam user reviews dropped after developer House House disclosed that limited portions of its development involved large language model tools. Since then, the game's overall Steam reception has recovered to Very Positive, with recent reviews sitting at 87% positive at the time of the discussion.

The situation has drawn comments from Cliff Bleszinski, the lead designer of the original Gears of War trilogy. In public posts, Bleszinski characterized the negative review activity as review-bombing and argued that players angry about the disclosure should reconsider their reaction. He also maintained that AI-assisted tools are already broadly used across game development, even when studios may be reluctant to discuss that use openly.

The disagreement around Big Walk is not merely about whether AI was used. It has also focused on what kind of AI was involved, how limited that use was, whether it should have been disclosed earlier, and what consumers should reasonably expect from a studio releasing a game on Steam. The case illustrates why even a narrowly described use of LLMs can trigger a much larger conversation about labor, authorship, quality control, platform policy, and trust.

Embedded X/Twitter post

House House describes limited LLM involvement

House House acknowledged the use of AI tools after several jurors connected to the Independent Games Festival stated that they would not vote for productions using the technology under any circumstances. The studio said that LLMs were used for small parts of Big Walk, estimating that the relevant material amounted to well under 0.1% of the game's total code.

For useful background on this topic, read Raw Fury Unshowcase Reveals Dungeon Automata Date, Kingdom Two Crowns DLC and More.

The developer's description is important because "AI use" can cover an enormous range of practices. It may refer to generative systems used to produce artwork, dialogue, music, marketing copy, or game code. It can also refer to more contained technical assistance, including troubleshooting a specific issue, generating an initial programming suggestion, or helping developers investigate an error. Those distinctions are central to the discussion, but they have not eliminated the objections of players and industry figures who oppose the presence of generative AI in creative work altogether.

Some Steam users responding to the controversy argued that the scale and stated purpose of the AI use should matter. One reviewer described the backlash as disproportionate, while another said that using an AI tool to help resolve a bug that even Unity itself could not fix sounded like one of the more defensible applications of the technology. Other players have taken a stricter stance, contending that any use of LLMs is a concern regardless of whether it represented a tiny fraction of the finished project.

That divide is unlikely to disappear soon. For some players, the core principle is that game creators should avoid generative AI entirely, particularly amid concerns about training data, creative labor, and the prospect of replacing artists, writers, programmers, and other workers. For others, the practical details are decisive: a game made substantially through generative systems is seen as fundamentally different from one in which a developer briefly consulted a tool while tackling a difficult technical problem.

The Steam disclosure question

A major point of criticism has been the absence of an AI-related disclosure on Big Walk's Steam page before the issue became public. Valve's Steam policies require developers to disclose certain uses of AI in their games, a rule designed to give the platform information about AI-generated material and its implementation.

House House said it did not make a Steam disclosure because the platform does not request disclosure for code or chatbot usage. The studio added that it was making the statement because the matter had become one of public interest. That explanation has shaped the response in two directions.

Supportive players have argued that the studio followed the practical distinction outlined in its statement and did not conceal AI-generated art, audio, writing, or other player-facing assets. Critics, meanwhile, have argued that the absence of a voluntary disclosure still matters. From that perspective, the issue is not limited to satisfying the narrowest reading of a storefront requirement. It is also about providing buyers with clear information before a controversy forces the matter into public view.

Transparency has become one of the most difficult areas for the industry to navigate. Studios may fear that any AI label, even one covering minimal internal use, will cause players to assume a game was generated wholesale. Players on the other side may conclude that unclear labels or delayed statements mean a developer is withholding information. Both concerns can feed a cycle in which disclosures arrive only after outside scrutiny, producing more suspicion than an earlier and more detailed explanation might have generated.

For a smaller studio, the stakes can be especially high. Independent games frequently rely on community goodwill, personal reputations, and a perception of careful craft. A dispute over development tools can therefore become much larger than the actual amount of code, art, or text at issue. Steam reviews, social-media discussions, award eligibility, and future purchasing decisions can all become tied to a single development-process question.

Bleszinski says AI use is already widespread

Bleszinski's comments place the Big Walk dispute within a broader industry argument. The veteran designer said that people need to "get over themselves" in response to the game's AI backlash, framing the review activity as an excessive reaction to tools used to help finish a project. In further replies, he argued that many, if not nearly all, developers are using AI in some form, but may not want to acknowledge it because of the hostile response such an admission can attract.

His position reflects a common argument among AI advocates: that the technology has already become embedded in everyday workflows, and that treating all usage as equally unacceptable fails to distinguish between automation, assistance, experimentation, and content generation. Under that view, the discussion should focus on specific applications, safeguards, and disclosure rather than treating the mere presence of an AI tool as disqualifying.

Opponents reject the idea that widespread adoption makes the practice acceptable. They argue that prevalence does not address the ethical and legal concerns associated with generative models, including questions over the material used to train them. They also warn that normalizing limited uses today can make it easier for publishers and studios to expand those uses tomorrow, potentially reducing jobs or changing the creative makeup of games.

Neither side is discussing a hypothetical future anymore. Generative AI has become a practical policy issue for game storefronts, festivals, studios, contractors, and players. The result is that each newly disclosed case becomes a test of how audiences will respond--and whether a developer's explanation is enough to retain trust.

Steam sentiment shifts back toward positive

Despite the review backlash, Big Walk's Steam rating has climbed back to Very Positive. Its recent-review score of 87% indicates that many players continue to evaluate the game favorably, including some who openly dislike generative AI but do not believe the studio's stated use justifies a negative review.

That recovery does not mean the controversy has been resolved. Steam's user-review system often becomes a venue for broader disputes that go beyond gameplay performance, design, and value. Reviews can function as a way for players to signal concern about business decisions, studio conduct, moderation, technical policies, or industry trends. Supporters may then post positive reviews to counter what they see as an unfair campaign, creating a second wave of reviews driven by the controversy itself.

In that environment, a score can reveal changing sentiment without offering a simple verdict. A rebound may show that players consider the final game worthwhile. It may also reflect the view that House House's explanation placed the AI use in a sufficiently limited technical context. At the same time, negative responses remain meaningful evidence that a segment of the audience expects stronger or earlier disclosure from developers working with these tools.

Why the Big Walk debate matters

The dispute around Big Walk demonstrates that the conversation around AI cannot be reduced to a single yes-or-no question. The details matter: what tool was used, what it produced, whether the output made it into the shipped game, how much of the production it affected, whether workers were displaced, and how clearly the studio communicated its choices.

House House's estimate of well under 0.1% of the game's code gives players a concrete scale to debate, but it does not settle the matter for those who believe any LLM use crosses an ethical line. Likewise, Bleszinski's argument that AI is now common throughout development may describe an industry reality, but it does not erase audience concerns about where adoption is heading.

For developers, the clearest lesson may be that technical compliance and community confidence are not always the same thing. Even when a platform does not request a particular form of disclosure, players may still expect one. For players, the case also highlights the value of examining specifics before judging a game: "AI-assisted development" can describe radically different practices from one project to another.

Big Walk's recovered Steam rating suggests that many users have accepted House House's explanation or chosen to judge the game primarily on its own merits. But the conversation surrounding it is likely to continue, because the standards for AI use, labeling, and accountability in games are still being established in public, one controversy at a time.