# A 3D game maker built on Godot, on free AI to start or your own Claude or ChatGPT

Flockbay is a 3D game maker built on Godot: its AI builds the scenes and writes the code from your description, on Flockbay's AI or your own Claude or ChatGPT. It sets up the scenes, the player controller and the props, then plays the game to check its work. Godot's own 3D editor is there in the Standard and Full views, so you can place or move anything by hand. It installs on your computer, and the game runs locally on Godot. 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.

Source: https://flockbay.com/3d-game-maker/ · Updated 2026-11-04

## Nothing here defaults to 3D

A new game starts with one sentence: what you want to make. Flockbay reads it and says whether it is a 2D or a 3D game, and nothing is created until you confirm. Both are first-class, neither is a mode of the other, and this page is about the 3D one.

That matters because plenty of beginner tools do 3D as a courtesy. You get a grey floor, a capsule that walks, and a fog wall about two hundred metres out because the tool cannot afford anything further.

Flockbay starts from the opposite assumption: a space with distance in it, full of props and characters, is the ordinary case, not an advanced feature you unlock. Terrain, sky and water come from a Godot plugin in the Plugins panel (Godot's Asset Library), or from nodes and scripts the AI writes. [The engine underneath](/what-is-godot/) is Godot, running as a bundled copy on your own machine, so the budget for what a scene can contain is your hardware rather than a hosting bill.

That means the questions you get to ask are the interesting ones. How big should the valley be. Where does the river go. What is over the ridge. Not: will this run.

## Flockbay builds the world, and your hand is there for the exact spot

Before it builds anything, Flockbay asks those questions, one round at a time, each with a recommendation, and writes a brief: what gets built first, what comes after, what is not in this version. Once you approve it, Flockbay builds: it sets up the scenes, writes the player controller, places buildings, props and characters, adds terrain or a sky from a Godot plugin when the game needs one, and then walks through it to see whether it reads. It all lands as nodes and resources in the scene tree, not as a picture of a world.

[Describing a landscape in a sentence](/text-to-3d-game/) gets you a landscape. It does not always get you the exact one in your head, because placement is taste. So Godot's own editor is there in the Standard and Full views. Move the tree, swap a model, nudge a building, and Godot's undo takes it back if you change your mind. A hill on a terrain plugin is shaped with that plugin's own tools.

It also means you are never blocked on knowing the right words. You do not need to know what a heightmap is to ask for a hill.

## Flockbay writes the code

Everything that makes the world behave is code, and code is the part you do not have to do. Flockbay writes GDScript directly in your project: the player controller, the camera, interaction, inventory, doors, quests, whatever the game needs. Then it runs the game, sends input events and reads the debugger to check the change before you see it.

You ask in plain language and you get a change you can play. If the sprint is too fast or the camera clips the wall behind you, say so. Revising is the normal rhythm of the work.

Because [the code lives in your project](/answers/can-i-edit-the-code-myself/) rather than behind an API, the project stays a Godot project. Nothing about it depends on this app continuing to exist.

## Local play, networked building

Press play and the game launches on your machine, using the copy of Godot that ships with the app. Your framerate is your machine's framerate. There is no streaming and nothing rendered anywhere but here.

Building is [the part that needs an internet connection](/answers/does-flockbay-work-offline/). The chat and asset generation come over the network, so building needs a connection. Playing a game you already built does not need the connection.

There is also nothing stopping you making the world small. A single island, a mountain pass, one village. Scale is a choice about the game rather than a demonstration of what the tool can do, and small worlds that are dense usually beat large ones that are empty.

## What it does not do

It does not hand you a finished game from a description: it agrees a brief with you first and builds the first version of it. For a head start, New from template on Home opens one of the game templates as an ordinary Godot project you then change.

And it does not decide for you [whether the result is good](/blog/how-to-judge-a-game-you-did-not-code/). You play it. You say. That is the part of the job that was always yours.

## What a first week usually contains

Day one is the brief and the first build: the ground, and a player controller who can walk on it. That sounds small and it is the correct place to start, because until you can walk around your world you cannot tell anything about it. Plenty of first landscapes turn out too flat or too big within minutes of walking them.

The middle of the week is the loop: play, say what is wrong, play again. [A camera that is wrong](/blog/the-challenge-of-cameras/). A run speed that makes the valley feel small. A hill you have to go round when you wanted to go over. Each of these is a sentence to fix, or one drag in the editor, and each of them changes how the world reads.

By the end you have a place that works and a list of what it needs. Buildings, a reason to go somewhere, something that happens. That list is the actual game design, and getting to it in a week rather than a season is what the tool is for.

Nothing about that week requires reading code, and all of it requires having opinions about a place. If you enjoy the second thing, this works. If you were hoping to skip both, it will not.

## Questions

### Do I need to model anything in Blender first?

No. Flockbay builds from a library of ready-made objects or Godot's own shapes, and bringing your own models works too if you have them. 3D models are generated only on your own Tripo key, if you add one.

### How big can a world be?

Large enough that a landscape and a populated scene are normal, with terrain, sky and water from Godot plugins. The practical limit is your own machine, since the game runs locally.

### Is it a browser tool?

No. It is a desktop app for Windows, macOS and Linux that you install.

### What happens if I want to hire a programmer later?

They open the Godot project and read the GDScript. There is nothing proprietary to unpick.

### What is free?

All of the building by hand: the editor, your own textures, props, sounds and rigs, plus play and playtesting. 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.

### How long before I have something playable?

A player controller walking on the ground Flockbay built from your brief is a first session. A game with a reason to be there takes as long as the design does, which is the honest answer and the same answer for any tool.

Download Flockbay free: Free to download for Windows, macOS and Linux. https://flockbay.com/

Related: [AI 3D game maker](/ai-3d-game-maker/), [3D game generator](/3d-game-generator/), [Free 3D game maker](/free-3d-game-maker/), [Make a 3D game](/make-a-3d-game/), [3D game maker online](/3d-game-maker-online/), [Flockbay is not a VR game maker](/vr-game-maker/)
