Online game maker, honestly: this one is a download that needs the internet

Flockbay runs in a window on your computer, not in Chrome. You download it, you install it, it appears in your dock or taskbar. There is no URL you can send someone that opens the builder.

It is online in one real sense: you cannot build without a connection. The AI that writes your code, the asset generation and the world data all come over the network. Lose your wifi mid-session and building stops. That is a genuine dependency and not something to soften.

What does not need the connection is playing the game you made. That runs locally on the copy of Godot bundled with the app, on your own hardware.

Browser game makers are genuinely convenient. Nothing to install, works on a school laptop, opens on any machine you sit down at. If those are your constraints they are the right answer and you should use one.

The cost is the ceiling. A browser tab has a fixed memory budget and a rendering path it cannot leave, so tools built for tabs are designed downward to fit: smaller scenes, simpler lighting, fewer things alive at once. You do not notice this at the start. You notice it the first time you want a landscape with a view.

The other cost is where the project lives. On a hosted tool, your game exists on somebody's server under their terms. Here it is a Godot project in a folder on your disk, and Godot is open source, so the project opens without this app existing.

More on this: You searched for an online 2D game maker. This one is a download.

You build the world by hand. Which controls you get depends on the question the app asks before it creates anything: 2D or 3D, with the answer read from your description of the game and yours to change. In 3D it is terrain, water, weather, buildings and characters placed with a mouse. In 2D it is ground dragged on a cell at a time — the tiles, the edges and the collision all fall out of which cells are covered — and sprites set down at an exact position, turn and size. Either one behaves like a level editor, and that is the part where taste is the input and describing a thing is slower than doing it.

Flockbay writes the code. You say what should happen, it writes GDScript into your project, and you play the result and say whether it is right. That back-and-forth is the normal shape of the work rather than a sign something went wrong.

Not writing the code does not mean not having a view on the game. You are the one who plays it and rules on it.

More on this: Game development software you install, with AI inside it

Anyone building something they intend people to play for more than ten minutes, and anyone whose game needs a world rather than a scene. Local rendering is what makes those reasonable.

Anyone who cannot install software — a locked-down school machine, a Chromebook with Linux turned off, a shared computer — should not. That is a hard blocker and no amount of good intentions gets around it.

The download is free so finding out whether it suits you costs nothing except the install. Flockbay is free on your own AI: your Claude or ChatGPT plan, your own agent, or an API key.

More on this: You searched for an online game builder. This one is a download.

Downloading takes a couple of minutes and then it is over. The reason people search for an online tool is rarely the download itself, it is everything the download implies: a machine you are allowed to install on, enough disk, enough graphics card, and being at that machine when you want to work.

Those are the real constraints, and they are worth checking against your life rather than against a specification sheet. If you build in twenty minute gaps on whatever computer is free, a browser tool fits how you work and this one does not.

If you have one machine you sit at and you want the game to be more than a tab can hold, the install stops being the topic within a day.

More on this: Online 3D game makers, and why this one installs