AI game engine: nobody should write a new engine for this. The engine is Godot.
The phrase AI game engine suggests somebody wrote a new engine with AI in it. That would be a bad idea. The engine here is Godot, and the AI is the layer that builds on it, on Flockbay's AI or your own Claude or ChatGPT. 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.
AppImage, x86_64. Ubuntu 22.04, Debian 12, Fedora 39 or newer.
Intel or AMD Chromebook, with Linux turned on.
Why not a new engine
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.
What the AI layer actually is
Three things. A capability layer that lets an AI read and change what a game is made of (scenes, nodes, scripts, the player controller, characters and props; in 2D, tile cells and sprites), so the game lands as real nodes and resources in the scene tree. Flockbay's AI, which agrees a brief with you, builds the scenes, writes GDScript into your project, and plays the game to check its work. And generation of pictures and sound, 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: A design tool where the design is playable the same day
The world is not AI generated behind your back
Flockbay builds the scenes, but only the ones in a brief you approved. A project is 2D or 3D, settled before anything else exists. In a 3D one: buildings, characters, light, and terrain or water from a Godot plugin. In a flat one: a TileMapLayer, and sprites at an exact position, rotation and scale. Every change after that is one you asked for, held against the brief.
Nothing invents a level from a description while you are not looking. The level is the part you have taste about, so the decisions come to you as questions with a recommendation, and Godot's own editor is there in the Standard and Full views for the calls only your eye can make. A tool that guesses produces something almost right, which is worse than something you chose.
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: Looking for an AI dungeon master, or a game to put one in?
What you install and what it costs
A desktop app for Windows, macOS and Linux. 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 asset generation come over the network. Playing what you built does not.
The download is free. 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.
More on this: An AI alternative to Unity, compared honestly
What bundling Godot actually means
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.
A note on what AI is not doing here
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: approve a brief, get a world and its code built and play-tested; play it, then say what is wrong or move it yourself.
More on this: AI game development tool: where it sits, and what it does not replace
Questions
- Is this a new engine?
- No. The engine is Godot, open source, bundled with the app. Flockbay is the layer on top.
- Does the AI run inside my finished game?
- No. The AI is a building tool. Your game is ordinary Godot code and runs on its own.
- Can I open the project in Godot directly?
- It is a Godot project, and Godot is open source.
- Is it free?
- The download is free. 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.
- Which platforms?
- Windows, macOS (Apple Silicon) and Linux. It is a desktop app.
Free to download for Windows, macOS and Linux. Godot underneath, AI on top.
Download Flockbay free