Puzzle game maker: the rule is the game, and the rule gets written

Good puzzle games usually rest on a single mechanic that turns out to be deeper than it looks. Boxes that can only be pushed. A light that reveals one thing and hides another. Time that runs backwards in one room. The design work is finding out what the rule can do.

That means the rule has to be cheap to change. If altering how the mechanic behaves takes an afternoon of code, you will test three variants. If it takes minutes, you will test thirty, and the thirtieth is usually the good one.

Director 1 writes the rule as GDScript in your project. You describe the mechanic, you play it, you say what should be different, and it rewrites. That cycle is the entire reason this is useful for puzzles.

Nobody generates good puzzle levels from a description. A level is a specific arrangement that makes exactly one insight necessary, and every element in it is placed deliberately. Generated levels are solvable and boring.

So you build them. Place the geometry, the objects, the doors, the pressure plates, by hand in the builder, on a Mac or Windows desktop with a mouse. Then you play your own level, which tells you almost immediately whether the insight lands or whether there is a stupid shortcut you did not see.

The other half of level design is order. Which puzzle teaches the thing the next one requires. That ordering is judgement and it is yours.

You will get worse at judging your own puzzles the more you build them, because you already know the answer. That is a known hazard of the genre and no tool fixes it.

What helps is that the game runs locally as a real build, so handing it to a friend is a normal thing to do. Watching somebody get stuck in a place you thought was obvious is worth more than any amount of solo tuning.

When they get stuck in the wrong place, you come back and change the rule or the room. Usually the room.

Stage Engine is strongest with 3D worlds — terrain, water, weather, real space — and a lot of interesting puzzle design lives there. Sightlines, elevation, what you can see from where, what a room looks like from the other side.

That is a different set of tools than a grid-based puzzle maker gives you, and it suits some puzzle ideas much better than others. A tile-matching game is not what this is for. A game about a building you have to understand very much is.

A desktop app for Mac and Windows, free to download, with Godot bundled inside. Games run locally on your machine. Building needs an internet connection because Director 1 and asset generation come over the network; playing does not.

Free plan, Indie at $10 a month, Pro at $50, differing in usage.

You will build puzzles that work, are fair, and are boring. Those are the hardest to remove because nothing is wrong with them, and removing them is usually what turns a set of puzzles into a game.

A useful test is whether the puzzle taught anything or asked for anything new. If it did neither, it is padding, however clever the arrangement is.

The other common cut is the tutorial. Most puzzle games explain too much, because the designer is nervous. Watching one person play without a word from you will tell you exactly how much of your explanation was necessary, and it is usually less than half.