How to make a 3D game when you build on your own Claude or ChatGPT plan
To make a 3D game on your own Claude or ChatGPT plan, connect it to Flockbay: from a brief you approve, it builds the 3D world and writes the GDScript in a real Godot 4 project, then plays the game to check it. You keep the verdict. 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.
Why most 3D attempts stop
Ask anyone who opened a big engine, followed a tutorial, and never opened it again what happened, and you get one of two stories. Either they spent three weeks on character movement and never got to the game, or they got movement working and then stared at an empty grey plane with no idea how to make a world.
Both are real problems. Movement code is a solved problem that you should not be re-solving by hand. A world is not a solved problem — it is your game, and nobody can generate your taste for you. But most of a world is work rather than taste: sculpting the terrain, laying the river, planting the hillside. The taste is in a handful of calls, like where the path bends and what you see when you spawn.
So the code and the work of the world stop being your job, and the taste calls become it.
The world is built from a brief, as real Godot data
First comes a brief. Flockbay asks what you are making, one round of questions at a time with a recommendation each, and writes down what gets built first, what comes after and what is not in this version. Nothing is built until you approve it. Then it builds the scenes: the player controller, characters and props, with terrain, water, sky or weather from a Godot plugin when the game calls for one, all as real nodes and resources in the Godot scene tree.
Terrain comes from a Godot terrain plugin you install from the Plugins panel, such as Terrain3D, with its own sculpt and paint tools. Water and a sky come from a plugin or from nodes Flockbay writes: a water surface, a WorldEnvironment with a sky and a sun. Set them up early, because a 3D game that is worth walking around needs them early, not as a polish pass.
Objects come from a few places: a library of ready-made objects, generated on your own Tripo key, brought in from your own files, or built directly from Godot's own shapes when that is the honest way to get you playing. You will be told which happened.
Godot's own editor is there in the Standard and Full views. You never need them. When a call is pure taste, nudge the crate or move the tree yourself, and Godot's undo takes it back. A sentence gets you a layout; your hand can get you the exact layout.
More on this: Can AI make a 3D game?
Getting the code without writing it
Flockbay writes GDScript inside your project. You describe behaviour in plain language — the door opens when you have the key, the enemy loses interest after ten seconds, falling in the water resets you to the shore — and the code appears in your project files.
Flockbay plays it first: it runs the game, sends input events, reads the debugger and captures the viewport, so a door that never opens is caught before you see it. You judge what is left by playing it. This is the part people expect to be a compromise and it is not: not writing the code does not mean not having standards about the game. You will reject things. That is the loop working.
Because the output is ordinary GDScript in an ordinary Godot project, nothing about it is locked to this tool. If you ever want to look, or hand it to someone who reads code, it is there.
More on this: Idea to game, without the part in between
It runs on your machine, which is the point
Flockbay is a desktop app for Windows, macOS and Linux with Godot bundled inside it. Press play and the game runs locally, using your GPU. Nothing streams and nothing renders in a data centre.
For 3D specifically this is the difference between a real scene and a toy one. Terrain, foliage, dynamic weather, and a population of characters is a normal local workload and an impossible browser workload, which is why browser tools nudge you toward small, flat, empty scenes without ever telling you why.
Building requires an internet connection, because the AI and asset generation come over the network. Once built, the game plays without one.
More on this: Make a game with AI without giving up the game
What a sensible first project looks like
Not an open world. One valley, or one building, or one street. Something with a shape you can hold in your head and finish.
Get a character walking in it. Add one thing to find and one reason to look for it. Play it repeatedly and fix the things that annoy you — the camera, the walk speed, the fact that the interesting part is behind you when you spawn. That list of annoyances is your design document.
Scale comes after, and it comes cheaply, because placing the hundredth building is no harder than placing the first.
The world settings worth understanding early
Terrain scale. It is very easy to build a valley that looks right from above and takes four minutes to walk across. Getting a feel for how large a space actually is when you are inside it, at walking speed, is the single most useful calibration you can do on day one.
Fog and haze. These control how far the player can see, and they are the strongest lever you have over the mood of an outdoor scene. They also hide the edge of your world, which is what stops a finite terrain from feeling like a diorama.
Time of day. A world at noon is flat and a world in late afternoon has shape, because long shadows describe the terrain. If a scene looks dull, the light is usually the reason before the geometry is.
More on this: Making a game from a picture: what a reference image can and cannot do
Questions
- Do I need to model anything in Blender first?
- No. Flockbay builds the scenes, with terrain, water or a sky from a Godot plugin when needed, and objects come from a library of ready-made ones, from Godot's own shapes, or from your own Tripo key. You can bring in your own models if you have them.
- What engine is it?
- Godot 4.6+. The official Godot, open source, ships with the app, not a fork, and new projects are made on it. Your project is a Godot project, and a project on an older Godot 4, or on Godot 3, can stay on your own Godot of that version, and Flockbay says which of its features that engine cannot run.
- How good does my computer need to be?
- Good enough to play the game you are making, since it runs locally. There is no fixed requirement because it depends entirely on the world you build.
- Can I do this entirely in a browser?
- No. Flockbay is downloaded and installed on Windows, macOS or Linux. That is what makes local 3D performance possible.
- What does it cost?
- Free to download, and building is free to start. 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 to download for Windows, macOS and Linux.
Download Flockbay free