Skip to content

A 3D game generator, and what actually gets generated

By Eduardo Orellana · Updated

Nothing generates a finished 3D game from a sentence. Flockbay agrees a brief with you first, then generates a first playable: the scenes, the player controller and props, terrain, water or a sky from a Godot plugin when the game needs one, and the GDScript that makes them behave. It plays the game to check its work, you play it to judge it, and any part can be reshaped by hand in the Godot editor. 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

Where the word "generator" stops being true

The promise implied by "3D game generator" is a text box, a sentence, and a game. It is worth saying plainly that no tool does that in a way that survives contact with actually playing the result. What comes out of a one-shot generation is a demo shaped like a game: it moves, it has a floor, and it has nothing you would return to.

The reason is not that models are not clever enough. It is that a game is a hundred small decisions about feel, pacing and space, and a sentence does not contain them. Anything not in the sentence gets invented, and invented decisions are usually the generic ones.

So Flockbay does not generate from the sentence. It generates from a brief, and the brief is where the missing decisions come from.

More on this: AI RPG generator: what generation is good for, and what it is not

The brief supplies what the sentence left out

Before anything is built, Flockbay asks questions one round at a time, each with a recommendation and a line of why. Is the player on foot or in a vehicle? Is the world one valley or a map you cross? What does the player do in the first minute? Then it writes the brief: what gets built first, what comes after, and what is not in this version.

Nothing is generated until you approve it. If the ask is out of reach ("an open world like the big studio ones"), you hear that plainly, with real comparable games, and get a smaller first version that is actually buildable instead of a starter world dressed up as a yes.

The world is generated as Godot data, not as a picture

Then Flockbay builds the first playable: the scenes and nodes, the player controller in GDScript, characters and props, with terrain, water or a sky from a Godot plugin when the game calls for one. All of it lands as nodes and resources in the scene tree of an ordinary Godot project, the same as if a level designer had built it.

It also writes the GDScript and the scenes. Movement, cameras, interaction, inventory, enemy behaviour, save and load, the state machine that keeps a character from sprinting and crouching at once. "The player should mantle a ledge under waist height" has one correct behaviour and a fiddly implementation, and generating the fiddly implementation is a good use of the technology.

There is more generation where it helps: pictures and sound, terrain through a Godot plugin, and objects from a library of ready-made models. 3D models are generated only on your own Tripo key, if you add one.

More on this: Can AI make a game?

It plays the game before you do, and then you judge it

A generator that never plays its output is guessing. Flockbay runs the game, headless or in a window, sends input events, reads stdout and the debugger, GDScript parse errors included, and captures the viewport to see what it built. Most of the obvious breakage is gone before you press play.

What is left is the part only you can judge. You are not asked to read the script. You are asked to play it and say whether it is right. Saying the mantle feels sticky, or that the valley should be tighter, is the normal loop, not a failure, and Flockbay changes it against the brief you approved.

Some calls are pure taste: exactly where the rock sits, which way the path bends. For those, Godot's own editor is there in the Standard and Full views, acting on the live scene, and Godot's undo takes any change back. A sentence gets you a layout. Your hand can get you the exact layout.

More on this: Can AI make a 3D game?

It runs on your machine

Flockbay is a desktop app for Windows, macOS and Linux with Godot bundled inside it. Press play and the 3D game runs locally, at your machine's framerate. No streaming, no render queue, no browser.

That is what makes a real 3D world a reasonable thing to attempt. Terrain with actual draw distance, weather, and a populated scene are not things a hosted preview handles gracefully, which is why hosted tools tend to keep worlds small and flat.

Building does need an internet connection, since the AI and generation come over the network. Playing what you built does not.

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

What to expect from your first session

A brief you approved, a first playable world Flockbay built and tested, a character that moves the way you asked, and a list of things that feel wrong. That is a good first session. The second one is where you fix them.

What you will not get is a finished game from a prompt, and any tool telling you otherwise is describing a demo.

Why one-shot generation keeps disappointing people

It is worth understanding the failure rather than just being warned about it, because the same shape will keep appearing in every tool that promises it. A prompt is a compression of an idea, and the decompression has to invent everything the prompt left out. Invented decisions are drawn from the average of everything the model has seen, and the average game is not a game anyone wants.

So the output is coherent and generic in exactly the same proportion. The terrain is plausible. The buildings are placed at plausible intervals. Nothing is anywhere for a reason, and a player feels that within a minute of walking, even if they could not name what is wrong.

The brief fixes this at the root rather than papering over it. The decisions the prompt left out are asked for instead of invented, so the world is built from your answers rather than from the average. What remains is taste you can only find by playing, and that stays yours: say what is wrong, or make the one change by hand.

This is also why there is no library of genre templates here. A template is a frozen set of somebody else's decisions, which is the same problem arriving by a different route.

Questions

Can it generate a whole 3D game from one description?
No, and neither can anything else in a way that holds up when you play it. Flockbay agrees a brief with you, generates the world and the code for a first playable, and plays it to check its work. You play it and say what is wrong, and it changes it.
What engine does the generated code target?
Godot. The world is nodes and resources and the code is GDScript, in a normal Godot project on your disk.
Is there a browser version?
No. It is a desktop app for Windows, macOS and Linux, and the game runs locally.
Do I need to know 3D modelling?
No. Flockbay builds from a library of ready-made objects or Godot's own shapes, and uses your own files when you have them. 3D models are generated only if you add your own Tripo key.
What does it cost?
Free to download. 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. Flockbay builds from a library of ready-made objects, or with Godot's own shapes.

Free to download for Windows, macOS and Linux.

Download Flockbay free