Former Valve Dev Challenges Tim Sweeney on Steam AI Labels

The latest public argument over Steam, Epic Games and AI disclosure has gained a notably direct new voice: Chet Faliszek, a former Valve developer whose credits include work on Portal, Half-Life and Left 4 Dead. In a video response to recent remarks from Epic Games CEO Tim Sweeney, Faliszek rejected the framing that Steam’s AI labels are political tests and challenged the claim that Valve has kept PC gaming back through a closed social ecosystem.

The exchange is bigger than a pair of executives trading barbs. It turns on two practical questions for PC players and developers: what information customers should see before buying a game, and what responsibility a platform owner has to provide tools versus allowing other companies and communities to fill the gaps.

The AI-label dispute is really about buyer information

Sweeney has criticized Steam’s AI disclosure policy, characterizing it as forcing developers into a political statement that could be used by a hostile audience. He also raised a hypothetical comparison: whether Valve should require developers to reveal their political affiliations, and whether doing so could be considered pro-consumer.

Faliszek’s response is that the comparison does not fit the policy under discussion. In his view, no one is seriously calling for political-affiliation requirements. The relevant question is narrower: whether people deciding how to spend money should be told about a game’s use of AI.

“Players are just making informed choices,” Faliszek said, arguing that treating disclosure as unnecessary assumes players cannot decide for themselves what information matters.

An AI disclosure, in this context, means a label or statement that tells a prospective buyer something about a product’s use of artificial intelligence. It does not itself tell a customer whether a game is good or bad, whether its creators acted responsibly, or whether that customer ought to buy it. It supplies a fact that may matter to one customer and not another.

Faliszek made that distinction plainly. He said he personally does not care about AI use in the same way he does not care about a game’s frame rate, but he does not see a reason to object to the information being available for players who do care. That is an important separation between personal preference and platform policy. A customer can ignore a listed detail without insisting that every other customer be denied it.

For players, the immediate implication is straightforward. Disclosures can help people set their own filters before purchasing, whether their concern is generative AI, performance, accessibility, online requirements, supported hardware or another feature entirely. More information does not settle the debate over AI’s place in game development; it lets the debate remain a choice at the individual purchase level.

Fab complicates the argument against disclosures

Faliszek also pointed to Fab, Epic’s open digital-assets marketplace, as a complication for Sweeney’s stance. Fab uses AI disclosures, Faliszek noted, and Sweeney has said those labels would remain there even if Steam changed its own approach because they make business sense.

That leaves two positions in tension. If an AI label is useful enough to retain on an Epic-operated marketplace, it is difficult to portray the basic act of labeling as inherently improper when Steam does it. Faliszek seized on precisely that contradiction, suggesting Sweeney could not reasonably object to disclosure as political while accepting it as a practical marketplace feature elsewhere.

There is still room for disagreement about how labels should be written, what threshold should trigger them, or how prominently they should appear. The material here does not establish the details of Steam’s or Fab’s individual policies. But the broader principle behind Faliszek’s rebuttal is clear: marketplace disclosure is not automatically a declaration of ideology simply because some buyers use it to make value-based decisions.

Steamworks, cross-platform communication and the meaning of a walled garden

Sweeney’s other major criticism was aimed at Steamworks, describing it as a social walled garden that has held gaming back by locking PC games into an environment where players cannot communicate across iOS, Android, Xbox, PlayStation, Switch and other PC storefronts.

Steamworks is the set of tools and services associated with releasing games on Steam. In this dispute, it functions as shorthand for the relationship between a major PC storefront, developers using its platform services, and the social systems that players encounter around games.

A walled garden generally describes an ecosystem in which a platform owner sets the rules, controls key services and can make it harder for users or developers to move freely between competing systems. The phrase is often used as criticism, but it needs precision. A platform can offer integrated tools without every product becoming fully isolated, and an open set of choices can still involve trade-offs, fragmentation or reliance on third-party services.

Faliszek did not argue that Valve supplies every tool developers could want. In fact, he said Epic has an “amazing” toolset and a backend solution that surpasses Valve’s. A backend is the behind-the-scenes service layer that can support functions such as accounts, connectivity and other online infrastructure. It is not the same thing as the game players see and control, but it can be essential to how an online game operates.

His larger point was that Valve’s restraint can be interpreted differently from Sweeney’s criticism. Faliszek said Valve leaves room for communities and third parties to develop the tools they need, while also offering tools that developers may choose not to use. He described the use of third-party alternatives as acceptable rather than evidence of a failure.

That creates a genuine industry tension. One approach is to build a comprehensive, tightly integrated suite of services. Another is to provide some foundational support while allowing developers to select independent solutions. Neither approach is automatically pro- or anti-consumer in every circumstance. A fully integrated system can be convenient; it can also concentrate control. A more varied ecosystem can create flexibility; it can also ask developers to make more technical and business decisions.

Faliszek’s argument is that Valve would be criticized either way. If it attempted to solve every development and service need itself—covering engines, tools and more—he said the complaint would instead become that Valve had built an even more powerful monopoly. That does not prove Valve’s current balance is ideal, but it identifies a contradiction in demands that the company simultaneously do more and exercise less control.

The Alan Wake 2 challenge

Faliszek closed with a pointed challenge directed at Epic: put Alan Wake 2 on Steam. His contention was that restricting a game to a particular storefront is a clearer example of a walled garden and an anti-consumer limitation than Steam’s disclosure policy or its optional ecosystem tools.

The challenge reframes the storefront argument from platform architecture to access. For a player, exclusivity can mean a preferred store, account, library or social setup cannot be used for a particular purchase. For a developer and publisher, exclusivity can be part of a distribution strategy. The supplied material does not establish whether Epic will change the game’s storefront status, and Faliszek’s demand is an argument rather than a confirmed development.

Still, it gives the disagreement a useful test. Criticism of closed ecosystems carries more weight when applied consistently to one’s own business decisions. If broad player choice is the central principle, the discussion cannot stop at what services a rival storefront offers; it also has to include where major games can be bought.

Why this matters beyond one online spat

There is plenty of personality in this dispute. Faliszek told Sweeney he was “kinda crashing out,” and he suggested some of the CEO’s behavior was “AI psychosis.” Those remarks will understandably get attention. But the more durable issue is whether the industry treats players as capable of making their own choices.

Faliszek’s position is that a platform should not hide information simply because not all customers prioritize it. AI use may be a decisive issue for some players, irrelevant to others and one factor among many for the rest. That range is normal. It is also why disclosure is different from a mandate to approve or condemn a game.

For players: Labels can provide a basis for personal purchasing decisions without deciding those decisions for them.
For developers: Platform-tool choices involve trade-offs among integration, independence, cost, support and audience reach.
For storefronts: Claims of being open or pro-consumer invite scrutiny of both policy design and exclusivity practices.

The PC ecosystem continues to evolve through storefront competition, platform services and developer-controlled alternatives. That landscape also includes the day-to-day work of maintaining games after launch, as seen in updates such as a recent PC game patch that added public lobbies and new lore. Behind every argument about ecosystem philosophy are practical choices about who builds tools, how players connect and what information appears before a sale.

Sweeney has not been confirmed to have answered Faliszek’s latest video, and there is no indication that the broader disagreement is nearing a resolution. What is clear is that the argument is no longer only about whether AI belongs in games. It is about transparency, customer agency, distribution control and who gets to define what an open PC gaming market should look like.