A r/gamedev essay from a self-described AI skeptic argues the AI-in-gamedev question is not black and white. He concedes generative tools produce new compositions but not new ideas — then draws a sharp line between where AI is a liability and where it genuinely helps.
The line he draws:
- Art, sound, and writing are a non-starter — derivative work is “creatively bankrupt,” and if the legal consensus lands on LLM output as derivative, it becomes a liability for any studio.
- The “AI is inevitable” framing is wrong — the future is set by present actions, and community pushback matters.
- The one genuinely exciting use case: a reactive story truly personalized to each player.
- Code is the gray area — copying code has always been normal (Stack Overflow, similar implementations everywhere), so AI-assisted code is less of a philosophical problem.
- His position evolved: older models couldn’t reliably produce working code; current ones implement well-described features in one or two passes.
- AI code is “average at best,” but shipping beats elegance — Undertale’s famously messy code powered a very successful game.
The essay’s sharpest distinction: derivative art is a legal and creative liability, while average code that ships is a productivity win. The author offers no general answer for where the line sits — but argues dismissing AI entirely is as short-sighted as evangelizing it. The thread’s top commenters add a useful counterweight: the economic and environmental costs, and the risk of problem-solving muscles atrophying for developers who never learn the underlying craft.