A no-code game maker where the code still gets written

The first kind removes code from the product. There is a menu of behaviours, you pick from it, and anything not on the menu cannot happen. Nothing is written because nothing can be written. These tools are quick to start and they end abruptly, usually on the day you want a specific thing.

The second kind removes code from your job. The code still exists, it still runs, it is still the thing that makes your game work. You are simply not the one typing it. Flockbay is the second kind, and the difference shows up about three weeks in, when the thing you want is not a checkbox anywhere.

It is worth knowing which one you are downloading before you start, because the ceiling of the first kind is invisible until you hit it.

More on this: A platformer maker with no ceiling on it

Flockbay builds the world, but not before it knows which one. It asks what you are making one round at a time, each question with a recommendation, and writes a brief: what gets built first, what comes after, what is not in this version. Nothing is built until you approve it. Then, in a 3D game, it lays out terrain, water, sky, weather, plants, props, characters and the player controller. In a 2D game it paints tile ground and puts down sprites, of which the Catalogue it builds from has plenty: 55,073 of its 60,648 objects are flat pictures.

All of that is real Godot data, nodes and resources in the scene tree, and flat ground shows why that matters. The tiles, the edges and the collision all fall out of which cells are covered, so a ledge is the ledge a character stands on the moment it is painted, and whether ground stops a walker at all is declared per material rather than chosen from a menu — which is why a top-down path and a platformer's solid block are painted with identical strokes.

Flockbay writes the code too. You say what should happen when the player walks into the room, and it writes the GDScript that does it, in your project, where you can read it if you want to. Most people do not want to, and nothing requires it. Before you see the change, it runs the game itself, sends input events and reads the debugger for errors.

Then you play it. You decide whether it is right. If it is not, you say what is wrong and it goes again, held against the brief. Handing the work back is the normal loop here, not a sign that something failed.

Some calls are too small to be worth a sentence. A tree one step to the left, a path that should curve the other way. For those the same world tools are buttons around the Godot editor's own 3D and 2D view, so you can drag the tree yourself, and Godot's undo takes it back if you change your mind. You never have to touch them. They are there for the moment describing the spot is slower than your hand.

More on this: An AI game maker for game jams, and the honest caveats

A lot of no-code marketing quietly assumes that someone who does not program also cannot tell good from bad. That assumption produces tools that make choices for you and hide them, which is fine until the choice is wrong and you have no way to say so.

The whole design here runs the other way. You are the one who plays the game and rules on it. Pacing, feel, whether the jump is floaty, whether the forest is too dense to walk through: those are judgements, they are yours, and the tool is built to take them.

Flockbay is a desktop app for Windows and Linux. It ships with Godot inside it, so when you press play the game runs on your machine, with your graphics card and your memory. No streaming, no render queue, no browser tab deciding your framerate.

That is what makes a 3D world with real terrain, weather and a crowd of characters a sane thing to attempt. A flat game gets the same treatment rather than being the smaller thing you settle for: same app, same world tools, same local Godot. Browser tools steer you toward smaller scenes because that is what a tab can carry, and this one does not have to.

Building needs an internet connection. The chat, asset generation and world data all come over the network, so there is no offline mode and it would be dishonest to imply one. Playing the game you built does not need the connection.

More on this: An AI game maker for kids: what it is good at, and what to know first

The download is free and so are the world tools. Flockbay is free, AI included: free hosted AI every day, or your own Claude or ChatGPT, your own agent, or an API key. Flockbay builds from a library of ready-made objects, or with Godot's own shapes. The engine is Godot either way and your project is a Godot project either way.

That holds for one person or a team, and the project stays yours either way: a folder on your own disk.

More on this: AI life sim maker: a place, a routine, and people who keep one