Skip to content

AI 3D game generator: two kinds of generation, and the verdict is yours

By Eduardo Orellana · Updated

There are two generators in a 3D game tool: one that makes material, and one that makes behaviour. Flockbay runs both, composes the world from your brief, and leaves the verdict to you, because your eye decides whether a world is worth walking through. 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 A 3D game maker built on Godot, on free AI to start or your own Claude or ChatGPT.

AppImage, x86_64. Ubuntu 22.04, Debian 12, Fedora 39 or newer.

Intel or AMD Chromebook, with Linux turned on.

Download for macOSDownload for WindowsDownload for Linux

Material generation

Terrain, water, weather, props, characters. These are raw material, and generating raw material is genuinely useful. A terrain plugin from the Plugins panel can take a heightmap and give you a landscape with the geology already in it. Water is a surface the terrain cuts into, so the coastline follows the land. A sky is a WorldEnvironment rather than a skybox image, and rain is particles.

What makes generated material useful is that it comes in as something that can still move: nodes and resources in the scene tree, not a picture of a world. A generated hill nobody can reshape is a picture. A generated hill that Flockbay can push around when you ask, or you can push around in the editor, is a starting point.

Assets can also come from the web or from you. The tool tells you which route it took rather than blurring the distinction, because you need to know what you are actually holding.

More on this: An asset generator attached to the game the assets are for

Behaviour generation

Flockbay writes GDScript into your project. Third person camera with collision handling. A character that vaults, swims and climbs. Enemies that lose track of you and search. An inventory that persists. Time of day driving what NPCs do.

This is where generation has the clearest win, because these are specified problems. The gap between "the camera should swing round obstacles rather than clipping them" and a working implementation is entirely mechanical, and mechanical is what a model is for.

You are not expected to read it. You are expected to play it and say what is wrong. That handback is the loop, not an exception to it.

Composition is not rolled at random, and the verdict is yours

Composition. Where the tower is, what you see when you round the corner, how far apart the two villages are, which way the road bends. It is the reason one level is memorable and another is filler, so Flockbay does not leave it to a random seed. It places each thing from the brief you approved, at an exact position in the scene, then plays the result to check it.

Whether it works is spatial judgement, not a technical skill, and you already have it. Play it and say what is wrong: "the second village is too close, I can see it from the first". When the call is pure taste, Godot's own editor is right there, so you can make that change by hand and Godot's undo takes it back. A sentence gets you a valley; your hand can get you the exact valley.

There is no library of genre templates to pick a world from either. A template only fits the game somebody already made, and you are not making that one.

It runs on your machine

Flockbay is a desktop application for Windows, macOS and Linux with Godot bundled inside. Press play and the 3D game runs locally, using your GPU. There is no streaming, no render queue and no browser preview.

That is what makes the ambitious version viable. A world with weather, draw distance and a few hundred moving things is not something a hosted preview handles, which is why hosted tools keep worlds small.

Generating needs a connection — code and assets both come over the network. Playing what you built does not.

More on this: AI NPC generator: an NPC is behaviour, not a portrait

Working with generated material rather than accepting it

The useful mental model is that generation produces stock, not results. A generated valley is a valley nobody chose, in the same way that a stock photo is a photograph nobody took of anything in particular. It is a fine starting point and a poor finishing point.

So the workflow that works is to generate broadly and then edit hard. Terrain comes in from a real place, then the pass gets cut through it. Buildings go where a person would have built them, which is almost never on an even grid. Flockbay does that edit pass from the brief and from your notes after each playtest, and any part of it can be done by your own hand.

The moment the editing starts is the moment the world stops being generic, and it happens fast. Ten minutes of deliberate placement will do more for a scene than any amount of better generation, whether the placing is done by a sentence or by your hand.

This is also why nothing here is locked. Terrain remains sculptable in its plugin, generated assets remain movable, and no part of the world arrives as a finished thing you are meant to accept.

More on this: An AI dungeon generator that hands you a dungeon you can edit

What it will refuse to fake

If a generation fails, the tool tells you it failed and what happened. It does not substitute something that looks similar and let you find out later that a texture is missing or a mesh never arrived.

That sounds like a low bar and it is not one every tool clears, because a graceful-looking failure demos better than an honest one. It is worth more to you to know, particularly when you are building on top of the result.

The same applies to code. If a request cannot be satisfied, you get told what happened rather than something that compiles and quietly does nothing. Knowing where you actually are is the only way to work at any speed.

More on this: Make a first person game where the world holds up close

Questions

Can it generate a whole 3D game from a description?
Not in one prompt. Flockbay asks questions first and writes a brief: what gets built first, what comes after, what is not in this version. Once you approve it, Flockbay builds that first version, world and code, and plays it. You judge the result and say what changes.
Where does terrain come from?
From a terrain plugin you install from the Plugins panel, such as Terrain3D, from meshes the AI builds, or from flat ground. Flockbay does not download elevation data; a heightmap of your own goes in through the plugin, and its own sculpt and paint tools are there in the editor if you want to reshape it yourself.
Do I need to be a 3D artist?
No. Flockbay builds from a library of ready-made objects or Godot's own shapes, or uses your own files, and 3D models are generated on your own Tripo key. Plain geometry is a legitimate look as well as a legitimate placeholder.
Is anything rendered remotely?
No. The game runs locally on the copy of Godot bundled with the app, using your own GPU.
Pricing?
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.
Can I mix generated and hand-made assets?
Yes, and most projects do. Generated terrain with your own buildings, or library props Flockbay placed and you nudged, are both normal. The tool records which is which.

Free to download for Windows, macOS and Linux.

Download Flockbay free