HTML5 game maker: what Flockbay is and is not

Two different things, and they need separating. Sometimes it means "I want the game to be playable at a URL" — the delivery matters, because you are putting it on a portal, embedding it somewhere, or sharing a link. Sometimes it just means "I want a game maker that runs in my browser" and the export target is not really the point.

If it is the second one, the page you want is the one about downloading versus not, because the answer there is that Flockbay is a desktop install and there are reasons for that. If it is the first, keep reading, because the answer is more specific.

More on this: AI game maker, online and free: half of that is true here

It is a desktop application for Windows, and it ships with Godot inside it. When you press play, the game runs on your machine, using your GPU and your memory. Nothing is streamed and nothing renders in a data centre.

That is the design rather than a detail of packaging. What it buys you is a plain Godot project in a folder on your own disk and a game whose budget is your hardware rather than a page load. On the 3D side that is what makes terrain, weather and a few hundred simulated characters a sensible thing to attempt at all.

The world-building is local either way. Creating a project asks 2D or 3D first: in a 3D one you sculpt terrain, outline water and set sky and weather, and in a flat one you paint tile ground by dragging across it and place sprites by hand at an exact position, turn and size. Neither is shaped by what a tab can afford, which is worth knowing before you plan a web release around it.

The engine underneath is Godot, and Godot itself has export targets beyond the desktop. But Flockbay is not built as a web-first pipeline, and it would be dishonest to present it as one. Anything you do in that direction is you working with your Godot project, not a feature of this app.

More on this: A Rosebud alternative that trades the browser for the hardware

For a browser game portal, an embedded game, or something you want people to click and play in ten seconds, a tool built for web output is straightforwardly better. It will handle the load times, the input differences and the asset budget that a browser imposes, because those constraints shaped it.

There are good ones and they are honest about what they are. Nothing is gained by using a local-first tool and fighting it toward the web.

More on this: Vibe jam: what the format rewards, and what it rules out

When the game is the point and the URL is not. A game people download and play for hours has different requirements from a game people click on a portal: it can take its time loading, it can weigh what it needs to weigh, and it does not have to survive being one of forty open tabs. A small flat game is welcome to those freedoms too — they are not a reward for being large.

You build the world by hand. Terrain, water and weather in a 3D project; painted tile ground and placed sprites in a flat one; buildings, props and characters put where you put them either way. Flockbay writes the GDScript for behaviour into your project. You play it locally and say what is wrong, and it changes. What you end up owning is a real Godot project in a folder on your disk.

Building needs an internet connection because the chat, asset generation and world data come over the network. Playing what you built does not. Flockbay is free on your own AI: your Claude or ChatGPT plan, your own agent, or an API key.

More on this: Web game maker: why this one is a download instead