Kicked out of gamedev forums for using AI, a 19-year veteran showed exactly how Claude built his farming game

The pitch is almost aggressively simple, and that is the point. In Just Farm you get in a tractor, clear a huge field, and think about not much else. Sell what you cut, make the machine faster and wider, open more land, and repeat. There is nitro, for no agricultural reason whatsoever. The tractor drifts. Auto-harvesters can clear fields on their own while you work somewhere else. The Steam page is explicit that realism was not the priority: clearing a field in the most satisfying way possible was.

What made the game travel was not the loop, though. It was the confession attached to it. The developer, posting as u/SirKnighty on r/accelerate on the evening of October 27, said he has made games for 19 years, that making them had gradually turned into a job, and that this one — built in about five weeks — made it fun again. He also said gamedev forums had removed his game for using AI. So instead of hiding the method, he laid it out in full, tool by tool, in a post that gathered about 630 upvotes and 146 comments, anchored by a 90-second video of the game in action.

The stack, step by step#

The breakdown is specific enough to be checkable, which is rarer than it sounds in AI-made-game posts. Claude Opus 5.5, running in Claude Code, wrote basically all of the C#, according to the author. A tool called Funplay MCP, paired with Unity 6, let Claude drive the Unity editor directly — inspecting scenes, changing values, and taking screenshots to see what it had done. Magnific produced concept art, textures, and material maps. Tripo turned the concepts the author picked into 3D models. Blender, driven by scripts through MCP, cleaned those models up, split them, rescaled them, and fixed them.

The author is equally specific about what the model did not do. He says he still made every taste call, and that manual game design work and feedback were still needed. That distinction matters, because it is the difference between two very different claims: that an AI made a game, and that a developer used AI tools across every stage of making one. The Steam page tells the same story in its own disclosure: generative AI tools were used during development to assist in pre-generated visual and audio content, all of it reviewed and integrated by the developer before inclusion, with no generative AI running during gameplay.

Why it got removed — and why the thread split#

The removal itself is the author’s account, and it is worth stating that plainly: the post says his game got removed from gamedev forums for using AI, and no forum moderator statement appears in the thread to confirm or contest it. What is visible is the reaction it provoked. The top comment, from u/aj_marshall with 209 upvotes, praised the game and then argued there is no benefit to telling people how it was made outside technical communities — at least where AI use is concerned. Under it, u/kalabaleek (98 upvotes) put the quiet part bluntly: everyone is using AI today, but many feel they have to stay quiet about it to avoid enraging an anti-AI crowd.

The author, replying in the thread, agreed with the broad point: most game developers are using AI tools now, many have to hide or minimize it, and Steam’s AI label makes little sense once those tools are standard. He also said he was surprised by the amount of hate. The thread’s supportive wing was loud too — “That looks really nice! It’s a shame people are such luddites,” wrote u/Ok_Letterhead1945 (100 upvotes) — and several commenters immediately asked for features, including a zombie mode the author said was already on his mind.

The pushback that actually lands#

None of the criticism in the thread debunks the core claim, and the Steam listing backs it up: the game exists, the description matches the video, and the AI disclosure is public. But three objections are worth carrying forward because they sharpen what “AI-made” should mean. First, u/klumpp asked whether the post is just an ad, noting a hidden post history — a fair question for any self-promotional launch post, and one the thread itself cannot fully settle. Second, u/DurrMerGurd asked whether someone who “did none of the work” should expect praise for “making” a game — a framing the author’s own account answers in part, since directing, selecting, and playtesting a five-week build is work, even if the typing was largely delegated. Third, the farming-realism quibbles: one commenter questioned whether the game would work on Steam rather than as a mobile title, another said the first tractor vibrates too much, a third that the fast tractors kill the chill vibe. Those are design notes, not refutations — and the Steam page concedes the realism point upfront.

What to watch#

Three things will decide whether this thread is a curiosity or a marker. First, whether Just Farm finds players beyond the thread — a Reddit upvote is not a player base, and the game’s deliberately narrow loop will either charm or bore people quickly. Second, whether disclosure norms keep shifting in the author’s direction: if AI tool use is now standard practice among developers, as he argues, then removal policies and disclosure labels built for a different era will keep producing exactly this kind of fight. Third, whether the vocabulary catches up. “AI-made” currently covers everything from a model typing every line to a human directing a suite of tools, and those are not the same achievement. This post is useful precisely because it refuses the vague version and itemizes the real one — code, editor control, art, models, cleanup — so readers can judge the work for themselves.

Sources: the original post by u/SirKnighty on r/accelerate (October 27, 2026); the Just Farm page on Steam, including its AI-generated-content disclosure. The editorial illustrations are AI-generated.