Online AI game maker: the AI is online, the app is on your machine

The AI is a service. Flockbay runs over the network, as does asset generation and the world data the builder pulls in. None of that happens on your machine and none of it can happen without a connection. If your internet drops, building stops.

The builder and the engine are local. Flockbay is an installed application for Windows, it ships with Godot inside it, and when you press play the game runs on your own hardware at your own framerate. Nothing is streamed to you.

So it is an online AI tool in a wrapper that is not a website. That combination is unusual enough to be worth stating plainly rather than letting the word "online" do work it should not.

Models good enough to write working game code do not fit on a laptop alongside a 3D engine that is trying to use the same GPU. Running both locally means one of them is starved, and it would be the game.

You do not top up credits with us to have a conversation. The platform is free. Flockbay is free on your own AI: your Claude or ChatGPT plan, your own agent, or an API key.

More on this: No-code 3D game maker for worlds, not just scenes

Flockbay writes code. GDScript, inside your Godot project, for whatever the game needs to do: movement, interaction, inventories, enemies, save systems, the lot. You describe the behaviour, it writes it, you play the result.

It does not build your world. That is deliberate. Placing a treeline, cutting a valley, deciding where the town sits — those are decisions your hands make faster than a sentence can carry, and you make them in the builder with manual controls.

And it does not decide whether the game is good. You play it and rule on it. Not writing code has nothing to do with not having taste, and the loop where you send work back is the normal one.

More on this: Make a 3D game with AI, and know exactly which part the AI did

Not a finished game. Anyone promising that is describing a demo. What you should expect is a project that exists, a world you have started shaping, and something moving in it that you asked for.

The second hour is usually where it gets interesting, because that is when you start disliking specifics and changing them. That is the work. It is real, and it is more fun than the first hour.

More on this: An AI game generator from text, and what text is actually good at

Download free for Windows. No browser version. Your project sits on your disk as a Godot project, and Godot is open source, so it opens without this app.

Building needs a connection. Playing does not. There is no offline mode and there will not be a pretend one.

A network dependency is a real one. Some days the connection is bad, and building will be slower or will stop. It is better to plan for that than to be surprised by it, and the easy plan is to keep some manual world building in reserve for those days, since the builder controls are local.

The other habit worth having is saving often and playing often, so that whatever state your project is in when something goes wrong is a state you understand. That is good practice regardless of who is writing the code.

Nothing about this makes an offline mode viable. It is a genuine dependency of the design rather than a gap waiting to be filled.

More on this: Make a game with AI without giving up the game