Build a Unity farming game with an overnight backlog runner and ship it to Steam

A game developer with 19 years' experience took a small Unity farming game from idea to a Steam page in about five weeks, with Claude Code writing nearly all the C# and working through a backlog overnight.

Done withClaude Code· Nov 12, 2026

What they did

The poster set themselves a challenge: carry one small game through development, art, marketing and the Steam launch alone, with AI doing the heavy lifting. Claude Code on Opus 5.5 wrote almost all of the C#, and an MCP server for Unity 6 (Funplay) let it inspect scenes, change values, take screenshots and play the game in the editor. Concept art and textures came from Magnific, 3D models from Tripo, and scripted Blender runs over MCP cleaned and resized those models. Plans, design ideas and feedback went into a backlog of cards. While the poster slept, a runner script fed one card at a time to the agent with a hard time and money budget, in its own branch: build the game headlessly, run tests, drive the built game to measure handling, screenshot it, and merge only if everything passed. A similar script filmed in-game camera shots, cut them into shorts and queued them for posting.

How it went

The game, a relaxed field-clearing farming game, reached Steam after about five weeks, and the poster says it was the first time in years making a game felt fun. They still made every call on feel and look, and the cutting mechanics, crops, camera, tractor handling and level setup took a lot of hands-on design and feedback rounds. Two gamedev subreddits removed their posts for disclosing AI use. The post gives no cost figures, though a commenter asked.

Worth knowing

The overnight loop only works because each card had a time and money cap and a pass-or-discard gate of headless build, tests and an automated playtest. Giving the agent a way to see and play the running game, not just edit files, is what the poster credits most. The poster tried several Unity MCP servers before settling on one.

Try it

With Claude Code· 6 parts to fill in

You are working on my Unity game in [project folder], with editor access through [Unity MCP server]. Take the next card from [backlog file]. Work on a new branch. Implement the card, then build the game headlessly, run the tests, play the built game to check [handling or feel metric], and take screenshots of the result. Stay within [time limit] and [spend limit] for this card. If the build, tests or playtest fail and you cannot fix them inside the budget, abandon the branch and write a note on the card explaining why. Only merge when every check passes, then stop and wait for the next card.

Square brackets are the parts to fill in. The prompt is ours; the story is theirs.

Where they said it

Related