Tim Sweeney Calls Steam’s AI Disclosure ‘Abhorrent’

Epic Games' Unreal Engine AI MegaJam: Cash for AI 'Slop' Games

Tim Sweeney fired off a short, sharp post on X and the thread turned hornets. He called Valve’s forced AI disclosure “abhorrent” and warned it would hand a weapon to organized critics. You could feel the room split in two.

I watch this stuff because you should know the playbook. You’re looking for what this actually changes for developers, storefronts, and anyone trying to sell a game without being dragged into a political fight.


At 10:23 a.m. on X, Sweeney wrote a one-line blast that ricocheted across the industry.

Sweeney quoted an employee at a generative media firm who called AI-disclosure rules “absurd” and “truly embarrassing” for Valve, and then added his own verdict: “Forcing developers to write a political statement to be used against them by the hate mob they’re helping organize is abhorrent.” That sentence did two things at once — it framed the label as a political act and cast Valve as the enabler.

Why did Tim Sweeney call Steam’s AI disclosure “abhorrent”?

Short answer: he thinks the policy weaponizes transparency. In Sweeney’s reading, a mandatory disclosure is not a neutral consumer note; it becomes a tag that opponents can use to mobilize against a developer. I don’t have to tell you how fast online outrage travels — the CEO’s claim feeds on that speed.

Sweeney’s stance sits inside a larger argument he’s been running for months: Epic is pro-AI and pro-fast rollout, critics are suspicious, and public labels become rallying points. You can trace the context to Epic’s recent PR: a new, “fully vibe-coded” storefront, a patched competition, and an AI hackathon that doubled as a marketing moment.

Steam games library
Steam has developers announce their use of AI when putting games in its storefront. Image via Steam

On Oct. 22, Epic rolled out a storefront update and pushed an AI MegaJam the day after Valve quietly sped its own client.

The marketing was loud: a promo image nodding to The Matrix, two hands offering colored pills, and one hand with six fingers offering the AI-friendly pill. Epic crowed about speed, calling its UI “vibe-coded” and flaunting the MegaJam. I call that move theatrical — they were positioning their AI-first posture as a selling point.

Sweeney is the final boss of vibe-coding.

That same week Valve shipped a patch that made Steam feel snappier, quietly cutting into Epic’s headline claim. The timing turned the marketing moment into a narrative battleground: speed, aesthetics, and the ethics of AI usage all became competitive levers.

What does Steam’s AI disclosure mean for developers?

It does two, opposing things. For consumers, a disclosure is a simple signal: you’ll know whether text, voice, or art was generated or assisted by AI before you buy. For some developers, the signal looks dangerous — it can draw attention, invites bad-faith campaigns, and might reduce sales if a segment of players refuses AI content.

Steam’s disclosure becomes a bullseye that organized mobs can aim at. Valve argues that the label protects buyers; Epic argues it weaponizes studios. You can see both positions make sense depending on your incentives: platform trust versus developer safety.


In public, the argument now folds into platform strategy and PR theater.

Epic is loudly pro-AI and willing to court controversy to set norms. Valve is positioning itself as consumer-protective by forcing transparency. NVIDIA’s DLSS 5 and other runtime AI tools live in this same ecosystem, where benefits and pushback travel together.

If you run a small studio, you’re watching this fight with real stakes. A label that repels buyers could feel existential; being labeled non-AI might look like a marketing advantage. Either way, the rules being written today will shape discoverability, storefront moderation, and how community outrage affects commercial outcomes.

I’ll keep tracking the beats and the backchannels so you don’t have to sift through every tweetstorm. Are developers about to be asked to pick a side and pay for it?


Read more sharp takes and quick explanations in the Moyens I/O Checkpoint newsletter — a few sentences, some snark, less fluff. Subscribe here