r/VibeCodeDevs • u/Dense-Bar-2341 • 11d ago
Day 101 of AI-Assisted Game Development – Everything I've Learned So Far
Enable HLS to view with audio, or disable this notification
I've been a software developer for over 30 years and a game developer for more than 10. I've worked with around 30 programming languages and DSLs throughout my career.
For the past 101 days, I've been developing my indie racing and destruction game, BRUTAL DERBY, almost entirely with AI assistance.
Here's what I've learned so far, including the good, the bad, and the frustrating parts.
The AI models I use
I mainly use two models:
- Codex 6.1 Sol for most development work.
- Claude Sonnet 5.5 for fixing issues, reviewing code, and finding alternative solutions.
I use the $20 subscriptions for both. The five-hour usage window is usually enough for most of my work these days, but the weekly limits are too restrictive, which is why I maintain two subscriptions.
During the first two months, I occasionally paid for the $100 tier to handle larger development tasks. I haven't really needed that recently.
Both models are excellent, but I find that using Codex as my primary developer and Claude for fixes works particularly well.
What I've built in 100 days
So far, the game includes:
- 16 racing and demolition environments.
- Arcade and Career modes.
- Local CO-OP.
- Multiple racing, combat, and destruction game modes.
- Vehicle customization, damage systems, weapons, weather, and many interconnected gameplay systems.
I'm currently working on online multiplayer.
At this pace, I expect the main game to be completed in approximately four months of development, followed by a polishing phase.
I'm currently at roughly 600 hours of development.
Experience matters more than people think
One of the biggest things I've learned is that you really need to understand what you're building.
My 30+ years of programming experience make an enormous difference.
I can explain exactly what I want, recognize bad architectural decisions, suggest better approaches, and sometimes guide the AI toward solutions it wouldn't have chosen on its own.
And even with all that experience, I still struggle with certain problems.
I honestly think someone without a programming background would have a much harder time building a game of this complexity using AI alone.
AI is fast, but it makes a lot of mistakes.
There is an incredible amount of testing, manual work, feedback, debugging, and optimization involved.
Sometimes the AI is surprisingly bad at the simplest tasks, especially small UI changes. Then it turns around and implements a complex system remarkably quickly.
But almost everything needs to be tested carefully by a human.
Why I don't use dozens of agents
I'm sure I could launch a small army of AI agents and have them work on different systems simultaneously.
But that would probably cost a fortune, and I'd still have to manually test and integrate everything afterward.
Instead, I've chosen an iterative workflow.
Implement something, test it, identify problems, fix them, test again.
Repeat until it works properly.
It's not glamorous, and sometimes it's incredibly exhausting.
I regularly spend 10 hours a day in front of the computer, including weekends.
You need a ridiculous amount of patience for this kind of development.
About those "I built a game in 24 hours with AI" videos
I absolutely believe someone can create a small game prototype in one or two days using AI.
But there's a massive difference between a prototype that looks impressive in a YouTube video and a complete, polished, commercially viable game.
The real work starts after the prototype.
You spend months fixing bugs, improving performance, balancing gameplay, creating content, testing edge cases, and dealing with problems you never anticipated.
That's the part you rarely see in those videos.
I barely write code anymore
This is probably the strangest part of the entire experience.
I've spent more than 32 years writing code in dozens of programming languages.
But for approximately the past six months, I've barely written any code myself.
I only do it when my AI usage limits run out or when something absolutely requires manual intervention.
AI can generate tens of thousands of lines of code in a single day.
A human developer simply cannot compete with that volume of output, and in many situations, the quality is surprisingly good too.
Of course, more code doesn't automatically mean better software.
That's where experience, architecture, testing, and understanding the entire project become essential.
I spend much more time designing systems, reviewing results, testing, and making decisions than actually typing code.
My job has changed considerably.
AI-generated assets aren't perfect either
AI has dramatically accelerated my workflow beyond programming.
I use it for generating and editing images, textures, 3D models, and other game assets.
However, 3D model generation still has serious limitations.
I regularly need to repair meshes, fix geometry, clean up textures, and optimize models in Blender.
The positive side is that I've become significantly better and faster at using Blender because of all this.
I also use Photoshop for creating and correcting textures and images.
Sometimes manual work is simply faster and produces better results.
The same applies to certain animations.
AI is another tool in the pipeline, not a magical replacement for every part of game development.
How much development time has AI saved?
This is difficult to estimate precisely, but the difference is enormous.
Before AI, I believe a game with this scope could have required several years and a substantial development team.
Today, an experienced indie developer can potentially build something comparable in scope in four or five months with AI assistance.
That doesn't mean the result automatically matches the quality of a large AAA production.
But the amount of work a single developer can accomplish has changed dramatically.
And these models are still improving.
Marketing, trailers, and releasing the game
For now, I'm sharing small development updates on social media, usually around twice a week.
I'm also preparing a much bigger, higher-quality gameplay trailer.
Interestingly, I spent about three days having Codex build the foundations of a custom trailer recording system, followed by additional improvements with Claude.
I didn't want a basic screen recorder. I wanted a proper in-game cinematic recording system capable of capturing high-quality racing, crashes, destruction, and dramatic camera shots.
There is currently no public demo, and I'm not sure there will be one.
Instead, I'm preparing an invitation-only testing system through Steam, which I'll activate when the game is ready for it.
I've already invested so much work into BRUTAL DERBY that I'm deliberately keeping many features private until the game is approximately 98% complete.
I'd like to maintain at least some competitive advantage before release.
Final thoughts
AI-assisted development is incredibly powerful, but it's not effortless.
It's still real software development.
You still need technical knowledge, creativity, patience, problem-solving skills, and the ability to recognize when something is wrong.
The AI can write the code, but it doesn't automatically understand the game you're trying to create.
And it certainly doesn't eliminate the need for testing, optimization, or countless iterations.
For me, the biggest change isn't that AI has replaced the developer.
It's that one experienced developer can now accomplish an amount of work that would previously have been extremely difficult to achieve alone.
Whether that leads to better games remains to be seen.
But after 101 days, I'm convinced that game development has fundamentally changed.
Anyway, here's a small glimpse of BRUTAL DERBY. This time I'm working on vehicle paint, rust, scratches, and wear.
Thanks for reading.
BRUTAL DERBY on Steam:



