A r/ClaudeAI post from Aug 18, 2026 — Week 3 of making my fishing game entirely with AI — is the opposite of a one-prompt Three.js clip. User u/RUSuper is three weeks into a Godot 4.7.1 fishing game, ~617 upvotes at scrape, a ~53-second in-engine video, and a workflow dump that is more useful than the footage.
This is not a playable demo. The author said they want more quests before sharing an .exe, and that friends have only poked fishing feel and art direction. Treat every technical claim below as self-reported. We did not run Godot, Blender, or their MCP servers.
If you want the clip, watch it on Reddit. We are not hosting their gameplay video.
What they actually built (claimed)
- A Dredge-adjacent boat-and-fish loop (they said Dredge and Civilization as inspirations; commenters clocked the inventory immediately).
- Graphic overhaul plus real 3D models versus earlier weeks.
- Water as Godot shaders, not a ChatGPT still.
- HUD still "work in progress" — ChatGPT mockups, Claude replication, lots of image elements, polish later.
- Design ideas that are not in the build yet: a river you cannot fight until a stronger hull, max boat level 5 unlocking Arctic water. They explicitly said no submarine.
Commenters compared it to Dredge, Age of Empires 3, Grepolis. The author had not played AoE3. Visual resemblance to a beloved commercial game is both the compliment and the risk: vibe-coded games that read as "Dredge with fewer tentacles" will get that line forever.
The pipeline, as a harness
1. Human eye first: ChatGPT as art director, not as engine
They generate references in ChatGPT / OpenAI Playground: concept art, fishing-structure mockups, skill-tree background. Quote the load-bearing sentence: without a human eye, "AI will just make stuff not fit together."
Advice they gave others: do not ask the model whether the image is good. Generate until you say you love it. Then keep iterating. Do not try to 1:1 clone a ChatGPT still into Godot — "they are just too perfect." Close enough, then the scene evolves as you add things.
That is the same split as Dilum Sanjaya's 5-hour cozy prototype: the model produces candidates; a human keeps taste.
2. Geometry as code: Blender MCP, not Rodin
They tried Rodin. Complicated meshes, lots of cleanup. They switched to a dedicated Blender session writing models via MCP.
Why it fits this camera distance:
- Script is the source of truth.
- Proportions stay editable.
- A family of assets stays a family.
- Low-poly is enough.
That is closer to Anthropic's Claude for Creative Work Blender connector and Tencent's WorldClaw BlenderMCP refine loop than to "upload a PNG, get a hero mesh." If you need a directory of servers, start at explainx.ai MCP servers.
3. A different session integrates
Placement, waterline, scale, wiring live in a non-modelling session. They described a window per concern, plus a general chat that can dispatch instructions to the others.
That is multi-agent orchestration by habit, not a fancy graph product. Same failure mode as any dispatcher: the modeller never sees the camera; the integrator never owns the mesh family.
Weeks 1–2: Claude Desktop, no MCP. Week 3: Claude Code + Godot MCP + Blender MCP. They think MCP spends less than Desktop. Unverified.
4. The in-game camera is the unit test
"Screenshots are the referee." Render from the actual game camera. Nothing counts until they looked at it.
The waste they admitted: four new islands, signed off from overhead, pancakes in play. From above, a pancake is a perfect island.
This is the 3D version of "the agent grepped the wrong log." Your eval distribution has to match the player's. Overhead orthographic is a different game.
If you copy one rule, copy this one: the agent's screenshot tool is not the game. Pin a short shot list in the integrator session (bow, three-quarter, dusk, HUD on, HUD off) and reject any "looks good" that is not from those cameras. Map, editor, and top-down debug views are allowed for placement, not for shipping art.
5. Scored critics, criteria written first
For a graphics pass they wrote scoring criteria before changing anything, scored twelve things out of ten, shipped only at 8+. One critic saw screenshots without being told which version was newer.
That is loop engineering with a blind A/B, not "I changed a lot so it is better." Pair it with Dilum's improvement-list: ranked work and a numeric bar.
A rubric that would have caught pancake islands: silhouette from player height, waterline contact, sand vs rock read at 30m, lighting consistency with the rest of the starting area, "would I screenshot this for a friend." Write those lines before the pass. After the pass, a second session scores stills with filenames like A.webp / B.webp and no "new"/"old" in the prompt. If the newer set does not clear 8, you did not ship a graphics upgrade — you shipped churn.
6. USER vs AI tags (steal this)
Every decision is written down and tagged: the human decided it, or an AI suggested it.
Failure mode: an upgrade nobody proposed sat in design docs and got quoted back as the user's idea.
That is intent provenance, not pixel provenance. If you run many sessions, this is cheaper than arguing with a hallucinated product spec. See when to stop the agent for the same gate in code agents.
A one-line schema is enough: YYYY-MM-DD | USER|AI | topic | decision | still in build?. The "still in build" column is the one that stops a discarded AI suggestion from reincarnating as a requirement three sessions later.
What to tell each session (copy this)
You do not need their exact MCP servers to steal the roles. Three windows, three system reminders:
- Art director (image gen). Output is reference only. Never writes Godot or
.blendfiles. Job: lock silhouette, palette, and "this is the fishing structure / skill-tree board / HUD ring." Stop when you would hang the still on the wall — not when the model says it is cohesive. - Modeller (Blender MCP). Input is those stills plus a poly budget. Output is scripts (or a blend that those scripts can rebuild). Forbidden: placing the island in the ocean, writing water shaders, "does this look good from above." Allowed: family variants (hut A/B/C) from one proportion sheet.
- Integrator (Godot MCP). Input is exported meshes and a shot list. Output is transforms, waterline, collision, lighting, shaders. Forbidden: inventing a new hull upgrade because it "would be cool." Allowed: asking the dispatcher to file an
AItag if it wants to propose one.
The dispatcher session holds the decision log and the critic rubric. It is allowed to quote the other sessions; it is not allowed to overwrite USER tags. That is the whole orchestration product. Graphs and subagents are optional; the role split is not.
Desktop-without-MCP vs Code-with-MCP is a tooling detail. Desktop is fine for the art-director chat. Code plus MCP is what makes "the script is the mesh" and "the shader is in the repo" true. If your Godot MCP cannot capture the game camera, you are back to pancake islands — screenshot-from-editor is not an eval.
Cost, effort, and what is not in the post
They said $200 Max plan, first two weeks at the limit, week 3 mostly polish so spend dropped. They described using "Ultracode" as highest-effort Claude. We are not treating that string as an official product name.
Hobby framing: they compared the subscription to months they would have bought games or Lego. That is honest and useless as studio forecasting.
They declined to make a tutorial video until a playable demo exists. Fair. A 53-second montage is not a reproducible build log.
Steal vs skip
Steal
- Split look (image gen) from geometry (Blender scripts) from integration (Godot).
- Eval from the player camera, not the debug camera.
- Write critic rubrics before the pass; blind the version labels.
- Tag USER vs AI on every design decision that will be re-quoted later.
- Keep UI late (their advice to another hobby RPG builder): mechanics spawn HUD you will throw away.
Skip / caveat
- Do not copy Dredge's silhouette and call it original. Inspiration is fine; "looks like Dredge" is the comment section.
- Do not confuse a pretty water shader with a game. Commenters already split: process is the game vs quality bar for other people's catalogues is still high.
- Do not assume MCP is cheaper. One user's week-3 polish phase is not a benchmark.
- Do not ship Rodin (or any generator) meshes into production without a cleanup budget — they bounced for a reason.
The thread's own split is worth keeping: people who make games with agents are often not the audience for other agent-made games, and a catalogue of generated assets is tiring to sort. A starting area with water that "looks alive" is still not a demo if the loop is repeated fishing. OP's own bar — more quests before an .exe — is the adult version of that comment.
Related on explainx.ai
- Build a game prototype in 5 hours (improvement-list) — shorter loop, same human-taste gate
- Claude games viral wave — one-prompt browser worlds vs this multi-week Godot harness
- World of ClaudeCraft — another long Claude-built game world
- Tencent Hunyuan WorldClaw — Blender MCP as a refine tool in a 3D agent
- Claude for Creative Work (Blender connector)
- What is MCP?
- What is vibe coding?
- Loop engineering
- Human-in-the-loop: when to stop the agent
- MCP servers on explainx.ai
Sources
- Week 3 post (r/ClaudeAI) — u/RUSuper, Aug 18, 2026; upvote count at scrape
- Author replies in-thread: Rodin vs Blender MCP, pancake islands, shaders, Max plan / Ultracode, Dredge + Civ, no demo yet, UI last
- r/ClaudeGameDev — subreddit the mods linked from the thread
Independent verification of Godot version, MCP server names, and token burn: none.