Make the puzzle game you keep describing to people

There is a specific kind of person this page is for. You have a puzzle idea. You have explained it at dinner more than once, with cutlery. You know roughly how the first few levels go. You have never built it because building it means learning to program, and you have looked at that and decided against it, probably several times.

That is a reasonable decision and it has been costing you the game. Programming is a genuine skill that takes a genuine amount of time, and wanting to make one specific thing is a poor reason to spend two years acquiring it.

Stage Engine exists so the decision is not required.

You explain the idea, in the same words you used with the cutlery. Director 1 writes the GDScript that implements it, inside a real Godot project on your machine. Then you press play.

The first version will be wrong, and that is normal and useful. Wrong in a specific way you could not have predicted from thinking about it. You say what is wrong, in plain language, and it changes. Then you play again.

Nothing in that loop requires reading code. It requires playing your game and being honest about it, which you can already do, and which is the skill that actually matters.

This is where a puzzle game becomes a game rather than a demo. Twenty, forty, a hundred small arrangements of the same rule, ordered so that each one teaches something before the next one tests it.

You build these by hand. It is slower than generating them, and it is the reason anyone will finish your game rather than close it at level six. The builder is set up for the rhythm of it: arrange, play, adjust, play.

You will also throw a lot away. Levels that seemed clever and turn out to have a boring solution. That is the job.

Stage Engine is a desktop app you install on a Mac or a Windows machine. It is not a website and there is no browser version. Godot, which is open source, is bundled inside, and your game runs locally on it.

Building needs an internet connection, because Director 1 and asset generation come over the network. Playing what you built does not. There is no offline building mode and it would be a lie to suggest otherwise.

The download is free and there is a free plan. Indie is $10 a month and Pro is $50, and what those buy is more usage, not a better engine or extra features.

Not the tool. The hard parts are the ones that have always been hard: finding out that your idea has one solution that works everywhere, designing the twentieth level when the obvious ones are used up, and finishing something rather than starting the next idea.

You should also expect the first playable version to be less exciting than the version in your head. That is not a sign the idea is bad. Ideas in your head have perfect art, perfect feel and no dead moments. The gap closes by iterating, not by planning harder.

And you will need someone else to play it, early, while you say nothing and watch. That is the single most useful hour in the whole project, and no tool can do it for you.

A twenty level game that exists is worth more than a hundred level game that does not, and not only for the obvious reason. Finishing teaches you the shape of the whole job: the menus, the endings, the pacing, the last five percent that takes a quarter of the time.

You learn none of that from the first forty levels of a game you abandon, and you will make every one of those mistakes again on the next project.

So set an end. Twenty levels, a title screen, an ending screen, and it is done. If the idea deserves a hundred levels, it will still deserve them after you have shipped the twenty and know what you are doing.