3D Game Design – Using ChatGPT o3-mini-high, Grok3, and Claude Sonnet 3.7
No, this isn’t a comparison of the three LLMs. At best, it’s a guide; at worst, just some casual reading. The goal was simple: could I create a 3D Space Invaders-style shooter without writing code, while still being able to share the final result with the world? Here’s how it went:
I started by outlining the game’s requirements—rules, visuals, and mechanics—using a rough draft. Of course, being a bit lazy, I asked ChatGPT 4o to fill in any missing features or dynamics I hadn’t accounted for.
With this rather long list that described the game (95 lines), I then turned to ChatGPT o3-mini-high and Grok3 to generate the actual game. Interestingly, Grok3 was much faster and, in my opinion, produced a better result. While the game mechanics weren’t significantly different between the two, I preferred Grok3’s visuals.
Continuing with the Grok3 version, I iterated on it several times, adding features like an AI player, a Pause function, and other refinements. This resulted in a somewhat playable game, all contained within a single, large HTML file.
Next, I wanted to embed this game into my website, which runs on Angular. For this task, I turned to Claude Sonnet 3.7. I had just been approved to use their new agent (“Claude”), which I’d previously tested on another project. I added the HTML file to my project folder and asked Claude:
“I’ve added a file in the app folder called grok_invader.html. I’d like to make this a component so that when users visit /invader, it displays that file while retaining the website’s header”
To my surprise, Claude nailed it on the first try. It automatically split the large HTML file into three files typical for Angular components:
• invader.component.html
• invader.component.scss (stylesheet)
• invader.component.ts
The most interesting part? Claude handled the JavaScript injection in invader.component.ts automatically—I never explicitly told it to do that. This turned out to be a clever approach, making everything work seamlessly.
The Verdict
The entire process took about 1.5 hours. Is it perfect? No. There are occasional timing issues, and at later levels, maneuvering becomes increasingly difficult. But given the minimal effort, I’m convinced:
The way we write software has forever changed.
Try it out yourself: https://vanguardsignals.com/invader
What do you think? Is this the future of software development?

Comments
Post a Comment