Nobody should write a new engine for this. The engine is Godot.

An engine is twenty years of rendering, physics, audio, animation, import pipelines and platform export. Anybody starting one from scratch in order to attach an AI to it would spend a decade catching up to where open source already is, and the AI would not be any better for it.

Godot already exists, is open source, and ships real games. So the sensible thing is to build on it rather than beside it. Flockbay bundles Godot and adds the layer on top.

The practical consequence is the one worth caring about: your project is a Godot project. Not an export from a proprietary format. Not a document only this app can open. A Godot project on your disk, which Godot opens.

More on this: AI game maker vs game engine: the difference

Two things. Flockbay, which writes GDScript into your project when you describe what should happen. And generation of assets and world data, which happens inside the project rather than as files you import afterwards.

That is it. There is no AI in the render loop, no model deciding physics, nothing running while your game is being played. The AI is a building tool, not a runtime.

This matters for what your game becomes. A game whose behaviour depends on a model responding at runtime is a game that needs a network connection and a bill to run. A game whose code was written by a model is just a game.

More on this: Building with Flockbay needs a connection. Playing what you built does not.

The other half of the app is a builder, and it is where you construct the world with your hands. A project is 2D or 3D, picked before anything else exists. In a 3D one: terrain, water, weather, buildings, characters, light. In a flat one: ground you paint as tiles, and sprites you put at an exact position, turn and size. Placed by you, either way.

There is no path where you describe a level and something invents it while you are not looking. That is deliberate. The world is the part you have taste about, and a tool that guesses at it produces something almost right, which is worse than something you made.

You are not expected to write code, and you are expected to have opinions. Those are compatible. Playing your own game and saying it is wrong is the loop the whole thing is built around.

More on this: Where this tool sits, and what it does not replace

A desktop app for Windows. It runs your game locally on the bundled Godot, at your machine's framerate. No streaming, no browser preview.

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

The download is free and so is the 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. There is no team or enterprise tier.

More on this: An AI alternative to Unity, compared honestly

The copy of Godot that ships inside the app is the one your game runs on when you press play. There is no separate preview renderer and no approximation, so what you see while building is what the game is.

It also means you are not installing and configuring an engine yourself, which is a small thing for an experienced developer and a real barrier for everyone else.

And because the project is standard, an experienced developer can open it in their own Godot install and work on it there. Neither of those two people has to compromise for the other, which is unusual.

It is not deciding your design. It is not picking a genre for you from a list, because there is no list. It is not editing your world while you are elsewhere.

Those constraints are the reason the output can be trusted. A tool that changes things you did not ask about is a tool you have to audit, and auditing is the thing you were trying to avoid.

What you get instead is narrower and more useful: describe behaviour, get code; place the world, see the world. Two clear halves, and no third path where something happens quietly in between.