A hobbyist solo dev in r/gamedev asks how to stay motivated when an AI could “one-shot” his small indie game. He develops slowly, deliberately keeps design decisions out of AI’s hands, and fears that by the time he ships in two or three years, one-shot generated games will be good enough for the indie market. His image for it: a sculptor who lives next to a factory casting a thousand copies of everything he makes.
The ~190-upvote thread does not resolve the market-timing fear. Instead it lands on a mix of factual check, product thinking, and one practical test.
- Nobody has actually one-shotted a full, hours-long, good game yet — what exists is impressive tech demos and short clips. “Good enough” is not the same as finished and playable.
- Millions of human developers could also build your game faster than you. If ease of replication does not invalidate your work when the faster maker is human, it should not when the faster maker is a model.
- The one-shot test: hand the AI your design doc and let it try to build the whole game. Either the result is hollow and unplayable — confirming what is yours is worth finishing — or it succeeds, and you merge and ship faster.
- If an AI can trivially reproduce your game, the game is probably generic. The defense is originality, not speed.
- Understanding every detail of the project is a bad goal anyway. What matters: Is it fun? Does it meet its design goals? Does it run well enough? Does it reward players? “The interesting part isn’t, and never was, how it was made.”
The emotional core of the thread is worth more than the reassurance: the understanding, decisions, and learning do not show up in the output, but they are real and stay with you. A finished small honest game that could only have come from you keeps its value regardless of what the tools can now produce. Comparison is the thief of joy — including comparison with a machine.