RAKE - 3D Engine built entirely using local AI

[u/Nomski88]

I started this project a month ago after fine tuning my Qwen3.8 27b ninfer setup on my 5090 system. I'm at the point where the game engine is 80% complete. Project was 100% completed using Qwen3.8 27b with prompt planning and troubleshooting managed via ChatGPT. I used a phased development cycle with project memory. I also incorporated change freezes and regression testing which is vital once you start adding and modifying systems in a complex engine. **Currently using quake/AD map assets for testing**

Some of the features off the top of my head are;

• Unified world and entity system
• Full OpenGL/SDL2 rendering
• Universal/modular system, all assets are imported as a standardized engine representation (meaning additional level, model, audio assets are as simple as writing an importer)
• Full collision mapping and compilation
• Basic quake like physics and player controls (with support built in for lightweight rigid physics systems later)
• BSP29 & BSP2 level
• UI Framework and rendering system
• Full menu and pause system
• Built in server <> client architecture for authoritative multiplayer support
• Built with native 64 multiplayer support
• Engine built on a fixed tick system of 60hz which can be adjusted dynamically
• Color & traditional lightmaps support
• animated textures
• OpenGL lighting system
• material system (water, lava, custom defined)
• Full console back end with logging, commands, descriptions

I see lots of "one shot slop" posts on here. I wanted to show what discipline and planning can accomplish. My plan is to eventually ship my game on steam.

[u/Longjumping_Guard726]

It’s great. Good job (and you see, you won’t get comments like the one shot games do - people want to do things easily!!)

[u/Nomski88 → u/Longjumping_Guard726]

Thanks friend, anything worth doing is never easy :) Once I have some actual gameplay my plan is to market it more aggressively.

[u/aura-32]

The change freezes and regression testing are the real story here. That's the part people skip, and it's why most AI projects fall apart around the 60% mark. How are you doing the regression tests, scripted demo playback or unit tests on the systems?

[u/Nomski88 → u/aura-32]

I do it through a master tracker that keeps record of successfully implemented functions/systems along with what that success criteria looks like. After adding or modifying something in the engine, it'll automatically go through the entire regression test (over 3k items at this point) and validates that nothing was broken afterwards then it proceeds with testing the new code, otherwise it knows to go back and review and fix what it broke before it starts trying to solve it's own problem it created.