
game-pipeline
Concept art (ChatGPT) -> Blender (Python) -> Godot 4 -> shipped Windows/Web/Android builds, with task1-5 templates.
- GitHub stars
- 6
Install
/plugin install game-pipeline@alchemists-of-pragueRun it inside Claude Code after adding the marketplace with /plugin marketplace add msveshnikov/alchemists-of-prague.
Contents
Discovered from sourceSkills 1
Game pipeline: concept art → Blender → Godot → shipped build
A workflow for 3D games where no asset is made by hand. Concept art comes from ChatGPT, everything 3D is generated by Python scripts running in Blender, and Godot assembles the game at runtime from JSON that Blender writes. Any file can be rebuilt with one command. It fits any 3D genre: RPG, shooter, horror, platformer, racing, survival, strategy with a 3D map.
Read only the reference you need for the current stage:
| Stage | Reference |
|---|---|
| Game idea → design doc, style block, prompts | references/01-concept-and-prompts.md |
| Ordering art from ChatGPT in the built-in browser (incl. attaching images) | references/05-chatgpt-browser.md |
| Writing task1–task5 files (templates) | references/02-task-templates.md |
| Blender: procedural assets, conventions, rebuild order | references/03-blender.md |
| Godot: runtime level loading, UI as code, autotest, exports | references/04-godot.md |
| Finish: commit, build all targets, deploy, verify | references/06-ship.md |
Helper scripts live in scripts/ next to this file (image upload to ChatGPT, aligning painted art
to a top-down layout render).
Tools the user needs
- Claude Code desktop app (for the built-in browser) and a ChatGPT account signed in there. No image API keys: art is ordered through the ChatGPT web UI like a person would.
- Blender 4.2+ — run headless:
blender -b --factory-startup -P script.py -- args. Blender MCP / Godot MCP are optional; the pipeline never waits for them. - Godot 4.x with export templates for Windows, Web, Android (Android also needs the SDK/JDK and a debug keystore).
- Python 3 with
numpy pillow opencv-pythonfor image tooling outside Blender. - Optional: a web server reachable over
scpfor hosting the Web build and APK.
Find the Blender and Godot executables first (often not on PATH) and write their paths into the project's README and memory, so later sessions don't search again.
The pipeline at a glance
- Design doc (
<Game> — concept art and tasks.md): pitch, genre, camera, core loop, player character, enemies/opponents, key mechanics, a style block pasted at the start of every art prompt, lighting/mood variants, and prompts for every location (plus an empty version), every character or vehicle, every UI screen, and a top-down world map. → 01 - Concept art via ChatGPT in the built-in browser: generate the best image first, then feed it back as a reference ("keep exactly the same art style as the reference image") for all the others. → 05
- Five task files, each self-contained and run in order by an autonomous Claude Code session:
task1.mdenvironment & props in Blendertask2.mdcharacters / creatures / vehicles: models, rigs, animationstask3.mdempty level(s): layout, gameplay markers, lighting presetstask4.mdpopulation: NPCs, enemies, pickups, effects, schedulestask5.mdthe game in Godot: controls, core loop, UI, progression, save/load, sound, builds → 02
- Vertical slice first: run task1–5 for ONE level or area (the most important one). Play it, fix the task files, and only then run task1–5 again for the remaining areas ("run 2"), and if the game has an open world, stitch them into one.
- Every task leaves a paper trail:
decisions.md(every choice made without asking),issues.md(what failed and the workaround),report_taskN.md(what was done / not done), asset lists, preview renders, README "Rebuild" section. - Iterate with reference art whenever something looks primitive: ask ChatGPT for a better prompt first, then the image, then make it fit the game exactly (e.g. align a painted map to a render of the real layout). → 05
- Finish every task by shipping: commit everything, export Windows + Web + Android, upload, open the live page and check it. Don't ask — this is the standing rule. → 06
Principles that made it work
- Autonomous mode in every task file: no questions, decide and log in
decisions.md, try another approach on failure, log toissues.md, never stop before the end, write a report. - Everything procedural: models, numpy-painted textures, rigs, skin weights, animations, level layout, population, UI textures, icons — all Python. No manual Blender clicks, so every fix is a code change and a re-run.
- Blender writes data, Godot reads it: glTF assets +
*_layout.json/*_population.json. The Godot scene is assembled at runtime from JSON, so a rebuilt level shows up in the game with no manual scene editing. - Strict conventions shared by all tasks (units, facing direction, node-name prefixes for
interactive objects, markers, lights and collision). Fix them in
decisions.mdin task1 and obey them afterwards. → 03 - Look at the result: render previews and contact sheets in Blender, take in-game screenshots with a scripted tour, compare against the concept art, fix, repeat. Never call something done without seeing it.
- Only free/open assets if anything is downloaded (CC0/CC-BY: Freesound, OpenGameArt, Kenney,
Quaternius, Godot Asset Library), each listed in
assets/CREDITS.md. No paid 3D generators. - Self-test: an
--autotestmode plays through the core loop and every system (movement, the main verbs, UI screens, progression, save/load, failure/death) and writes screenshots + a log; a--tourmode shoots given spots. Run them after every change.
Starting a brand-new game
- Pin down the basics, asking the user only for what they haven't said: genre, camera (first person, third person, top-down, isometric, vehicle chase cam), setting and art style, core loop (what the player does minute to minute), player verbs (shoot, slash, jump, drive, build, sneak...), opponents, progression, target platforms. Everything else you decide.
- Draft the design doc from 01's template.
- Create the folder layout:
concept/{locations,characters,empty,ui},blender/scripts,assets/{architecture,props,characters,textures,levels,ui,audio},scripts/,renders/,build/. Put a.gdignoreinconcept/andconcept_art/so Godot doesn't import reference images. - Order the concept art (05). Ask before each download, as the browser rules require.
- Write
task1.md–task5.mdfrom 02, filled in for this genre and scoped to the vertical slice. - Run them one at a time (a fresh session per task works best; each reads the previous reports).
- Ship (06). Then expand to the other areas with run 2 of the tasks.
Adding to an existing game made this way
- New level or area: write run-2 style task1–5 sections for it (02), reuse the libraries in
blender/scripts/lib_*.py, add abuild_<area>step, then stitch it into the world builder. - New look for something: order reference art (05), then change the generator code, re-run, compare.
- Always finish with 06.
Sponsors
Details
- Marketplace
- msveshnikov/alchemists-of-prague
- Source
- msveshnikov/claude-game-pipeline
- Category
- Community