# AI 2D game maker: what a working session actually looks like

Flockbay is an AI 2D game maker in a specific sense: the AI builds the scenes and writes the code, and you decide whether the game is right by playing it. 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.

Source: https://flockbay.com/ai-2d-game-maker/ · Updated 2026-10-18

## The first session opens on a brief, then on an opinion

A new game starts with a sentence. Flockbay reads it, says whether it is a 2D or a 3D game and what it understood, and you confirm; nothing is created until you do. Then a round or two of questions, each with a recommendation, and a brief: what gets built first, what comes after, what is not in this version. Approve it and the first build lands. For a platformer that is a backdrop, a TileMapLayer with a ledge cut into it, a platform off to one side, and a player controller who walks, falls and jumps. Flockbay has already played it, sending input events and reading the debugger, before you press a key.

So the session does not open with setup. It opens with an opinion: the jump is floaty, the ledge is too far out, that platform wants to be lower. Having something to be wrong about is the useful state to be in, and most tools make you spend an afternoon earning it.

Widening the ground is one sentence, or one drag in Godot's TileMap panel. Ground is a TileMapLayer: cells laid, cells erased, and the TileSet's terrains pick the tiles, the edges and the collision. Nobody picks a corner piece out of a palette.

Then the behaviour. A character who runs, jumps and wall-slides. Flockbay writes the GDScript, runs it, and you press play. The run is fine. The jump is heavy. The wall slide catches on the corner. You say those three things, they change, and somewhere around the fourth pass the movement feels like the thing you had in your head, which is the point at which the room starts to matter, because now you can tell whether it is laid out well.

That is the whole loop. Ask, play, judge, repeat, with your own hand for the taste calls. Nothing in it requires [reading a line of code](/blog/how-to-judge-a-game-you-did-not-code/), and all of it requires having an opinion.

## A brief beats a one-line level description

It would be easy to build a tool where you describe the level in one line and the AI invents the layout. It has been tried and the results are legible. Generated levels feel like nobody chose anything, because nobody did.

Flockbay builds the layout too, but not from one line. The brief settles what the level is for before anything goes down, and every build is held against it. What a brief cannot settle is the last metre: whether that platform sits a tile too high. That is cheap to do by hand and expensive to describe, so Godot's own 2D editor is there in the Standard and Full views, and Godot's undo takes a change back.

The same logic applies to [starting from a template](/templates/godot-2d-game-template/). A template is a level somebody else laid out around a feel somebody else tuned, so it is worth starting from one when its feel is close to the one you want.

## Side-on and top-down are not two modes

They fall out of one declaration. Say the world has gravity and down becomes a direction: steering is horizontal, and a jump is a thing you can have. Say it has none and the same body steers on both axes and there is nothing to jump away from. Same code underneath, and no menu anywhere that makes you tell it which genre you are in.

Whether ground stops a walker is set per tile in the TileSet's physics layer, for the same reason. A platformer's solid block and a top-down dirt path can be painted with identical strokes, and only one of them carries a collision shape. Drawing and physics are separate decisions, which is why a top-down room here is not a side-on room with the gravity switched off and the best hoped for.

Feel is values rather than a rewrite. Walk and run speed, how long the body takes to reach a speed and how long it takes to lose it, air control, gravity, jump apex, body size, step length. "Make it heavier" is a handful of numbers moving, not new code. A walk cycle can have its playback speed tied to the body's velocity, so the legs stay with the speed instead of skating out from under it.

## Things people usually give up on

A save system that survives being closed mid-level. A settings menu with remappable keys. Enemies with a state machine that does not deadlock. An achievement that fires exactly once. None of these are interesting to build and all of them are the difference between a prototype and a game. Asking for them is a sentence, and that is the practical reason the AI earns its place.

