A Stencyl alternative where the blocks go and the 2D stays

It took block-based programming seriously as a production tool rather than a teaching aid. Snap-together logic, actors with behaviours, scenes, and games that got published and played. For a lot of people it was the first tool where a game they made left their own machine.

Its behaviour model in particular was well designed. Attaching reusable behaviours to actors is a good way to think about a 2D game, and it scales further than a single script per object does.

If Stencyl is working, there is no argument here. This page is for the two moments when it stops working: when a behaviour outgrows the blocks, and when the next idea does not fit inside a scene.

Blocks are excellent until a behaviour needs twenty of them and a variable whose purpose you have to remember. At that point they have stopped simplifying and started being a slower way to write code.

Dimension is the other reason, and it is the one this page used to lead with. A 2D tool can be pushed toward pseudo-3D but not into a landscape, and the moment your idea involves standing on a ridge and looking down at something, the tool is the wrong shape. That case is served here too. It is just no longer the only case.

The usual advice at the block ceiling is to learn a scripting language. Flockbay exists for people who are not going to.

Creating a project asks which kind of game you are making, 2D or 3D, shown as two pictures. There is no default and nothing is created until you pick one. Same app, same builder, the same chat either way, so 2D is a setting the project carries rather than a second product.

Pick 2D and the first thing on screen is playable: a sky colour, a band of scenery along the horizon, ground with a ledge and a floating platform, and a person who walks, falls and jumps under the keys you are pressing. That is the starting state, not the reward for finishing a tutorial.

Ground is a tile layer you paint. You drag to lay it and drag to erase it, and the tiles, the edges and the collision all follow from which cells are ground rather than being picked out of a palette. Because that is a pure function of the coverage, painting the same cells in a different order draws the same world and a rebuild never reshuffles an edge you were happy with. Whether ground stops a walker is declared per material, which is why a platformer's block and a top-down path are drawn identically and only one of them stops anybody.

The person is a character body with the camera on them, and it is a set of controls rather than a script you inherit. Walk and run speed, how long it takes to reach a speed and to lose it, air control, gravity, jump apex, body size and step length are all values you change, so "make it feel heavier" is a retune. The walk cycle advances by distance travelled, which is why the legs stay with the speed instead of skating. Side-on and top-down are not modes either: declare gravity and down is a direction, so steering is horizontal and a jump is available; declare none and the body steers on both axes with nothing to jump away from.

Everything else in the scene you place by hand — a picture or a scene from your project at an exact position, turn and size. A picture sits on its own drawn bottom-centre rather than on the corner of its file, so a crate stands on the ground instead of hovering by however much transparent margin came with it, and draw order follows that same point, so a thing lower down the screen is in front. The camera is framed by dragging three boxes on the running game: what is in view, the dead zone the player can move inside before it follows, and how far it may scroll. The scroll limits follow the ground you paint until you drag them yourself.

More on this: AI 2D game generator: the code is generated, the game is not

Flockbay writes GDScript into your project from what you describe. Twenty blocks of behaviour is a sentence, and what you do afterwards is play it and say what is wrong rather than trace which block fired.

The engine underneath is Godot, which is open source. Your project is a Godot project in an ordinary folder on your own disk and opens in stock Godot, so nothing is trapped in a format only one tool understands.

You still build the world with your hands. In a flat game that is dragging ground into place and putting sprites exactly where you want them; on the 3D side it is shaping terrain, outlining water and setting the weather. Either way it happens directly in the builder, because that part is taste and pointing is faster than describing.

More on this: Pixel art is a discipline, and the code is still the blocker

It is a desktop app for Windows. There is a download and an install, there is no browser version, and what you end up holding is an ordinary Godot project in a folder rather than a web build someone can click through to.

Building needs an internet connection, because the chat, asset generation and world data all come over the network. Playing what you built does not, because the game runs locally on the bundled Godot.

You lose inspectability. A block stack is visible; generated code is only visible if you open it. It is there — GDScript in your project — but the workflow does not put it in front of you the way blocks are in front of you.

And nothing here animates a character for you. Flockbay builds from a library of ready-made objects, or with Godot's own shapes but not a walk cycle, so frames come from the Catalogue — mostly sprites, 55,073 of its 60,648 objects, searchable by name with a picture of each — or from your own hand. Stencyl did not draw them either, but it is worth being plain that this does not.

More on this: AI 2D game maker: what a working session actually looks like

One place and one idea. A single room with a jump you have to earn, or a stretch of street with a thing that follows you. Small enough to finish in a week and specific enough that finishing it tells you something.

Resist the sequel-sized plan. The reason is not that the tool cannot do it — it will happily build whatever you ask for — but that a large project takes months to reach the point where you learn anything, and a small one takes days.

Once the small thing works, the second project can be three times the size and you will actually know how to steer it. That progression is the same in every tool and it is the part people skip.

The download is free and so is the builder. Flockbay is free on your own AI: your Claude or ChatGPT plan, your own agent, or an API key.

The fit is: someone comfortable with the idea of building a game, no longer interested in assembling the logic themselves, and wanting it to run natively on their own machine. Whether the game is flat is not part of that description any more. What is: if a link someone can click is the point of finishing, a tool that exports to the web is still the better answer and it is worth saying so.

More on this: Point and click is writing, plus a lot of plumbing