A 2D game maker where the first thing you do is press play
Flockbay makes 2D games the same way it makes 3D ones: it builds the scene and writes the GDScript from your description, then plays the game to check its work. The TileMapLayer, the backdrop, the player controller and the sprites stay editable by hand in Godot's own 2D editor, and the result is a real Godot project on your own machine. 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.
AppImage, x86_64. Ubuntu 22.04, Debian 12, Fedora 39 or newer.
Intel or AMD Chromebook, with Linux turned on.
The project asks which kind of game before it will make one
A new game in Flockbay starts with one question: what game do you want to make? Flockbay reads your sentence and answers with two things, whether it is a 2D or a 3D game and one line of what it understood, and you confirm that on a single card. Nothing exists on disk until you do.
That sounds like a small piece of interface, and it is most of the argument. Tools that "also do 2D" usually bolt it on as a mode inside a 3D editor, so the flat game inherits menus written for a solid world and quietly gets the worse half of everything. Here the choice comes first and the project carries it from then on. Same app, the same chat, and Godot's own 2D editor underneath.
What changes is which tools those are. A 3D project gets a terrain, water and a sky from Godot plugins or from nodes the AI writes. A 2D project gets none of them, because none of them mean anything in a flat world. It gets its own instead: a TileMapLayer, Parallax2D layers behind it, the player controller, and the sprites placed in the world.
More on this: AI deckbuilder maker: synergies you can only find by playing
The first build is the brief's, not a template's
Every game starts blank. Before anything is built, Flockbay asks what it needs to know, one round of questions at a time, each with a recommendation, and writes a brief: what gets built first, what comes after, and what is not in this version. Nothing is built until you approve it.
Then the first build lands, and for most 2D games it is the part every project needs before it is anything: ground to stand on, a player controller that walks when you hold a direction, falls when the ground runs out and jumps when you press the key, and scenery behind it. The usual first evening of a 2D project, getting a character moving with gravity roughly right and something to land on, has already happened. Flockbay has also already played it: it runs the game, sends input events, reads stdout and the debugger, and captures the viewport to check its own work.
That changes the shape of the work more than it sounds like it should. The first thing you do is judge something rather than assemble something, and when the starting point runs, every change has an immediate answer. Ask for more ground and play it. Drag the platform somewhere else in the editor and play it. You are never staring at an empty scene working out which of the twelve missing pieces is the one stopping you.
More on this: An AI game maker for game jams, and the honest caveats
Ground is painted cells, and the tiles work the rest out
Ground is a TileMapLayer, and nobody places tiles one by one. Flockbay paints the cells, and so can you: Godot's TileMap panel paints cells as you drag, and a right-click drag erases them. The TileSet's terrains decide which picture lands in each cell, where the edges and outside corners fall, and what the player collides with.
The painted cells are data saved in the scene, and that has a practical consequence you only notice when it is missing: change one cell and only that cell and its neighbours' edges change, so a gap you tuned stays tuned. Godot's terrain autotiling picks the edge and corner pieces from the TileSet, so nobody places corner tiles by hand.
Whether ground stops a walker is set per tile in the TileSet's physics layer rather than assumed. A platformer's solid block and a top-down dirt path are painted the same way, and only one of them carries a collision shape.
The limit worth saying out loud: Flockbay's ground is tiles. A TileMapLayer covers cells on a grid; it does not draw an arbitrary curve of ground. If what you want is a hand-drawn hillside rather than a grid, knowing it now is worth more than finding out in week three.
More on this: AI city builder maker: simulation you can watch
Top-down and side-on are the same code with gravity switched off
Most tools ask you to pick a template at the start, platformer or top-down, and then the two behave like different products, so moving between them means starting again.
Here it falls out of one declaration. Say there is gravity and down becomes a direction: steering is horizontal, the body has weight, and a jump is a thing you can have. Say there is none and the same body steers on both axes, with nothing to jump away from. Same character body, same code, two genres.
The rest of how the player controller feels is a set of values rather than a script. Walk and run speed. How long it takes to reach that speed and how long to lose it. Air control, gravity, jump apex, body size, step length. So "it should feel heavier" is a retune of numbers that already exist, which is why asking Flockbay for it works, and why you can also set them yourself in the Inspector. A walk cycle is an AnimatedSprite2D or AnimationPlayer whose speed the script ties to the body's velocity, so the legs stay with the speed instead of skating.
The camera is a Camera2D that rides with the player: its drag margins are the dead zone the character can move around inside before the camera bothers to follow, and its limits are where the scroll stops. Flockbay sets them, and they are the Camera2D's values in the Inspector when you want to set them yourself. Cameras are one of the least forgiving parts of a 2D game, and the dead zone is a good example of a call you may want to make with your own hand after you have played it.
Most of the Catalogue is already sprites
The Catalogue holds 60,648 objects and 55,073 of them are sprites, 90.8%. Flockbay searches it by name for what the brief needs, and you can browse it too, with a picture of each object before it goes in. For a flat world that is the main route to art, ahead of drawing anything and ahead of generating anything.
Flockbay places a sprite, or a scene from your own project, at an exact position, rotation and scale, and you can move it by hand in Godot's 2D view. Its offset puts the figure's feet on the node's origin, so a barrel stands on the ground instead of hovering by however much transparent margin the artist left around it. With Y-sort on, draw order follows that point, which means a thing lower down the screen is in front of a thing higher up without anybody sorting anything.
Beyond the ground the backdrop is a background colour and Parallax2D layers, as many as the game wants depth for. Each layer is a node you can select, reorder and give a new texture in the Inspector.
The gap, plainly: Flockbay does not generate animation. It can make a single still picture when you ask for one, but not a six-frame attack. A walk cycle or any other multi-frame sprite comes from you or from the Catalogue, and once those frames are in the project, Flockbay wires them into the scene like any other node.
More on this: An adventure game maker where the writing stays yours
The parts of 2D that are quietly code problems
Most of the hard parts of a 2D game are invisible in a screenshot. Coyote time. Input buffering. State machines for a character with six actions that can interrupt each other in the wrong order. What an enemy does when it loses sight of you. What happens to a save file when the player quits mid-level.
These are exactly the things people give up on. They are also exactly the things a code-writing layer is good at, because they are well-understood problems with fiddly implementations. Asking for a jump that forgives a few frames of late input is one sentence. Writing it, testing it and not breaking the wall slide is an afternoon.
You say what should happen, Flockbay writes the GDScript inside your project, runs it, and reads the debugger for anything it broke. You do not have to read the script. You do have to play the game and say whether the jump feels right, because nobody else can tell you that. That loop, you judge and it revises, is the normal way of working, not a sign something went wrong.
A desktop app, and why that matters even in 2D
Flockbay is downloaded and installed on Windows, macOS or Linux. It ships with Godot inside it, so pressing play runs your game locally, on your machine, at your machine's framerate. What you end up holding is an ordinary Godot 2D project in an ordinary folder.
For 2D that sounds like it should not matter, and for one room it does not. It starts to matter when the painted world is large, when there are a few hundred things moving at once, or when you simply want the gap between making a change and seeing it to stay near zero.
Building does need an internet connection. Flockbay's AI and generation come over the network. Playing the game you built does not. If you are on a train with no signal you can play; you cannot build.
Getting from a room to a game
The distance between "the character moves nicely in a test room" and "this is a game" is mostly content and mostly boring. You need a way to move between rooms without losing state. You need a checkpoint that puts you back somewhere sensible rather than at the start of the world. You need a menu, an options screen, a volume slider that persists, and a pause that stops the physics rather than merely hiding it.
People underestimate this every time. The movement is the fun part to build, so it gets built first and built well, and then the project meets the unfun part and stops. Having that half written for you is not a shortcut around the craft. It is a way of arriving at the craft with time left.
The order that works is roughly: get the feel right in one room, then build the connective tissue, then make levels. The middle step is short here, which is the point.
And when you do reach the level-making step, you have a character that already feels correct, so every room Flockbay builds can be judged honestly rather than through a fog of "well, the jump is temporary".
Questions
- Can Flockbay really do 2D, or is it a 3D tool with a 2D mode?
- Flockbay settles 2D or 3D with you before anything exists, and the project carries that choice from then on. A flat game is built from 2D nodes: tile cells for the ground, a 2D player controller the AI writes, with the camera on it, and sprites at an exact position, rotation and scale. For you, Godot's own 2D editor and TileMap tools are there in the Standard and Full views. It is not a 3D scene with the depth switched off.
- Can I make a top-down game as well as a platformer?
- Yes, with the same tools either way. Side-on and top-down are not modes here. Declare gravity and you get horizontal steering and a jump; declare none and the body steers on both axes. Ground is painted identically for both, and whether it stops a walker is a property of the material rather than of the game type.
- Do I need to draw my own sprites?
- Usually not. The Catalogue is 55,073 sprites out of 60,648 objects, searchable by name with a picture of each. You can also bring your own art, and Flockbay can make a single still image on request. What it does not generate is an animated character: multi-frame sprites come from you or the Catalogue.
- Does it run in a browser?
- No. It is a desktop app for Windows, macOS and Linux. Your game runs locally on the bundled copy of Godot.
- How much does it cost?
- The download is free and every tool in it 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 open the project in Godot myself later?
- Yes. It is a normal Godot project on your disk, not a proprietary file that only this app can read.
Free to download for Windows, macOS and Linux.
Download Flockbay free