Skip to content

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

By Eduardo Orellana · Updated

Removing an axis does not make a game simpler, it makes every remaining decision more visible. Side scrollers are precise, and precision comes from iteration. 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.

Download for macOSDownload for WindowsDownload for Linux

The simplicity is a trap

A side scroller looks like the easy option. Two directions, a floor, some gaps. In practice it is the genre with the least room to hide. Every jump arc is fully visible to the player, every gap is measured by eye, and a movement system that is slightly wrong is obvious within one screen.

Compare that with a 3D game, where a loose jump can pass unnoticed because the player is dealing with a camera and a third dimension. Side scrollers offer no such cover. They are simple to start and demanding to finish.

That makes iteration speed the deciding factor, which is what Flockbay is arranged around.

The first screen plays before you have touched anything

The brief settles 2D or 3D before anything is built, along with what the first version is: one movement idea, a few screens, and what comes later. Approve it and Flockbay builds the first screen: a TileMapLayer with a ledge in it, a Parallax2D backdrop, and a player controller that walks, falls and jumps under the keys. It runs the game itself first, sends input events and reads the debugger, so the first screen you get to have an opinion about is one that already plays.

The ground is a TileMapLayer. Its TileSet's terrains give the edges and the collision, so nobody goes looking for the right corner piece, and every block is solid the moment it appears. When you want the ledge wider yourself, Godot's TileMap panel lays cells as you drag and erases them with a right-click drag, and Godot's undo takes it back.

Everything standing in that screen is a sprite at an exact position, rotation and scale, and most of it comes out of a library of ready-made objects: 55,073 of its 60,648 objects are sprites. A sprite's offset puts its base on its origin rather than the middle of its file, so a crate stands on the ledge instead of hovering by however much transparent margin the file happens to carry.

More on this: AI top down game maker: the camera that shows everything

Movement is argued with before it is written

A good deal of how the body feels is already there as settings on the player controller rather than code. Walk and run speed, how long it 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 a rewrite, and 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.

The rest Flockbay writes as GDScript in your Godot project: the fall that is faster than the rise, coyote time, jump buffering, wall behaviour, ledge forgiveness. Every one of those is a number that changes how the game feels, and none of them are things you should have to name in advance.

You will not tune any of it by reasoning. You will tune it by jumping onto the same ledge forty times and saying it still feels heavy. That is a real specification here and it is one you can give without reading a line of code.

The camera deserves the same attention, and gets less of it in most projects. In a flat project it is framed by three boxes: what is in view, the dead zone the player can move around inside before anything scrolls, and the limits the view will not pass. Flockbay sets them, and they are the Camera2D's values in the Inspector when you want to set them yourself. A side scroller with a bad camera plays badly even when the controller is right.

More on this: Puzzle platformers fail in the seam between the two halves

Layout is the design, so every screen gets played

Flockbay lays out the level from the brief, and the layout is where the design happens: what the player is taught in the first screen, what the third screen tests, how far the checkpoint is from the hard part. Those are the decisions you judge by playing. When a platform is a tile too far, move it yourself in Godot's 2D view; when the whole third screen is wrong, say so and it gets rebuilt.

Godot handles both 2D and 3D, and side scrollers exist in both. A 2.5D side scroller — 3D geometry with the camera locked to one axis — is a 3D project with a constrained camera rather than a flat one, and it is a real choice if you want terrain, water and weather sitting behind the plane the player runs along. It is the other option, not the recommended one. When the game is the jump, which in this genre it usually is, flat is the shorter road to finding out whether the jump is any good.

More on this: A Stencyl alternative where the blocks go and the 2D stays

What you are getting

A desktop app for Windows, macOS and Linux, installed on your machine, with Godot bundled so the game runs locally. Consistent framerate matters unusually much in a genre where the player is timing jumps, and running locally is what gives you it.

Building needs an internet connection, because the model and asset generation come over the network. Playing what you built 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: How to make a 2D game without learning to code

The first screen is the tutorial whether you like it or not

In a side scroller the player learns entirely by moving right and finding out what happens. Whatever is in the first screen teaches them the rules, so it teaches them something whether you designed it to or not. A gap that can be cleared without thinking teaches that gaps are free.

The classic sequence is introduce, repeat, complicate, test. Show the mechanic somewhere safe. Ask for it again. Combine it with something known. Then demand it under pressure. That structure is decades old because it works, and it is invisible to players, which is the point.

You author that through the brief and through playing: say what the first screen should teach, play what Flockbay builds, and move the gap yourself if it is still free to clear. It is also why you should get a few screens built and play them before adding a second mechanic. A side scroller that teaches one thing well is better than one that introduces five and explains none.

Checkpoints are part of the difficulty

How far the player is sent back matters as much as how hard the jump is. The same sequence can be a satisfying challenge or an infuriating one depending entirely on whether failing costs three seconds or ninety, and this is the single most common thing new side scroller designers get wrong.

Generous checkpointing lets you build harder content, because attempts are cheap and the player stays in a rhythm. Sparse checkpointing makes ordinary content feel punishing. Decide which game you are making, then place them deliberately rather than at convenient intervals.

Questions

Is it 2D or 3D?
Whichever the brief settles on, before anything is built. A flat side scroller gets a TileMapLayer, a Parallax2D backdrop and a player controller that walks and jumps. A 2.5D one is a 3D project with the camera locked to an axis, which buys you terrain, water and weather behind the action.
Can I use pixel art?
Yes, and the grid suits it, though nothing here tells you what style to work in. Flockbay's library of ready-made objects is mostly sprites, Godot's own shapes work for blocking out, and your own files drop in because it is a normal Godot project. What it will not generate is an animated sprite (no frames, no sheet), so anything that has to move through drawn poses comes from your own files or an artist.
Do I need coding skills?
No. Flockbay builds the levels and writes the code. You judge how the movement feels.
Does it run in a browser?
No. It is a desktop app for Windows, macOS and Linux, and the game runs locally on the bundled Godot.
How much does it cost?
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.
Should I build the levels or the movement first?
Movement, but only just, and in a flat project the first build gives you both, so it is really a question of which you change first. Get the body roughly right, then get a screen built, because the screen is what tells you whether the body is right.

Free to download for Windows, macOS and Linux. Tune the jump until it is right.

Download Flockbay free