A hobbyist dev spent almost a year on a $1.99 itch.io game — code, story, and mechanics their own, visual assets AI-generated. They disclosed the AI art on the game page and inside the game itself, expecting transparency to defuse the criticism. It didn’t: commenters called it AI slop without playing the demo. At ~120 upvotes, the thread turns into a useful post-mortem on why disclosure failed.
The core lesson: the label tracks the visible result, not the provenance statement.
- “It doesn’t matter what you disclaim, if it looks like generic ai, ppl will know” — the top reply’s diagnosis
- Getting a good art direction with AI and staying consistent with it across a whole game is the genuinely hard part — that’s what separates AI-assisted work from AI-looking work
- Uncurated output is ammunition: a commenter spotted unparsed markdown underscores in the OP’s writing and used it to call the “own story” claim hollow
- Context that matters: a corporate dev’s hobby project on free time, published through a friend’s Play account — not chasing a career, just didn’t want unjustified hate
- The OP argued back, then stopped and just thanked critics for the page views — probably the right call
Disclosure is a floor, not a shield. Audiences react to what a game visibly is, and anything that reads as generic AI — art direction, text, UI leftovers — earns the slop label regardless of how honestly it was labeled. For solo devs the real bottleneck isn’t the disclosure statement; it’s curation and keeping a coherent art direction.