The AI Scarlet Letter is a storefront problem, not an AI problem
By Oleg Sidorkin, CTO of Cinevva
On June 25, Epic CEO Tim Sweeney called Valve's Steam AI-disclosure requirement "really irresponsible." His argument was blunt. You have to ship on Steam so people can wishlist you, and the moment you do, "you have to get this Scarlet Letter of AI attached to your product, and now there is a hater community trying to kill the game." His conclusion: the tag makes it "much, much, much harder for a game developer to have a chance of success."
The uncomfortable part is that the data backs the fear. Per Game Oracle, titles carrying the generative-AI disclosure pulled in 53% fewer reviews than comparable games without it. Reviews feed the recommendation engine, so the gap compounds. Fewer reviews means less visibility, which means fewer players and fewer reviews again.
The contradiction nobody is naming
Here's what makes this the story of the month rather than a spat. Sweeney said this eight days after his own company shipped the loudest pro-AI move in engine history. At State of Unreal on June 17, Epic revealed Unreal Engine 6 and shipped 5.8 with experimental MCP server support, a plugin that wires LLMs like Claude and Gemini straight into the editor. So the same person runs the biggest engine, which is racing to put AI at the center of how games get made, and attacks the biggest storefront for admitting AI was used to make them.
Call it hypocrisy if you want, but it maps where the tension actually sits. AI is welcome at the tooling layer, where it saves the developer time and nobody outside the studio ever sees it. AI is punished at the shipping layer, where the storefront prints a label and the crowd decides what it means. Same technology, opposite treatment, and the line between them is exactly the storefront's edge.
Sweeney's fix aims at the wrong target
His pitch is to remove the label. That treats the symptom. The label is only lethal because Steam is a single gate that a few thousand games pass through every month, where a "made with AI" tag becomes a coordination point for a review-bombing crowd and a signal the recommendation algorithm quietly reads. Strip the tag off and you still have the gate, the crowd, and the algorithm. The penalty just moves somewhere harder to measure.
The disclosure isn't the trap. The chokepoint is. Any single storefront powerful enough to make a wishlist matter is also powerful enough to make one label decide a launch. Developers who built their whole distribution on that gate are discovering that the gate has opinions.
The browser doesn't hand out Scarlet Letters
A game that runs at a link has no disclosure form, no tag, and no crowd waiting at a single storefront to sort it into "real" and "AI slop" before anyone plays it. The judgment happens where it should, in the first thirty seconds of play, not in a metadata field the algorithm reads before the game ever loads.
To be clear about what this does and doesn't fix, people who hate AI art will still hate it in a browser tab. The sentiment travels. What doesn't travel is the institutional label that turns a sentiment into a sorting rule, the checkbox an algorithm reads and a review-bombing crowd coordinates around before anyone presses play. Strip that away and the question collapses back to the only one that was ever fair: is the thing fun. A browser game earns its audience the same way whether a human or a model drew the trees, and that's the difference between distribution you rent and distribution you own.
What this means if you're building
Sweeney is right that the disclosure penalty is real and that it's going to shape what gets made. He's wrong that the answer is to argue the label off the biggest storefront in the world. You don't win that fight, you just wait for the next policy. The move is to stop needing the gate that prints the label in the first place.
We built Cinevva around exactly that. Games made and played in the browser, shared as a link, judged by whether they're fun and not by how they were made. The studios fighting over the AI tag are fighting over shelf space in a store. The more interesting bet is that the store stops being the only shelf. When your game opens in a browser tab, the Scarlet Letter has nothing to pin itself to.
Related:
- The 52/52 split — company adoption and developer backlash sit at the same number, and storefront rules are part of why
- Everyone wants to be the AI game engine now — the tooling-layer land grab that Unreal Engine 6 just escalated
- AI-native engines are shipping — MCP in the editor was a startup idea in March, it's in Unreal now
- For game creators — publish playable games to a link, no storefront gate, no disclosure tag