An r/aigamedev dev posted Moonlight Harvester, a 2DHD idle RPG in Godot, three months after starting AI-assisted game dev and 50+ abandoned prototypes. The current project is about two weeks old. He states plainly that he has zero coding experience and no plans to sell it — free on itch.io eventually.

The screenshots are the pitch. The pipeline is the useful part, because asset consistency is where most AI-built games fall apart:

  • Engine: Godot, driven from Codex and Claude Code, with the Godot MCP wired in for harder tasks only
  • 2D sprites and animation: PixelLab. 3D: Tripo, plus Claude with Blender MCP
  • No asset packs at all — every sprite is GPT Image-Gen or PixelLab, every model is Tripo or Blender-via-Claude
  • Visual north star: Octopath Traveler, for the high tilted camera and the tilt-shift look

The animation loop that keeps characters from drifting between clips:

  • Start from an approved character design and use it as the identity reference
  • PixelLab’s PixMiniMax animates each clip from a short action description, at most two jobs running at once
  • Every result is checked for identity, motion, loop seam and alpha, then judged in-engine before integration with fixed ground anchors

The limits he reports are as instructive as the wins:

  • Local models were not up to it — OpenCode with a Gemma 4 model “was pretty bad.” The quality came from frontier models, not from the harness
  • 3D placement is still manual labor: the models get assets placed, but he moves nearly everything by hand — clearing paths, pulling bushes out of houses
  • Credits, not capability, gate 3D work; Tripo burns them fast enough that new assets wait for next month
  • The UI was redone in one pass two days before posting because the earlier version “looked not so good” — a model upgrade retroactively fixed older work

One community note fixed the most common tell in AI art in minutes: throw world-space noise on terrain textures to break up the visible repeating pattern of tiled ground.

Generation is not the hard part; making two hundred assets look like they belong to the same game is. The gates that work are mechanical and cheap — identity match, loop seam, alpha, ground anchor, then judge it in-engine — and the rest is taste applied by hand. The bottleneck shows up in credits and manual cleanup, not in the prompting.