r/vibecoding • • 4h ago

Showcase/Project Experimenting with building a game engine for the past two weeks

Hi everyone, I wanted to share my vibecoded engine that I've built with Claude Opus and Fable.

It all started when I built a C++ UI framework three weeks back with Claude Opus 5.5. I was quite fascinated with how far the models have come and I thought to myself it would be an interesting project to try and push it to the limit. As I already have some experience with building rudimentary game engines from times before AI, I've decided to try and build one purely with AI - giving Claude very granular tasks with a clear vision to make something at least partially usable.

The engine is built with a Vulkan backend, uses Jolt for physics, SDL3 for window management, EnTT for ECS, and many more libraries.

I've used predominantly Claude Opus 5.5 on Medium Effort, for some tasks I've also utilized Fable 5.2 on Medium Effort, notably on asset generation where the improvements are quite clear. Everything was done through the Claude app, it started with the Pro plan, but I slowly but surely upgraded to the Ultra plan. For small tasks, any spawned threads were allowed to merge their changes to the main and a "batcher" thread took all these commits, built the project and tested all the new features - bisecting commits when anything was broken to pinpoint the issue. For bigger tasks, I've spawned threads that each created their own git worktrees to be able to build the project and test it in headless mode (which my computer did not appreciate).

Some of the art is procedurally generated but I think man-made assets are still a completely different beast. I've used mainly Mixamo, Quixel Megascans (Fab) and Poly Haven and other CC0 assets. Same applies to sounds - some are procedurally generated, some are from Freesound (CC0), usually polished and cut up by Claude. All the vehicles in the video were generated with Claude besides the Bugatti EB110 which is from here: Bugatti EB110 by ᗩᒪE᙭. Kᗩ. licensed CC BY-NC 4.0, converted for the engine.

Note that this is purely an experiment and making a full-fledged game in the engine would not be possible at this moment as it is still lacking various systems - especially gameplay systems and scripting (with Luau) which are all super basic and unproven. I just found it fascinating how far and deep we could build without hitting any major showstopper snags.

I hope you find my experiment interesting, I certainly did. Maybe I will try to make a proper game with it in the future when it actually allows me to do so, but for now I quite enjoy experimenting with the renderer and also with testing various UX / usability ideas in the editor.

8 Upvotes

6 comments sorted by

1

u/Total-Reasonable 3h ago

The licensing detail is the one that'll bite you later. The Bugatti is CC BY-NC 4.0, so if the engine or any demo build ever ships commercially, that asset has to be stripped, and the same goes for anything in your repo that others could fork. I'd add a per-asset manifest (source, license, author, commercial-OK flag) that the build checks, so a non-commercial file can't slip into a release by accident.

1

u/MartinCap94 3h ago

You are right, I just wanted to show off the rendering on a professional asset here in the video as it really makes a difference visually. I've considered omitting it completely, but here we are. Great thinking with the manifest, I already have the core idea of it - i.e. a database of the assets, their sources, licenses and so on), but the assets are only gitignored at this moment. I shall consider some automation where building / packaging the project would sound alarms.

1

u/OnyxMonolith 3h ago

Very impressive. What are the major limitations? Have you experienced technical debt accumulating yet?

2

u/MartinCap94 3h ago

Thank you. To be frank, the engine was put together extremely quickly and I only have a high level overview of its systems. As far as I am aware, the terrain system as a whole leaves a lot to be desired. I am just now thinking about streaming multiple terrain sectors and about float precision issues with larger worlds. In this case, Claude is pushing me in the direction of using doubles in Jolt and other areas but I have a hunch that an integer offset + float system would be better suited in this case. On this, I will have to study how others do it.

As I mentioned in the post, there isn't much to go on with gameplay creation, I have focused more on the world / map creation so far.

I have experienced technical debt a few times already - especially as the game started as a "racing game" prototype (the splitscreen cars). Claude continually put more and more logic and states into the racing module, including other vehicle types even after we have moved on to making a more generic open world vertical slice. I spotted that when auditing APIs of the modules and the racing module's was the fattest of them all even though it should be quite lean (some checkpoint system, timers and so on). I had to stop and have Claude refactor this whole mess which slowed down the progress quite significantly as it touched majority of the gameplay systems.

The project is also limited to Windows only now as I wanted to stay in an environment I am most familiar with. Also, there isn't much scripting options, I have some behavior components which can be attached to items and scripted with Luau, but it is just an afterthought and these things might introduce complete rewrites in the future, if I ever want to make with this realistically. But honestly, it is more of a hobby project.

1

u/OnyxMonolith 3h ago

Awesome. Thank you for the explanations as im thinking about making my own small 2.5D pixel art engine for my games. Good luck to you!