Skip to content

AI 2D game generator: the scenes and the code are generated, the feel is not

By Eduardo Orellana · Updated

The honest boundary of an AI 2D game generator: it can build the scenes and write every line of code in your project, and it cannot decide how the jump should feel. Flockbay is built along that line. 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 A 2D game maker where the first thing you do is press play.

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

Two things get called generation and only one works

Generating code is a solved-enough problem. A character controller, a tilemap collision fix, a dialogue box that queues lines, a boss with three phases: these are specified problems with known-good implementations, and a model writes them reliably.

Generating a game from one prompt is not. A 2D game is a stack of small feel decisions, and a prompt does not contain them. What comes back from a one-shot "make me a platformer" is a demo: it runs, the character jumps, and there is nothing in it you would play twice.

Flockbay draws the line where it actually falls. It agrees a brief with you, then generates the scenes and the GDScript and plays them to check its own work. You play the result and decide whether it is any good.

Before anything is generated, there is a brief

A 2D project here does not start from a prompt box. You say what game you want, Flockbay says whether it reads as 2D or 3D and what it understood, and you confirm. Then it asks what it needs to know, one round at a time, each question with a recommendation, and writes a brief: what gets built first, what comes after, what is not in this version. Nothing is generated until you approve it. For a platformer the first build is usually the floor every 2D game needs: a backdrop, a TileMapLayer with a ledge in it, and a player controller who walks, falls and jumps under the keys you press.

That changes what generation is being asked to do. Every request after that lands against a running game, and a request against a running game is much smaller than a request against nothing. "Make the jump heavier" has a jump to be heavier than. "Add a dash that cancels into a wall slide" has a character and a wall to attach it to.

The failure mode of one-shot game generation is that the model has to invent the context as well as the code (what the world is, what the character is, what any of it is for), and inventing context is where the result stops being yours. The brief removes most of the inventing: the context is decided with you, and every later change is held against it.

More on this: AI map generator for games: a real Godot world you can keep editing

What generation is genuinely good at in 2D

The unglamorous parts. Input buffering so a jump pressed four frames early still fires. Coyote time so stepping off a ledge does not feel like a betrayal. Slope handling that does not launch you. Screen shake that decays properly.

Every one of those is a known technique with an annoying implementation, and every one of them is where a hobby project stalls. Asking for them is a sentence each. Writing them yourself is a week.

It is also good at the systems that are boring rather than hard. Save and load. A pause menu that actually pauses physics. A settings screen that persists. Nobody wants to write those and every game needs them.

Where to stay alert is the category that is easy to generate and easy to get subtly wrong: a timer that drifts, a random number generator that is not seeded reproducibly, a score that rounds differently on two machines. These come back looking finished. Being explicit about what you want is what keeps them from becoming month-three mysteries.

The editor is yours, and the camera is where your hand wins

Layout and art direction run on real tools rather than a prompt box. Ground is painted: covering cells says where ground is and erasing takes it back, and the tiles, the edges and the collision all follow from that coverage rather than from anyone placing tiles one by one. Paint the same cells in a different order and you get the same world. Flockbay paints from the brief, and Godot's TileMap panel lets you repaint a path yourself.

Sprites go down at an exact position, rotation and scale, whether Flockbay places them or you move them in Godot's 2D view. Each one's offset puts its feet on its origin rather than the middle of its file, so a crate stands on the floor instead of hovering by however much transparent margin the image carries, and with Y-sort on a thing lower down the screen draws in front of a thing higher up.

The camera is a Camera2D: its drag margins are the dead zone the character moves around inside before the camera follows, 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. This is the clearest case for your own hand. A camera is judged rather than specified: you can see in one second that the dead zone is too generous, and you would struggle to say it in a paragraph.

How the player controller moves is a set of values too: 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 feels floaty" is a retune of numbers that already exist rather than new code. You do not need to know which number. Being non-technical means you do not write the code, not that you cannot tell when a jump is wrong.

And side-on and top-down are not two templates you choose between. Declare gravity and down is a direction, so steering is horizontal and a jump is available; declare none and the same body steers on both axes with nothing to jump away from. Asking for behaviour in a top-down game is the same kind of ask as in a platformer, because underneath it is the same code.

More on this: Why nothing generates a fighting game, and what can be generated

Most of the art already exists, and generation is the smallest route to it

The Catalogue holds 60,648 objects and 55,073 of them are sprites, 90.8%, searchable by name, each with a picture of itself before it goes in. For a flat world that is the ordinary way to get art. After it comes bringing your own, whether you drew it or found it, which is just as legitimate.

Generation is the smallest of those routes and it is worth being exact about its size. Flockbay can make a single still image when you ask for one, and sound: effects, loops and music. It does not generate an animated character: there is no multi-frame sprite generation. If your game needs a six-frame attack, those frames come from the Catalogue or from you, and it is better to know that now than in week three.

Whichever route a piece of art came from, you are told which. That matters if the game is ever going to be sold.

Working with stand-in art for the first few sessions is not a compromise. It is how you find out whether the game is fun before you spend anything on how it looks, and the first build is usually exactly that: some ground and a player controller, standing in for a game you are still deciding.

More on this: An asset generator attached to the game the assets are for

Where it runs

Flockbay is a desktop app for Windows, macOS and Linux with Godot bundled inside it, so your 2D game runs locally when you press play. No browser, no streaming. What you end up holding is an ordinary Godot project in an ordinary folder.

Generation itself needs an internet connection, as do the chat and asset generation. Building is online; playing what you built is not.

How to ask for something and get it

Describing behaviour well is a skill and it is not a technical one. The useful version is to describe what the player experiences rather than what the code should do. "The dash should feel committal: once it starts I cannot steer out of it, and there is a moment at the end where I am vulnerable" is a better request than any attempt to name variables.

Being specific about the exception cases helps more than being specific about the main case. What happens if the player dashes into a wall. What happens if they dash off a ledge. Those are the parts that get invented if you do not say, and an invented decision is a decision you did not make.

When something comes back wrong, saying what is wrong is enough. You do not need to diagnose it. "The dash goes too far and I keep overshooting the platform" is a complete and actionable report.

This is the loop the whole tool is arranged around, and it treats you as the person who knows what the game should feel like, because you are.

More on this: AI metroidvania maker: building one when the map is the design

Questions

Can it generate a complete 2D game from a prompt?
Not from one prompt. It agrees a brief with you, then generates the scenes and the code and plays them to check its work. You play the result and judge the feel, which is the part a prompt cannot contain. The ground, the sprites and the camera are also yours to move by hand in the Godot editor.
What language does it generate?
GDScript and Godot scenes, written into a normal Godot project on your disk.
Can it generate sprites too?
Mostly you will not need it to. The Catalogue is 55,073 sprites out of 60,648 objects, searchable by name with a picture of each, and you can bring your own art as well. Flockbay can make a single still image on request. It does not generate animated sprites.
Does it only do platformers?
No. Side-on and top-down come out of the same character body: declare gravity and you get horizontal steering and a jump, declare none and it steers on both axes. Ground is painted the same way for both, and whether it stops a walker is a property of the material.
Do I need to review the generated code?
No. You review the game by playing it. The code is there if you ever want to look.
Is it free?
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 ask for changes to code it already wrote?
Yes, and that is most of the work. Describe what is wrong with the result and it revises. You never have to edit a script yourself.

Free to download for Windows, macOS and Linux.

Download Flockbay free