Skip to content

An AI game maker for solo devs: one person, several jobs

By Eduardo Orellana · Updated

Working alone means every discipline is a bottleneck in turn. Flockbay takes the programming out of the rotation so the project keeps moving on the evenings you have. Free AI to start: Flockbay's AI and your own Claude, ChatGPT, agent or API key are free for your first build; after that, a plan keeps you building. It runs on Windows, macOS and Linux, on the official Godot engine.

The main page on this subject is What is an AI game maker that writes a real Godot project?.

AppImage, x86_64. Ubuntu 22.04, Debian 12, Fedora 39 or newer.

Intel or AMD Chromebook, with Linux turned on.

Download for macOSDownload for WindowsDownload for Linux

The solo failure mode

Solo projects rarely die from lack of ideas. They die in the third month, on a Tuesday, because the state machine is broken and you have two hours and no energy, and that is the fourth evening in a row where nothing about the game has visibly changed.

The reason that kills projects is momentum. When you work alone, the only thing keeping you going is seeing the thing get better. Weeks of invisible plumbing remove exactly that.

Flockbay attacks the plumbing specifically. You describe the system, Flockbay writes the GDScript into your project, you press play. The evening produces something you can look at.

More on this: How long does it take to make a game with AI?

What stays yours when you work alone

You decide the game, and you touch it when you want to. Flockbay builds it from a brief you approved, in whichever kind of world the project is: 2D or 3D, read from your description of the game and yours to confirm. On the 3D side it is buildings and characters, with terrain, water or weather from a Godot plugin when needed; in a flat project, painted tile cells and sprites at an exact position, rotation and scale. Godot's own editor is there in the Standard and Full views, and working alone, that last pass of placement is often the part you enjoy. It is also the part a sentence gets close to but not exactly right.

You do the design. Every decision about how the game feels — pacing, difficulty, what the player is afraid of — stays yours, and it is the only thing that makes a solo game distinctive.

And you do the judging. Play it, decide it is wrong, say what is wrong. That loop is the tool working correctly rather than failing.

Working in short sessions

A lot of solo development happens in ninety-minute blocks after work. That shape punishes tasks with long ramp-up, which is most programming: half the block is spent remembering where you were.

Describing behaviour has almost no ramp-up. You can arrive, say what should change, see it, and leave with the game measurably different. Nudging a piece of world by hand is similar: immediate, visual, and you can stop anywhere.

A 2D project is the sharpest version of this. Once the first build lands it is playable every evening you open it, so the session starts with playing rather than with setting up, and ground you paint is walkable at once. Ninety minutes is enough to end with a room that is genuinely different.

That is not a productivity claim with a number attached. It is a claim about what kinds of tasks fit a short evening, and it is why solo projects here tend to keep moving.

More on this: Unlimited AI game maker? An honest answer

Your project stays yours

The output is a real Godot project on your disk. Godot is open source. Version control behaves normally, the scripts are readable GDScript, and nothing about the project depends on our app continuing to exist.

This matters more when you are alone, because you have no one to inherit the mess and no studio to migrate it. A project that stays in a standard format is a project you can still open in five years.

The practical facts

Desktop app for Windows, macOS and Linux. It bundles Godot, so setup is one download. Building needs an internet connection because the chat and asset generation are online; the game you built runs locally and does not.

Free to download. Free AI to start: Flockbay's AI and your own Claude, ChatGPT, agent or API key are free for your first build; after that, a plan keeps you building. Flockbay builds from a library of ready-made objects, or with Godot's own shapes.

More on this: AI idle game maker: the genre that is almost entirely code

Scope, which is the only thing that will kill you

Removing the coding bottleneck moves the bottleneck rather than deleting it. The new one is content and finish, and it is less visible, so it catches people out.

A world takes as long to get right as it takes, regardless of who built it. Ten levels is ten levels. Deciding early how big the game actually is, and writing that number down, is worth more than any tooling decision you will make.

The useful habit is to build the smallest complete version first, including the ending. A finished small game can be expanded. An unfinished large one cannot be shrunk.

Questions

Is this a replacement for hiring a programmer?
For game code, largely. For deep engine work, custom rendering or hard optimisation on a shipping build, no.
Do I need to read the code it writes?
No. You judge the game by playing it. The code is there in plain GDScript if you want it.
Can I keep working if I stop using Flockbay?
Your project is a Godot project on your own disk and Godot is free and open source, so stock Godot opens it.
Does it work offline?
Building does not — the AI and asset generation come over the network. Playing what you built does.
What does it cost?
Free to download. Free AI to start: Flockbay's AI and your own Claude, ChatGPT, agent or API key are free for your first build; after that, a plan keeps you building.

Free for Windows, macOS and Linux. Keep the project moving on a weeknight.

Download Flockbay free