What Flockbay does

Flockbay is not generating a description of a game somewhere else. It reads, creates and edits ordinary files inside your project folder, the same way a programmer would, and those edits are on your disk immediately.

It can only write inside the project you have open. It cannot reach the rest of your machine, and it does not touch Flockbay’s own bookkeeping.

This is why you do not need to write code. It is also why the result is a real Godot project rather than something only this app can open.

As well as editing files, Flockbay has typed tools for the world itself, and which tools it has depends on whether you made a 2D or a 3D project. It is the same chat in the same chat either way; it is simply told the truth about what the world it is looking at can do.

A 3D project gives it six: terrain, water, environment, weather, the player, and placed objects. Terrain builds ground from real-world data. Environment covers sky, sun, moon and the clock. Placed objects puts individual things at exact positions.

A 2D project gives it the four a flat world has: the ground, what is beyond it, the person, and placed objects. Ground is the tile layer, covered and erased by cell. Beyond it is a sky colour and one band of scenery along the horizon. The person is the character body and its handling. Placed objects works as it does in 3D — a picture or a scene put at an exact position, turn and size.

Which means the missing ones are genuinely missing. There is no water tool and no weather tool in a flat world, because a flat world has no answer to give them, and asking for rain there is a call that cannot succeed rather than one that quietly does something else. Knowing that up front is worth more than a substitute that half works.

These are separate tools on purpose. Flockbay is not allowed to compose them into one sweeping "build me a world" action, and there is no hidden macro behind them — each thing that happens to your world happens because a specific tool was called for it.

Flockbay does not ask for permission before it edits a file in your project. There is no diff to review — the work lands, and you judge the result by looking at it. On your Claude plan, a shell command that is not one of Flockbay’s own does ask first.

It does not decide whether the game is good. You do. Playing it and saying it is wrong is the normal loop, not a failure of the tool.

It also does not replace the builder. Placing a tree exactly where you want it, getting a shoreline right, or nudging a sprite until it sits on the ledge the way you meant, is faster by hand.