An AI voxel game maker that runs on your own machine
Voxel games are the clearest case for building on your own hardware. Chunk generation, meshing and a world the player can dig through are all things that fall over in a browser tab and are ordinary on a desktop. Free AI to start: Flockbay's AI and your own Claude, ChatGPT, agent or API key are free for your first build; after that, a plan keeps you building. It runs on Windows, macOS and Linux, on the official Godot engine.
The main page on this subject is What is an AI game maker that writes a real Godot project?.
AppImage, x86_64. Ubuntu 22.04, Debian 12, Fedora 39 or newer.
Intel or AMD Chromebook, with Linux turned on.
Why voxels and browsers do not mix
A voxel world is a memory problem before it is a graphics problem. You are holding a large grid, regenerating meshes when it changes, streaming chunks in and out as the player moves, and doing all of it fast enough that nobody notices. It is the kind of workload that punishes every layer of indirection between your code and the machine.
This is why voxel games made in browser tools tend to be very small, very flat, or very slow. It is not that the developers were lazy. It is that the environment does not have the headroom.
Flockbay is a desktop application for Windows, macOS and Linux with Godot bundled inside it. Press play and the game runs on your computer, with your memory and your framerate. Nothing is streamed and nothing is rendered somewhere else.
The code you would otherwise be writing
Voxel is the genre where a non-coder hits the wall fastest, because there is no way to fake the core system. You need chunk storage, a meshing pass that does not generate faces nobody can see, a system that rebuilds only the chunk that changed, and terrain generation that produces something worth exploring rather than uniform noise.
Flockbay writes that as GDScript inside your project. You describe the world you want: caves that actually connect, ore that gets rarer with depth, a surface with biomes that blend rather than snap. It writes the generator and you go and look at what came out.
Looking at what came out is the real work. Terrain generation is a parameter search, and the parameters are judged by walking around in the result. You will spend more time deciding whether the caves feel right than anyone spends on the code.
Set pieces are placed with intent, not rolled
Not every part of a voxel game should come out of noise. Structures, landmarks, a starting area, the village the quest points at. These need to be placed with intent: Flockbay places them where the brief says, and you walk the result. When the village should sit on the next hill, say so, or move it yourself in Godot's 3D view.
The non-voxel parts of the world are built normally too. Terrain, water, weather and lighting sit underneath, from Godot plugins or the scene's own environment, so a voxel game with a real sky and real rain is not a hack. It is just the rest of the scene doing what it does.
Mixing the two is the interesting territory: a generated landscape with hand-placed set pieces, which is how most good games in the genre actually work.
Playing, breaking, and asking again
Mining, placing, inventory, crafting, tool durability, day and night, mobs that path across an uneven grid. All of these are requests. You describe the behaviour and Flockbay writes it into your project.
The first version of a mining feel is almost always wrong. Blocks break too quickly or the arm swing has no weight or the placement preview snaps to the wrong face. You play it, you say which, it changes. That loop is the normal way to work here.
Building needs an internet connection, since the chat and asset generation come over the network. Playing the game you built does not.
Style, and why voxel does not have to mean blocky
Voxel is a data structure, not a look. The genre is dominated by one visual style because one game established it, but a grid of volumes can be rendered smoothly, shaded flatly, textured densely or reduced to solid colour, and the choice is yours rather than the format itself.
Palette is the cheapest lever you have. A voxel world built from twelve colours that agree with each other looks intentional. The same world built from every colour available looks like a test scene, and no amount of lighting fixes it afterwards.
This is where building on a real engine pays off. Lighting, fog, sky and post-processing sit underneath and behave normally, so a voxel world at dusk with volumetric light through the trees is a lighting decision rather than a hack around a template.
It is also where you should spend early time. Deciding the look before you generate a hundred square kilometres of terrain saves you regenerating it, and the look is easier to judge when the world is small enough to walk across.
A starting project for this is the simulation game templates.
Questions
- How big can the world be?
- That is a question about your machine and your chunk strategy rather than about a limit we set, because the game runs locally rather than on a server we pay for.
- Do I need to understand chunk meshing?
- No. Flockbay writes it. You judge the result by how the world looks and how it performs when you play it.
- Can players modify the world at runtime?
- Yes, that is a normal request. Digging, placing and the rebuild that follows are code Flockbay can write into your project.
- Is this a Minecraft clone tool?
- No. A Voxel Sandbox template is there if you want a start, and Flockbay is a general engine layer, which is why a voxel game here can look and behave nothing like the obvious reference if you do not want it to.
- What does it cost?
- The download is free. Free AI to start: Flockbay's AI and your own Claude, ChatGPT, agent or API key are free for your first build; after that, a plan keeps you building.
Free for Windows, macOS and Linux. Generate the world, place the landmarks with intent, dig into it locally.
Download Flockbay free