Skip to content

A no-code game engine that is still a real engine

By Eduardo Orellana · Updated

Most tools called no-code make you trade the engine for the convenience. Flockbay does not: the game you build is a real Godot project, running locally on your own machine, and you never open a script to make it. 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

What no-code usually costs you

The phrase "no-code game engine" almost always describes a closed system. You get a visual editor, a fixed set of behaviours, and a game that only exists inside the tool that made it. That is a reasonable trade for a weekend prototype, and a bad one the moment your game needs something the menu does not contain. The ceiling is not a difficulty curve you can climb. It is a wall.

The other version of the trade is the browser tool. Your project lives on someone else's server, the editor runs at whatever framerate the tab allows, and the game you export is a web build with the performance that implies. Again: fine for a prototype, and a real constraint on anything you intend people to play for hours.

Flockbay takes neither trade. The engine underneath is Godot, which is open source and which serious games ship on. Your project is a Godot project. What sits on top is a layer that lets an AI build the scenes and write the code from a brief you approved, with Godot's own editor in your hands whenever you want it, and none of that removes the engine you are standing on.

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

Flockbay does the building, and the judging stays with you

It starts with a brief, not a build. Flockbay asks what you want one round at a time, each question with a recommendation, and writes down what gets built first, what comes after and what is not in this version. Nothing is built until you approve it. That is the answer to the usual problem with describing a game to a machine, which is that you get its guess instead of your game.

Then it builds the scenes, as real Godot data: nodes and resources in the scene tree, not a picture of a world. In a 3D game that means a player controller, characters and props, with terrain, water, a sky or weather from a Godot plugin when the game needs them. In a 2D game none of those plugins appear, because they mean nothing in a flat world; it gets painted tile cells and sprites instead. Both are first-class rather than a main case and a mode.

A flat world is a TileMapLayer, Parallax2D layers behind it, and sprites at an exact position, rotation and scale. The terrains of its TileSet give the edges and the collision, so the ground is walkable the moment it is painted. And most of the Catalogue is already sprites, the library Flockbay builds from: 55,073 of 60,648 objects.

It also writes the code. You say what should happen and it writes the GDScript that makes it happen, inside your project, where you can open it in the Script editor and change it. Then it play-tests its own work: it runs the game, sends input events, reads stdout and the debugger, GDScript parse errors included, and captures the viewport. The first time you press Play is not the first time the game has run.

Then it is your turn. You play it and say what is wrong, and it changes it, held against the brief you approved. When the call is pure taste, like exactly where a ledge sits, Godot's own editor is there in the Standard and Full views, so you can make that one change by hand, and Godot's undo takes it back. A sentence gets you a layout; your hand can get you the exact layout. You never have to touch those buttons.

That loop — you judge, it revises — is the normal way to work here, not a failure mode. Not writing the code does not mean not having an opinion about the game. It means the opinion is the part you supply.

More on this: AI battle royale maker: read the hard part first

The game runs on your machine

Flockbay is a desktop application for Windows, macOS and Linux, and it ships with Godot inside it. When you press play, the game runs locally, at your machine's framerate, with your machine's memory. There is no streaming, no render queue, and no tab.

This matters more than it sounds. A world with real terrain, weather and a few hundred simulated characters is not a thing a browser tool will run smoothly, which is why browser tools quietly steer you toward the smallest version of whatever you asked for. Running locally is what makes an open world a reasonable thing to attempt — and it is also what keeps the gap between changing a painted tile and seeing it near zero.

Building does need an internet connection. The chat, asset generation and your account all come over the network, so this is not an offline tool. The distinction worth holding is that building needs the connection and playing does not.

More on this: AI bullet hell maker: patterns are maths, and maths is code

Who this is actually for

People who want to make a specific game, developers or not, on the free hosted AI or their own Claude or ChatGPT. Not people who want to click through a template and have something that resembles a game by the end of the afternoon — there are faster tools for that, and they are honest about what they are.

The work is real. You will spend time on the brief and on your world, you will play it and dislike parts of it, and you will send it back. What you will not do is learn GDScript first, or spend a week wiring a state machine before anything moves.

More on this: Make an endless runner where the tuning is the game

Questions

Is Flockbay actually free?
The download is free, and so are the editor, your own art, playtesting and export. 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.
Do I need to know how to code?
No. Flockbay builds the world and writes the code from a brief you approve, and you play it and judge the result. You can read the code if you want to — it is a normal Godot project — but nothing requires it.
Does it run in the browser?
No. Flockbay is a desktop app for Windows, macOS and Linux, and your game runs locally on the copy of Godot that ships with it. Building needs an internet connection; playing what you built does not.
What engine is underneath?
Godot, which is open source. Your project is a Godot project rather than a file only this tool can open.
Can I make a 3D open world?
Yes. In a 3D project, populated worlds, with terrain, water and weather from Godot plugins, are the intended shape rather than an advanced feature you graduate to. What is not true is that 3D is the only case it is built for.
Can I make a 2D game with it?
Yes. Say the game is 2D and the tools follow: Flockbay paints a TileMapLayer instead of a 3D terrain, adds Parallax2D layers behind it and places sprites on top, and side-on or top-down comes from whether the player controller it writes has gravity, not from a template you picked. In Godot's own editor, the TileMap panel and the 2D view are there for the cell or the sprite you want to change yourself.

Flockbay is free to download for Windows, macOS and Linux.

Download Flockbay free