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

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 you build the world by hand and have the code written for you, and neither of those things removes the engine you are standing on.

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

The division is deliberate and it is the whole design. You build the world directly, with your hands, in a builder that behaves like a level editor rather than a chat window. That is the part where taste matters and where describing what you want in a sentence is slower than doing it.

What "directly" puts in your hands depends on a question the app asks before it will create anything: 2D or 3D, shown as two pictures, with no default. Both are first-class categories rather than a main case and a mode, and the builder carries the answer from then on.

Pick 3D and you place terrain built from an elevation map, water, weather, a time of day and a sky, along with buildings and characters. Pick 2D and none of those appear, because none of them mean anything in a flat world — the toolbar honestly shrinks to what is actually there. In their place you drag over cells to say where the ground is, and the tiles, the edges and the collision are all derived from that one map of covered cells, so the ground is walkable the moment you paint it. Whether a material stops a walker is declared rather than assumed, which is why a platformer's block and a top-down path are the same gesture. Then you place sprites, and most of the Catalogue is already sprites — 55,073 of 60,648 objects.

Flockbay handles the part where taste does not help you: the code. You say what should happen and it writes the GDScript that makes it happen, inside your project, where you can see it. You can open it in the Godot editor and change it. You are asked to play the result and say whether it is right.

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: A 3D game maker for people who bring their own Claude or ChatGPT plan

Flockbay is a desktop application for Windows, 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 world data 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: Looking for an AI dungeon master, or a game to put one in?

Developers who want to make a specific game on their own Claude or ChatGPT plan. 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 your world, you will play it and dislike parts of it, and you will go back in. 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