Tech & AICan It Code?AI Built This Space Game From Scratch — Here's Exactly How

AI Built This Space Game From Scratch — Here's Exactly How

Long-form17:30GamingPublished Aug 23, 2026, 6:48 PM · 8w ago
Views
48,026
+0 views/hour
Views / hour now
0
measured 19h ago
Peak views / hour
—
 
First 24 hours
—
not tracked from upload
Engagement
3.8%
likes + comments / views
Likes
1.6K
3.4% of views
Comments
216
0.45% of views
Est. ad revenue
$336–$768
lifetime, $7–16 RPM

Checked every 24 h while the video is this age · last check 19h ago · next in 268 min. YouTube itself updates public counts with a short delay.

Avg views / day
839
since upload
vs channel median
1.0×
this video's views ÷ the channel's usual
Rank in channel
#10
of 20 tracked

Views over time

0 readings

Total views Views gained per hour
Live tracking started
The chart fills in as FameX records new readings.

Description

One week, four AI models, and a playable sci-fi game in Godot — built from literally nothing. No asset packs, no templates, no pre-made scenes. Grey boxes on day one, a lit and textured ship with a walking astronaut on day seven. You asked for the workflow after the last video, so this time I skip nothing: how the work gets handed out, how Blender gets driven without ever touching the mouse, how a game gets tested by an AI instead of by me, and every place it broke along the way. WHAT'S IN IT · The Color Bible — one palette every model is contractually stuck with · One orchestrator model that builds nothing and only hands out work · How to actually test a game with AI: let it measure, then let it look · Blender with no mouse — the model writes Python, Blender runs it headless · The Gauntlet Loop, run on one task instead of a whole game · An astronaut with 41 solid parts, 17 joints, no skeleton and zero animation frames — every step is calculated in Godot, live · Code-generated textures vs Poly Haven photos, side by side · Seven lighting modes, from day to full blackout · The frame rate disaster: under 30 FPS, and the fix nobody expects · Spiders that had to learn to walk — and started flying instead TOOLS Godot Engine · Blender · VS Code with Claude Code, Kimi Code and Codex Models: Fable 5 (orchestrator), Opus 5, Kimi K3, GPT-5.6 CHAPTERS 0:00 From a grey box to a ship 0:19 One week, four models, 100+ agents 0:33 The setup — VS Code and three extensions 1:05 The idea, the references, the Color Bible 1:48 The plan, and the model that builds nothing 2:21 How you test a game with AI 3:05 Grey boxes first 3:53 Blender with no mouse 4:44 The Gauntlet Loop 6:05 The rooms, for real 7:50 Space, the planet and the ship outside 8:12 The astronaut — 41 parts, zero animation 9:14 Teaching him to walk 10:19 Textures: code vs Poly Haven 11:07 Lighting, mode by mode 12:08 Under 30 FPS — and it was the shadows 12:48 Spiders that started flying 14:04 The story 14:26 Full playthrough ASSETS Sound effects: Pixabay (free license) Planet model: the only ready-made asset in the whole project Everything else — every wall, room, tool, suit and creature — was generated during this build. If you like this kind of thing, subscribe — I'm on the road to 10k.
Tags
AI codingcan it codeAI builds a gameAI game developmentGodotGodot 4AI coding challengeGPT vs ClaudeClaude vs GPTAI vs AILLM comparisonAI programmingcoding with AIvibe codinggame devindie game devartificial intelligenceAI experimentsGPT 5Claude OpusGLM

Statistics from the YouTube Data API, tracked by FameX. Views per hour, revenue and comparisons are FameX estimates.