Flockbay vs GameMaker

GameMaker is one of the most proven 2D engines in existence. Games made in it have sold in large numbers and been played for years, which is not a claim a new tool gets to make about itself. When a tool has been shipping commercial products for that long, the rough edges have been found already.

Its drag-and-drop mode is a real no-code path, and GML — its own language — is deliberately small and forgiving, which makes it one of the gentler first languages. The room editor, sprite pipeline and tilemap tools are tuned by long use, and export to desktop, mobile and console is a solved, documented path rather than a project.

If you might one day be willing to write a little code, GameMaker is a strong answer and this page is not going to argue otherwise. Its case rests on GML, on the sprite pipeline and on twenty years of export targets — not on 2D being unavailable anywhere else.

More on this: The best free 2D game engines, and what "free" means for each

Creating a project in Flockbay asks which kind of game you are making. 2D or 3D, shown as two pictures, no default, nothing created until you choose. Both go through the same app, the same builder and the same chat, so the dimension is a setting the builder carries rather than a second product with a thinner feature list.

Pick 2D and the project is already running: sky, 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 press. Ground is a tile layer you paint, and the tiles, the edges and the collision are derived from which cells are ground rather than placed one at a time. Side-on and top-down are not modes to pick between — they fall out of gravity, so declaring it gives you a jump and declaring none gives you a character who steers on both axes, from the same code.

Pick 3D and the subject is terrain, water, weather, a day-night cycle, characters moving through a space with distance in it. Those tools are 3D tools and they have no flat equivalent: a 2D game here has no water and no weather. Say that plainly rather than letting a feature list imply otherwise.

Either way it is a desktop app for Windows with Godot bundled inside it, so your game runs locally at your machine's framerate, and your project is an ordinary Godot project you can open in stock Godot at any point.

And either way there is no language to learn, not even a friendly one. Flockbay writes the GDScript inside your project. You build the scene by hand in the builder and then describe the behaviour you want, play it, and say what is wrong. That is the whole of the difference: GML is a language you learn, GDScript is a language written for you.

More on this: Construct alternatives, sorted by what you are actually leaving for

GameMaker gives you certainty. When you write GML, the thing you wrote is the thing that runs, and if it misbehaves the cause is in front of you. Generated code moves that relationship: you get further faster, and when something is wrong you describe the symptom rather than locate the line.

Flockbay gives you reach across shapes. A 3D world with weather and a populated village is a large project in GameMaker and an ordinary one here. That is not because the engine is better — Godot is not doing anything mysterious — but because the layer on top is built for that shape, and the same layer now covers a flat one.

GameMaker also has the export story, and it is not close. Console and mobile ports are a documented path there. Here the game is a desktop game running locally on Windows, and that is what it is best at.

GameMaker runs on your laptop with the wifi off. Flockbay does not, for building: the chat, asset generation and world data all come over the network, so a connection is required while you work.

Playing what you built needs nothing, because it runs locally on the bundled Godot. But the building half is online, and anyone who works on trains should weigh that before switching.

More on this: Should I use Flockbay or GDevelop?

The reasonable objection to making a 2D game outside a 2D engine is art. You need sprites, and a twenty-year-old engine has a market bolted to the side of it. Half of that objection has an answer now: the Catalogue is 90.8% sprites — 55,073 objects out of 60,648 — searchable by name with a picture of each, and you place one with the mouse at the position, turn and size you want. A picture sits on its own drawn bottom-centre, so it stands on the ground instead of floating by however much transparent margin its file carries, and draw order follows the same point, so a thing lower down the screen is in front.

The half that is still true is animation. Flockbay builds from a library of ready-made objects, or with Godot's own shapes. It cannot generate an animated character, and there is no animation editor here to draw frames in. GameMaker's sprite editor, its frame timeline and its long-established market of animated character sets are squarely ahead, and no amount of AI in the other tool cancels that. If your game is a hand-animated character with twelve states, GameMaker is the honest recommendation.

On the 3D side, art still comes from generation, the web or you, there is no stock library to shop in, and 3D assets remain harder to source than flat ones. Simple geometry can be built directly, which is often the fastest honest way to get something playable before art exists.

More on this: A Defold alternative when you would rather not write Lua

Flockbay is free on your own AI: your Claude or ChatGPT plan, your own agent, or an API key. GameMaker has its own tiers with different limits, so compare against what you would actually use.

Pick GameMaker for console or mobile export, for a character that needs hand-drawn animation frames, or if you suspect you would enjoy learning GML. Pick Flockbay if you have no intention of writing code and you want the game running natively on your own machine — and note that the recommendation is the same whether the game is flat or a place you walk through.