An AI game maker without a credit counter, and how the free AI works instead

What a free AI game maker gives you is defined on that page.

The problem with a visible balance is not the money. It is what it does to iteration. Every time you consider trying a second version of something, the counter is an argument against it, and you accept the first result more often than you should.

That is the opposite of how anything creative works. A game gets good because you did the thing eleven times. A pricing model that makes attempt eleven feel expensive is quietly making your game worse.

So the counter is not just an accounting choice. It is a design constraint on the user, and it usually was not intended as one.

It is free: every world tool, your own art, playing, sharing with playtesters and exporting. Flockbay is free, AI included: free hosted AI every day, or your own Claude or ChatGPT, your own agent, or an API key.

Here is the honest part: AI still has a meter somewhere. Any tool that pays a model provider per request and offers you unlimited requests is either mispricing or planning to change the terms. Flockbay's hosted AI is a daily allowance, and the app shows a quiet share of today's usage left; it is not a balance you buy, and it refills the next day. Your own Claude or ChatGPT has its provider's limits, and an API key draws on a balance you top up with its company. On your own AI, Flockbay adds no counter of its own on top.

Which AI you use changes who pays for the requests, not the engine underneath. The world tools and the bundled Godot are the same whichever AI does the work.

The world tools in your hands are never metered. They are buttons around the Godot editor's view, and shaping a coastline, moving a building, adjusting weather or rearranging a whole level twelve times by hand uses no AI at all.

Playing your game is free in the same sense. It runs locally on the copy of Godot bundled with the app, on your own machine, for as long as you want.

So the pattern that gets expensive elsewhere, endlessly re-rolling a scene, is one you rarely need here. Flockbay changes what you asked about rather than regenerating everything, and the fine adjustments can be done by hand at no cost.

A desktop application for Windows and Linux, downloaded and installed, with Godot inside it. Not a browser tool. Your project is a real Godot project on your disk.

Flockbay agrees a brief with you, builds the world, writes the GDScript for the behaviour you describe, and plays the game to check its work. You judge the result by playing it.

Building needs an internet connection because the AI and generation are online. Playing what you built does not.

More on this: Free online game maker, and the case for downloading one instead

The question worth asking about any of these tools is what happens on your eleventh attempt at the same thing. If the answer involves opening a top-up page, that will shape your project whether you want it to or not.

With Flockbay there is no top-up page. Your eleventh attempt comes out of the free daily allowance, out of a plan’s monthly usage if you chose one, or past that month out of on-demand usage if you turned it on, or out of your own AI's limits if you connected one.

What runs on the AI is Flockbay doing the work: asking the brief's questions, building the world, writing code, generating pictures and sound, and play-testing. Flockbay builds from a library of ready-made objects, or with Godot's own shapes.

Everything else is your machine: the world tools in your hands, the editor, the game running on the bundled Godot, your project files on your own disk. None of that is counted and none of it stops when today's AI usage runs out.

So the practical shape is that a day of hand-tuning the world costs nothing, and a day of big new systems is where the AI usage goes. That is worth knowing when you plan a week.