Skip to content

AI platformer game maker: the whole genre lives in the jump

By Eduardo Orellana · Updated

Platformers are judged in the first ten seconds, entirely on how the jump feels. Flockbay makes that feel something you tune by describing and playing, rather than by editing a character controller you did not write. 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 platformer maker with no ceiling on it.

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

Ten seconds is the whole audition

Nobody reads your platformer description. They press right, they press jump, and they decide. Gravity, jump height, the acceleration curve, how much control you keep in the air, whether a jump pressed slightly before landing still counts. Get those wrong and the level design cannot save it.

The reason so few first platformers feel good is not taste, it is iteration count. When changing gravity means editing a script you barely understand, you try three values and settle. Feel comes from trying thirty.

Flockbay changes the cost of an iteration. You say the jump is floaty at the top, Flockbay changes the code, you play it again. Thirty iterations is an afternoon.

More on this: How to make a game like Mario: start with the jump

The parts you will end up asking for

Every good platformer has a handful of forgiveness mechanics that players never notice and would miss instantly. Coyote time, so a jump still works a few frames after leaving the ledge. Input buffering, so a jump pressed just before landing fires. Variable jump height tied to how long the button is held. Corner correction, so clipping a ledge nudges you around it instead of stopping you dead.

Naming them is not required. Describing the problem is enough: "I keep falling when I swear I pressed jump on the edge." That is a solvable, well-understood problem and Flockbay writes the GDScript for it in your project.

You do not need to read the script to know whether it worked. You need to play it. That loop is the design process, not a workaround for not coding.

More on this: Claude Haiku 5.5: Can the Cheapest Claude Build Celeste's Jump?

Levels are built a room at a time, and judged by playing them

Once movement feels right, a platformer is a sequence of small spaces that each teach or test one thing. The gap that shows you the jump distance. The first enemy you must jump over rather than around. The room where the two combine.

That sequence is not something to describe in a sentence and hope. It goes in the brief as rooms, each with the one thing it teaches, and Flockbay builds them and plays them. Then you play them. A platform two units too far left is one sentence, or one drag with the same tool in the Godot editor when it is quicker to do than to say.

Which kind of space it is gets settled before the project exists: the app reads 2D or 3D from your first message, and nothing is created until you confirm it. Neither is the reduced version of the other.

A 2D level stands on a TileMapLayer, whose TileSet terrains give the edges and the collision, and a block is standable the moment it is laid. Moving a ledge two units left is a sentence to Flockbay, or a drag in Godot's TileMap panel.

A 3D project gets that side's own nodes instead, with terrain, water and weather from Godot plugins. The flat world has a shorter list — a TileMapLayer, the backdrop behind it, the player controller, and placed sprites. That is the honest scope of a flat world rather than a smaller advantage.

Nothing this genre is judged on sits on the missing part of that list. Walk and run speed, how fast the body reaches a speed and how fast it loses it, air control, gravity, jump apex, body size and step length are controls on the player controller: Flockbay turns them when you say the jump is floaty, and they are values in the Inspector if you would rather turn them yourself. Thirty iterations of the jump is thirty small moves rather than thirty rewrites.

More on this: AI side scroller game maker: one axis, a lot of precision

The practical facts

Flockbay is a desktop app for Windows, macOS and Linux with Godot bundled inside. Press play and your game runs locally at your own framerate, which for a genre that lives on frame-accurate input is the right way round.

Your project is a real Godot project. It is not a save file only this tool can read, and Godot is open source.

Building needs an internet connection, since the chat and asset generation come over the network. Playing does not. Free to download. 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.

More on this: Racing games are won or lost on the car, not the track

The camera is half the feel and nobody notices it

A platformer camera is doing constant quiet work. Leading the character in the direction they are moving so you can see what is coming. Lagging slightly on landing so a fall does not lurch. Holding still in a small room instead of drifting. Looking down when you hold down.

Get it wrong and players will tell you the jump feels bad, because they cannot see the camera and they can see the character. It is one of the most common misdiagnoses in the genre.

It is also code, so it changes when you describe the problem. If a section feels claustrophobic, say so and let the camera pull back before you start rebuilding the level. Testing the cheap fix first is usually right.

A starting project for this is the platformer game templates. The design note that goes with it is how Mario levels teach one mechanic at a time.

Questions

Can I tune the jump without editing code?
Yes. Describe what feels wrong and Flockbay changes the GDScript. You play it again and decide.
2D or 3D?
The app reads it from your first message and you confirm it, and neither is the cut-down one. A 2D platformer stands on a TileMapLayer, with gravity, air control and jump apex as properties of the player controller Flockbay writes. A 3D one is built from 3D scenes, with terrain or water from a Godot plugin when the level needs them. Same app, same editor, the same chat.
Does it include coyote time and input buffering?
They are code, so they get written when you ask for them. You can describe the problem rather than name the technique.
Is it free?
The platform 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.
Does it run in a browser?
No. It is a desktop app for Windows, macOS and Linux, and your game runs locally.

Free for Windows, macOS and Linux. Spend the afternoon on the jump; it is worth it.

Download Flockbay free