North Line Gaming is an independent publication covering PC games, major updates and new releases with clear reporting and a player-first perspective.
Canada
Joined October 2026
- Tweets49
- Following0
- Followers0
- Likes2
Able retweeted
Someone with zero coding background shipped a game in 6 weeks with Claude Opus 5.5 and Godot, and the setup is worth copying line by line.
The rule underneath all of it: one feature at a time, tested in the game, before the next one exists.
Step 1 -> Opus 5.5 in Claude Code, opened inside the Godot project itself.
Step 2 -> Build one feature, play it, adjust until it feels right, only then start the next.
Step 3 -> Reference images in the game's style from Codex/Astra.
Step 4 -> Every image prompt that works gets saved as JSON and fed into the next generation, so the style never drifts.
Step 5 -> Big 3D assets in Tripo P2, built from those references.
Step 6 -> Small props modeled in Blender, textured in Tripo with the same refs, which is the cheap route.
Step 7 -> Animation in Cascadeur.
Step 8 -> Every VFX and shader documented in Obsidian so the look holds across six weeks.
Who does what:
> Opus 5.5: most of the code.
> Codex/Astra: references and assets.
> Tripo P2: the big 3D models.
> Godot: custom tools, headless scripts, the game itself.
One JSON file of good prompts is the reason every character, monster and prop looks like it belongs in the same world.
(Built by afterthewinddev, all credit there.)
I built an Ori-style platformer with GPT Image 2.5, Tripo and Claude Opus 5.5, and it runs on desktop and on a phone. The whole thing comes down to one rule.
Make it exist first. Make it good after.
What came out: a night storm, wrecked ships, piers, buoys, and one glowing giant you have to read before it hits you.
The order:
Step 1 -> Mood boards in GPT Image 2.5: storm, piers, wrecks, one boss that glows.
Step 2 -> Tripo P2 turns the mockups into 3D: the giant, the ships, the piers, the buoys.
Step 3 -> Blender cleanup: scale, pivots, low poly so a phone can hold 60 fps.
Step 4 -> The hero stays 2D: a run, jump, attack sprite dropped into the 3D world.
Step 5 -> Opus 5.5 writes the game: movement, jumps, camera, rain, water.
Step 6 -> The boss gets one readable rule: the giant's light shows where the fist lands.
Step 7 -> SFX and music from ElevenLabs, at the very end.
Step 8 -> Deploy to Vercel, send the link, watch people die to the giant.
The split:
> GPT Image 2.5: every mood board.
> Tripo + Blender: every model.
> Opus 5.5: the code, the camera, the weather.
> ElevenLabs: everything you hear.
> Me: play the grey box and decide what stays.
Ship the ugly version that works before you polish anything. A playable grey box beats a beautiful mockup every single time.