The camera is where your own hand pays off most, and it is worth knowing why. Flockbay sets up a Camera2D: its zoom is what is in view, its drag margins are the dead zone the player can move around inside before anything scrolls, and its limits are where the view stops. All three are values in the Inspector, yours to set. Framing is taste, and taste is often faster with a cursor than with a paragraph.

Add to that the things that only show up on someone else's machine: a resolution you did not test, [a controller that maps its buttons differently](/blog/controllers-control-everything/), a frame rate that is double yours and quietly breaks anything tied to frames rather than time. Asking for these to be handled properly at the start is far cheaper than discovering them from a stranger's bug report.

## The project is a Godot project

Everything written goes into a normal Godot project on your own disk. There is no proprietary format. If you want to open it in Godot yourself, or hand it to somebody who codes, that works without an export step.

[The engine underneath being open source](/what-is-godot/) is not a footnote. It means the ceiling on your project is Godot's ceiling rather than ours.

That also means nothing here is a one-way door. If you outgrow the tool, or you want to work with someone who codes, the project comes with you and keeps working. There is no export step and no conversion, because there was never a proprietary format to convert from.

## Installed, not in a tab

Flockbay is a desktop app for Windows, macOS and Linux. Godot ships inside it and your game runs locally when you press play. There is no browser version.

[Building needs an internet connection](/answers/does-flockbay-work-offline/) because Flockbay's AI and generation come over the network. Playing what you have built does not.

## Art, and when to care about it

The temptation is to sort out the look first, because the look is the part you can picture. It is usually the wrong order. A game with perfect sprites and a bad jump is a bad game that took longer to find out about.

Coloured rectangles are a legitimate way to work for the first stretch. They are honest about what has been decided and they make it obvious when the movement is carrying the game rather than the art. Once the feel is right, the art has something to serve.

When you do get to it, most of what a flat game needs is already in the Catalogue: 55,073 of its 60,648 objects are sprites, searchable by name with a picture of each. Flockbay places one at an exact position, rotation and scale, and so can you, in Godot's 2D view. A sprite's offset puts its feet on its origin rather than the middle of its file, so a crate stands on the ground instead of hovering by however much transparent margin the file happens to carry, and with Y-sort draw order follows that same point, so the thing lower down the screen is in front.

Flockbay builds from a library of ready-made objects, or with Godot's own shapes, and can make a single still image on request. It does not generate an animated sprite: no frames, no sprite sheet. That is a gap worth naming here rather than on the day you need a walk cycle for a boss: anything that has to move through drawn poses is your art, an artist's, or the web's. Whichever route an asset took, the tool says which rather than blurring them, and that matters if the game is going to be sold.

Plenty of finished 2D games have deliberately simple art. Simple is a style as well as a stage.

## Questions

### Do I have to describe my level to the AI?

Only as much as you want to. You describe the game, Flockbay asks the questions that matter and builds the level from the brief you approve. If you would rather lay a platform yourself, Godot's TileMap panel and 2D view are right there.

### Is 2D a cut-down version of the app?

No. Same app, the same chat, with the flat world's own tools. 2D is a setting the project carries from the moment you confirm it at creation.

### What if I do not like what it writes?

Say so and it changes. Handing the result back is the normal loop rather than a failure.

### Which AI writes the code?

Flockbay, which writes GDScript directly into your project.

### Does it work offline?

No. Building needs the network. Playing a finished game does not.

### What does it cost?

The download is free. 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.

### Can I make something other than a platformer?

Yes, and there is no genre list to pick from. Top-down and side-on are the same code with gravity declared or left out, so a top-down game is not a mode you have to be granted.

Download Flockbay free: Free to download for Windows, macOS and Linux. https://flockbay.com/

Related: [2D game maker](/2d-game-maker/), [AI 2D game generator](/ai-2d-game-generator/), [AI platformer maker](/ai-platformer-maker/), [AI side scroller game maker](/ai-side-scroller-game-maker/), [AI top-down game maker](/ai-top-down-game-maker/)
