A game maker for kids, with the grown-up details up front

Flockbay is a desktop application. It installs on a Windows PC, or on a Chromebook with its Linux environment turned on. It is not a website and not a tablet app. If the machine in the house is a tablet, this is not the right tool and it is better to know that now.

Building a game needs a live internet connection, because the AI that writes the code and the systems that generate assets are online. Playing a game that has already been built does not need the connection. So a long car journey is fine for playing, and not for making.

The download is free and so is the builder. There is no family or child pricing. Flockbay is free on your own AI: your Claude or ChatGPT plan, your own agent, or an API key. Every child is using the same free app and the same engine as anyone else.

After they describe the game, the app asks one thing: 2D or 3D, with the answer read from their description, and nothing made until they confirm it. Pick 2D and there is already a game running — a sky, a band of scenery along the horizon, ground with a ledge in it, a platform off to one side, and a person who walks, falls and jumps when they press the keys. The ground is painted, so laying more of it is holding the mouse down and dragging, and rubbing it out is dragging back over it. Nothing has to be set up before that works.

Pick 3D and they build a place first. Raise hills, put a lake in the dip, drop trees along a ridge, put a character on the path. This is done directly, with a mouse, in a builder that works the way a level editor works. It is closer to building something in a sandbox game than to filling in a form.

Then they say what should happen. The character can double jump. Touching the spikes starts the room again. The wolves come out at night. Flockbay writes the code that makes those true, in the project, and the game runs on the computer straight away.

Then the good part: they play it, and it is wrong. The jump is floaty, the wolves are too fast, night is boring. They say so, it changes, they play again. Kids are extremely good at this step and usually much less polite about it than adults, which makes them better at it.

A lot of software for children works by removing choices, on the theory that fewer options means less frustration. The result is that every game made with it looks the same and the child can feel the ceiling within an afternoon.

This works the other way round. The thing removed is the code, which is the part that stops people. The decisions stay. What the world looks like, what the game is about, whether it is any good — those are the child's, and there is no menu of approved game types they have to pick from.

The engine underneath is Godot, which is open source and which real games ship on. What a child makes is a real Godot project on the disk. If they stick with it for years, they do not have to leave and start over.

There is no age gate to speak of, and no claim that this is designed for a specific age band. What it needs is a person who can use a computer with a mouse and keyboard, describe what they want in sentences, and stay with something for longer than one sitting. That describes some eight year olds and not some fifteen year olds.

It is worth setting one expectation. This is not a tool that hands over a finished game in five minutes. The first playable version arrives quickly; making it good takes as long as making anything good takes. A child who wanted a finished game to appear will be disappointed, and a child who wanted to make one will not.

Sitting with them for the first session helps, mostly because the first session is where the loop clicks. After that most of them do not want you there.