GDevelop alternatives: a short survey

Five tools people move to from GDevelop, what each is actually good at, and the one question that decides which of them is yours.

The question that decides it

Before comparing anything, answer this: are you leaving because the tool cannot do what you want, or because the way you have to tell it what you want has become unpleasant? Those lead to completely different places.

If it is capability — you want 3D, or performance a web export cannot give you — you need a different engine. If it is the event sheet turning into an unmaintainable program, another visual scripting tool will hand you the same problem in a different colour, and you need a different way of specifying behaviour altogether.

Construct 3

The closest relative. Browser-based, extremely polished, and its event system is arguably the best-executed version of the idea. If you like how GDevelop thinks and want a more refined version of the same thing, this is the swap with the least friction.

It is subscription-priced and it is 2D and web-first. You are not solving a capability problem here, you are buying polish. Which is a legitimate purchase.

GameMaker

A step toward being a programmer. The 2D authoring tools — rooms, sprites, tiles — are excellent, and it has a long record of shipped commercial games, which is not nothing when you are choosing something to spend two years in.

The cost is GML. You will be writing code. If the code was the thing you were avoiding, this is a sideways move.

Godot on its own

The default serious answer. Open source, no licensing risk, strong 2D and capable 3D, and a large community. Nothing about it will run out from under you.

It also asks you to write GDScript. For someone leaving GDevelop because the events got heavy, that is a real option — you trade a leaky abstraction for a real language. For someone who never wanted to program, it is the wall in its most direct form.

Unity and Unreal

Both can build anything, and both are far heavier than a solo project needs. The learning curve is measured in months and the complexity does not scale down for a small game.

Pick one of these if you specifically need something only they have. Do not pick one to escape an event sheet.

Stage Engine

A desktop app for Mac and Windows built on Godot. You build the world by hand — terrain, water, weather, buildings, characters — and Director 1 writes the GDScript for behaviour inside your project. You play it locally on the bundled Godot and say what is wrong, and it changes.

It answers both versions of the leaving question at once: there is no visual program to maintain because you are not maintaining the program, and 3D worlds are the default case rather than a stretch. What you end up owning is a real Godot project in a folder.

The costs are real. It is a download rather than a browser tool. Building needs a live internet connection, because Director 1, asset generation and world data come over the network, though playing what you built does not. And GDevelop is free outright where this has a free plan with Indie at $10 a month and Pro at $50 for more usage.

Questions

Which is closest to GDevelop?
Construct 3. Same idea, more polish, subscription pricing, still 2D and web-first.
Which one gets me out of visual scripting entirely?
Godot if you are willing to write GDScript yourself, or Stage Engine if you would rather describe what you want and have Director 1 write it.
Is anything here free?
Godot is free and open source. Stage Engine is free to download with a free plan and paid tiers at $10 and $50 a month for more usage. Construct and GameMaker are paid.
Can any of them import a GDevelop project?
No. Moving between any of these means rebuilding.
Which is best for a 3D world?
Godot, Unity or Unreal if you are programming. Stage Engine if you are not.