AI 3D game maker for people who want scale

By Eduardo Orellana · Updated

Flockbay is free on your own Claude or ChatGPT plan. Claude Pro or Max, or ChatGPT Plus or higher, builds a real Godot project in the Godot editor. Claude Free and ChatGPT Free do not run here. More models are optional, a credit reload at API prices. Windows today. The engine is the official Godot release. Most AI game tools are small on purpose, because they run in a tab. Flockbay is a desktop app with Godot inside it, which is why a 3D world here can have a horizon.

Ambition is a hardware question first

The reason most AI game tools produce small flat scenes is not the AI. It is where the game runs. A hosted preview has to fit inside a tab and a hosting budget, and the honest consequence is short draw distances, few objects and simple light.

Flockbay puts the game on your machine. Godot ships inside the app, so pressing play launches your world natively with your GPU behind it. The ceiling is your hardware, and your hardware is a lot more generous than a tab.

That single decision is what makes terrain, weather, water and a populated world the ordinary case rather than the thing that makes the editor stutter.

More on this: AI survival game maker with real terrain and weather

Where the AI sits

Flockbay writes GDScript inside your project. That covers the character controller, the camera, interaction, inventory, quests, enemy behaviour, save and load, and every unglamorous system that stands between a walkable scene and a game.

You ask in plain language. You get something you can play. If it is wrong you say what is wrong and it changes. There is nothing in that loop that requires you to read code, and nothing in it that removes your judgement about the result.

The AI is used at build time, writing the code that ships in your project. What runs when you play is your game.

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

Where you sit

You build the world with your hands. Terrain, water, weather, buildings, props, characters, routes. The builder behaves like a level editor because that is the right instrument for spatial decisions.

And you play, and you have opinions. The valley is too open. You cannot see the tower from the road and you should be able to. The night is too dark to navigate. All of those are worth acting on and none of them require any technical vocabulary.

None of this requires you to learn a vocabulary first. You do not need to know what a navmesh is to say that the villagers walk through the wall, and knowing the word would not make your report any more useful.

More on this: An AI tower defense maker where the numbers are yours to set

What it will not do

It will not hand you a finished 3D game from a sentence. It will not offer a menu of genre templates, because a template only works for a game that already exists.

And it will not pretend. If a thing did not work, the tool says what happened rather than producing something that looks like success. That is worth more to you than a demo that falls apart in the second session.

It will not size a list for you either. If your request depends on something you have not specified, it asks rather than inventing a plausible default, because a default you did not choose is a decision made on your behalf and hidden from you.

Practicalities

A desktop app for Windows, free to download, with a free plan that covers the whole world builder. Flockbay is free on your own AI: your Claude or ChatGPT plan, your own agent, or an API key. Flockbay builds from a library of ready-made objects, or with Godot's own shapes.

Building needs an internet connection. The chat, asset generation and world data come over the network. Playing what you have built does not.

More on this: AI game prototyping, on an engine the prototype can survive on

The failure mode to watch for

The common way a 3D project goes wrong here is not technical. It is building a beautiful world that has nothing to do. Terrain is satisfying to make, the feedback is immediate, and it is very easy to spend three weeks on landscape and never ask what the player is supposed to want.

A useful discipline is to put the reason in early, even badly. Something to reach, something chasing you, something to collect. It can be a grey box on a hill. The point is that the moment there is a goal, you start judging the terrain by whether it makes the journey interesting rather than by whether it looks nice from the sky.

Almost every good design decision in an open world comes from that shift. A ridge is not there to look like a ridge, it is there so you cannot see what is behind it.

Nothing in the tool enforces this and nothing will stop you making a landscape for its own sake, which is also a completely legitimate thing to do. It is just worth knowing which one you are doing.

Questions

How large can a 3D world get?
Large enough for terrain, weather and hundreds of moving things. The limit is your machine, because the game runs locally.
Is the AI running while I play?
No. Flockbay writes the code at build time. What ships in your project is ordinary GDScript.
Can I use my own 3D models?
Yes. Your own assets, generated ones, sourced ones, or plain geometry all work.
Windows?
Both. There is no browser version.
Do I need to know Godot?
No. It is useful if you already do, because the project is a normal Godot project, but nothing requires it.
What if I have never used a 3D tool before?
The builder is closer to arranging a room than to a modelling package. The first hour is terrain and walking around, which is enough to start having opinions, and opinions are the input the whole loop runs on.