Make an endless runner where the tuning is the game
An endless runner is about four numbers and how they change over ninety seconds. Flockbay writes the system for you so you can spend your time on the numbers, which is where the game actually is. 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 What is an AI game maker that writes a real Godot project?.
AppImage, x86_64. Ubuntu 22.04, Debian 12, Fedora 39 or newer.
Intel or AMD Chromebook, with Linux turned on.
The genre is small and unforgiving
There is not much to an endless runner. Something moves forward, obstacles arrive, you jump or you do not. Everyone who has made one knows the code is a weekend and the feel is a month.
The month goes on jump arcs, gap spacing, how fast the speed ramps, how long the grace window is when you press jump slightly early, and how the spawner avoids handing the player an impossible sequence. Get those wrong and a technically complete runner is unplayable. Get them right and a very plain one is hard to stop playing.
Which is why an AI that writes the code is more useful here than it sounds. The code is not the hard part, but it is the part standing between you and the tuning.
What Flockbay builds and what you decide
Describe the runner and Flockbay writes the GDScript: the endless track, the chunk spawner, the pooling so it does not stutter after five minutes, the difficulty curve, the score and the death. It goes into your project as ordinary code you can point at.
You then do the part that matters, which is playing it. Say the jump feels floaty and it gets less floaty. Say the gaps get punishing too early and the curve softens. That back and forth is the normal way to work, not a sign that something went wrong.
You do not need to be able to write a spawner to know that a run is not fun in its fortieth second. That judgement is the thing you bring.
The chunks are level design, and you judge them by running them
Most endless runners are built from chunks: a handful of authored track segments that the spawner shuffles. Building those chunks is level design. Flockbay lays them out from the brief, with the gaps and the obstacle spacing as numbers it can change, and runs them before you do.
Whether a jump sequence is right is something you see, not something you read. Play it and say the third gap comes too soon after the second. Or, when it is quicker to do than to say, open the chunk in the Godot editor and move the platform yourself: it is an ordinary Godot scene, and Godot's undo takes a change back.
The world around the track is the same. In a 3D world that is buildings and props going past, with terrain or a sky from a Godot plugin; in a flat one it is a background colour and Parallax2D layers. Runners live or die on readability, so seeing at once whether the obstacle reads against the background is worth more than any generator.
More on this: No generator produces a platformer worth playing, and here is why
Framerate is a feature here
A runner at an inconsistent framerate is a broken game, because the player is timing inputs against motion. This is one genre where where the game runs is not a technicality.
Flockbay is a desktop app for Windows, macOS and Linux, and the game runs locally on the copy of Godot bundled with it. Not in a tab, not streamed from somewhere else. You are seeing your machine, which is also what your player will see.
Building needs an internet connection because the chat and asset generation come over the network. Playing what you built does not.
What it costs to try
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.
A runner is a genuinely good first project on any tool, because the scope is honest and you find out quickly whether you like the loop of describing, playing and correcting.
The score and the reason to run again
A runner without a reason to restart is a tech demo. The reason is usually a number, and how you present that number does more work than anything else in the game.
A best score that sits on screen during the run. A near miss that registers. A short pause on death that is long enough to feel the loss and short enough that you press restart before thinking. Those are all code, and they are all things you specify by playing and reacting rather than by planning.
Unlockables and daily variants come later and are usually a distraction until the base run is good. If the fortieth second is not fun, nothing bolted on top will fix it.
Questions
- Can I make a 3D runner, not just a 2D one?
- Yes. The app reads 2D or 3D from your first message, and you confirm it before anything exists. A three-lane 3D runner is a normal project here. So is a side-on 2D one, where the track is painted tile cells and the obstacles are sprites from the library. Same app, same editor, the same chat.
- Can I publish it to mobile?
- Through Godot. Export in Godot… opens Godot's own Project › Export… on your project for Android, with the usual Android SDK and signing steps. Flockbay itself is a desktop app for Windows, macOS and Linux, so you build on a computer rather than on a phone.
- How do I change the difficulty curve?
- Play it, say what felt wrong, and Flockbay changes the code. You can also open the values yourself, since it is plain GDScript in your project.
- Is there a free version?
- Yes. 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.
Free to download for Windows, macOS and Linux. Get the runner running, then tune it.
Download Flockbay free