A Construct 3 alternative that does not ask you to give up 2D

By Eduardo Orellana · Updated

Flockbay is free on your own Claude or ChatGPT plan. Claude Pro or Max, or ChatGPT Plus or higher, builds a real Godot project in the Godot editor. Claude Free and ChatGPT Free do not run here. More models are optional, a credit reload at API prices. Windows today. The engine is the official Godot release. Construct 3 is genuinely good at what it does, and what it does is 2D in a browser. Flockbay does 2D on your own machine, which means the comparison stopped being about dimension and is now about the browser, the event sheet, and who writes the code.

What Construct 3 is good at

Start with the part most comparison pages skip. Construct 3 runs in a browser tab, which means it starts on a Chromebook, a school machine or a laptop you do not have install rights on. For teaching, for game jams and for anyone whose computer is not theirs to configure, that is a serious advantage and Flockbay cannot match it.

Its event sheet system is also mature. You build logic as readable rows of conditions and actions, and for 2D games that model has held up for years. Plenty of finished, sold games were made in it. If the event sheet is working for you, changing tools is a cost with no obvious payoff, and nothing below is an argument that you should.

And it exports to HTML5 immediately, so a link to your game is always one step away. That loop is fast and it is hard to beat.

Dimension stopped being the dividing line

The reasonable version of this comparison used to end in one line: Construct is 2D, Flockbay is 3D, and if your game is flat you already have your answer. That line is out of date, and what replaced it is a list of specific things rather than a change of emphasis.

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. It is the same app, the same builder and the same chat either way, so 2D is a setting the project carries rather than a second product you download.

Pick 2D and the first thing on screen is playable. 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 are pressing. That is the starting state, not the reward for finishing a tutorial.

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

Side-on and top-down are not modes you switch between, 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 and there is nothing to jump away from. Same code, one decision.

Where this runs out is animation. Flockbay builds from a library of ready-made objects, or with Godot's own shapes, and the Catalogue is 90.8% sprites — 55,073 objects out of 60,648, searchable by name with a picture of each — but nothing here hands you a walk cycle for a character you invented. If your game leans on a lot of original animation, that part is still yours to make, and Construct will not make it for you either.

More on this: An AI game maker for indie devs who would rather design than plumb

Where the event sheet stops being the easy part

There are three usual reasons to look for an alternative, and dimension is no longer one of them. The first is the logic itself — event sheets are readable until a project gets large, and then a complex behaviour becomes a very long sheet that only you can follow. The second is performance: everything is running in a browser, so the ceiling on how much can be moving at once is set by the tab rather than by your hardware. The third is the project, which only one editor can open.

Flockbay answers those three differently rather than better on every axis. The logic is real GDScript, written by Flockbay, so complexity lives in code rather than in a diagram you have to hold in your head. It is a desktop application for Windows, so the game runs on your machine at your machine's framerate. And what you are left holding is an ordinary Godot project in an ordinary folder, which any Godot developer can open.

More on this: AI that makes games, described accurately

You do not write the code, but the code is real

The point of an event sheet is that a non-programmer can express behaviour. Flockbay reaches the same goal from the other side: the behaviour is expressed in a normal programming language, and it writes it. You say the guard should lose interest after a while and go back to its post. It writes that. You play it, decide the guard gives up too quickly, and say so.

That means there is no ceiling made of available events. Anything expressible in GDScript is expressible in your game, whether or not anybody anticipated it. It also means your project is a Godot project that any Godot developer could open, which is a different relationship to your own work than a file only one editor understands.

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

The trade you are actually making

You give up the browser. Flockbay is downloaded and installed on a Windows PC, so it is not an option on a locked-down machine or a tablet. You also give up the instant playable web link, because what you build is a local game rather than a web build.

You gain the engine. Local performance, real code, both dimensions treated as first-class cases, and a project you own in a format the wider Godot world can read. Whether that is a good trade now turns on how much the browser and the instant link are worth to you, rather than on whether the game in your head is flat.

Building needs an internet connection — the chat and asset generation come over the network. Playing what you built does not.

More on this: Is Flockbay a browser game maker?

Cost, plainly

Construct 3 is a subscription with a limited free tier. Flockbay is free on your own AI: your Claude or ChatGPT plan, your own agent, or an API key. Nothing is held back: there is no better engine to buy, no watermark and no export gate.

There is no team or seat pricing on our side, because this is a desktop app rather than a shared workspace.

More on this: A Buildbox alternative for people who outgrew the drag and drop

Questions

Can I import a Construct 3 project?
No. Construct projects are event sheets and web assets; a Flockbay project is a Godot project. There is no meaningful conversion between them, and pretending otherwise would waste your time. Art you own can be reused.
Is Flockbay better than Construct 3?
For local performance, code you did not have to write and a project any Godot developer can open, this is the better trade. For instant web publishing or working on a machine you cannot install software on, Construct 3 is the better tool and we would say so. Whether the game is 2D is not part of that answer any more.
Does Flockbay run in a browser?
No. It is a desktop app for Windows. Your game runs locally on the Godot build that ships with it.
Do I need to know GDScript?
No. Flockbay writes it inside your project. You judge the result by playing it.
Can I still make 2D games?
Yes, and it is a choice you make when you create the project rather than a fallback. A new 2D project opens playable, ground is a tile layer you paint, and 55,073 of the Catalogue's 60,648 objects are sprites. If an instant web link is the point, Construct is still faster to one.