Skip to content

Who writes the code in Flockbay?

By Eduardo Orellana · Updated

Flockbay's AI writes the code and builds the scenes, from a brief you approve, into your own Godot project on your own disk, and plays the game to check its work. You never have to open a script, but you can read and change every GDScript file and scene yourself, and Godot's own editor is there in the Standard and Full views for changes by hand. Your half is approving the brief and judging what you play. 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.

Download for macOSDownload for WindowsDownload for Linux

The one-line answer

Flockbay's AI writes the code. The app is a desktop app for Windows, macOS and Linux, and the AI inside it is called Flockbay. You say what should happen in plain language, and it writes GDScript into your project, in files on your own disk, in the format Godot uses. You can open, read and change every one of those scripts yourself.

That is the whole of the code question. There is no visual scripting graph to wire up, no menu of behaviours to assemble a game out of, and no point where the tool announces that you have reached the part requiring a language. If you can describe what should happen, that is the input.

It does not stop at the code. From the same brief it builds the world the code runs in, and then it plays the game to find out whether what it made works.

More on this: Best no-code AI game maker: where the ceiling is

The world comes from the brief, and gets checked by playing it

Before anything is built, Flockbay asks about your game one round at a time, each question with a recommendation, and writes a brief: what gets built first, what comes after, and what is not in this version. Nothing is built until you approve it. Ask for something the size of GTA 6 and you get the truth, with real comparable games, and a smaller first version instead of a fake yes.

Then it builds. In a 3D game that means characters, props and a player controller written for this game, with terrain, water and a sky from a Godot plugin or from nodes it writes. In a 2D one it means a TileMapLayer, whose TileSet terrains give the edges and the collision, Parallax2D layers behind it, and sprites at an exact position, rotation and scale. All of it is real Godot data, nodes and resources in the scene tree, not a picture of a world.

Then it play-tests its own work. It runs the game, headless or in a window, sends input events, reads stdout and the debugger, GDScript parse errors included, and captures the viewport. The code and the world get checked together, because a door script is only right if the door is where the script expects it to be.

More on this: What is an AI game maker that writes a real Godot project?

A sentence gets you the valley, your hand gets you the exact one

Describing a landscape in words gets you a landscape. "A ridge running north with a village in the lee of it" is a fine sentence, and the AI will build you that ridge. What a sentence carries badly is the exact line of it: the spot where it should sit two metres lower so the church spire shows over the top.

That is why Godot's own editor is there in the Standard and Full views. They act on the live scene, and Godot's undo takes any change back. Nudge the house, move the tree, repaint the path. Using them is optional, and a game can go from brief to playable without you touching one.

Code mostly goes the other way. "The lantern goes out in the rain and the player has to relight it" is exact in one line and tedious as a sequence of clicks. So the sentence does most of the work, and your hand is there for the one call that is pure taste.

More on this: AI that makes games, described accurately

What non-technical means here

It means you do not have to write the code. It does not mean you cannot judge the result, and that distinction matters more than anything else on this page.

You play the game. You are the one who notices that the jump feels heavy, that the enemy gives up chasing too early, that the door opens but the sound belongs to a different door. Nobody else is in a position to notice, because it is your game and the standard is yours.

So the loop is: approve the brief, play, say what is wrong, play again. Handing work back is the normal state of this tool, not a sign that something failed. A first result that is close and wrong is the expected result, and the fix is a sentence about what is wrong rather than an evening in a text editor, held against the brief you agreed.

The code is visible, not hidden

Flockbay writes into your project, not into a box we keep. The scripts are GDScript files and the scenes are Godot scene files, in a folder on your machine, readable by anyone who reads code, in the format of an engine that is open source and widely known. Inside the app they open in Godot's own editor, in the Script editor, the Scene dock and the Inspector, and you can change any of it.

You are not asked to read them and plenty of people never will. But the option costs nothing to keep open, and it changes what is possible later: you can hand the project to a programmer, put the folder in version control, back it up like anything else, or open it in stock Godot yourself.

A tool that wrote your code somewhere you could not see would be a tool that owned your game. This one does not, and that is worth more the more time you put in.

Why not a menu of behaviours instead

The usual alternatives are a menu or a graph. A menu ships a fixed set of behaviours and you assemble a game from them, which is quick to start and has a ceiling shaped exactly like the menu. A graph of nodes and connections composes much better, and it is programming with a different notation, so it hands back the conceptual work you were trying to avoid.

Writing real script has neither problem. There is no list to run out of, and there is no notation to learn, because the thing you supply is a description of what should happen.

The cost is that written code is written rather than assembled, so getting it right sometimes takes a round or two. That is the trade, and it is why the AI plays its own work before you do, and why the judging half of the job matters as much as it does.

More on this: AI game maker comparison: the five axes that matter

What Flockbay will not do for you

It will not build before you agree what it is building. There is no path where one sentence quietly becomes a starter world behind your back. The brief comes first, nothing is built until you approve it, and every later change is held against it.

It will not decide whether the game is good. It plays its build to check that it runs and that input does what the brief says, but it has no opinion worth having about whether your village feels lonely enough or your combat is satisfying, and a tool that claims otherwise is guessing on your behalf.

And it will not work without a connection. The AI runs over the network, along with asset generation and your account, so building needs internet. The game you have built runs locally on the copy of Godot inside the app and needs nothing.

Questions

Does Flockbay write the whole game?
It writes the code and builds the world, from a brief you approve, and plays the result to check that it runs. Judging whether it is right is yours, and any part can be changed by hand in the Godot editor.
What language does it write?
GDScript, which is Godot's own language, in ordinary script files inside your project.
Do I have to read the code?
No. Most people building here never open a script. Every script and scene is readable and editable in the Godot editor if you want it, which is a different thing from being required.
What do I do when the result is wrong?
Play it, say what is wrong, and ask again, or make the one change yourself by hand in Godot's own editor. That is the intended loop rather than a failure of it.
Is Flockbay a separate product?
No. It is the AI inside the Flockbay app, for Windows, macOS and Linux. It is not a plugin for another engine and it is not sold on its own.
Can I use my own AI instead?
Yes, free for your first build and on a plan after it: Flockbay runs on your own Claude or ChatGPT sign-in (a free ChatGPT account works) or an API key, and your own agent, such as Claude Code, Codex or Cursor, can build in the app over MCP. Your agent runs on your own machine with your own model and credentials, and Flockbay stays available alongside it.

Free to download for Windows, macOS and Linux, and the AI is free to start.

Download Flockbay free