The whole genre lives in the jump

Nobody reads your platformer description. They press right, they press jump, and they decide. Gravity, jump height, the acceleration curve, how much control you keep in the air, whether a jump pressed slightly before landing still counts. Get those wrong and the level design cannot save it.

The reason so few first platformers feel good is not taste, it is iteration count. When changing gravity means editing a script you barely understand, you try three values and settle. Feel comes from trying thirty.

Stage Engine changes the cost of an iteration. You say the jump is floaty at the top, Director 1 changes the code, you play it again. Thirty iterations is an afternoon.

Every good platformer has a handful of forgiveness mechanics that players never notice and would miss instantly. Coyote time, so a jump still works a few frames after leaving the ledge. Input buffering, so a jump pressed just before landing fires. Variable jump height tied to how long the button is held. Corner correction, so clipping a ledge nudges you around it instead of stopping you dead.

Naming them is not required. Describing the problem is enough: "I keep falling when I swear I pressed jump on the edge." That is a solvable, well-understood problem and Director 1 writes the GDScript for it in your project.

You do not need to read the script to know whether it worked. You need to play it. That loop is the design process, not a workaround for not coding.

Once movement feels right, a platformer is a sequence of small spaces that each teach or test one thing. The gap that shows you the jump distance. The first enemy you must jump over rather than around. The room where the two combine.

That sequence is not something to describe in a sentence and hope. You place it, play it, move the platform two units left, play it again. The builder is a builder for exactly this reason.

Stage Engine is built for 3D worlds with real terrain and weather, so a 3D platformer with real landscape gets a lot from it. A flat 2D platformer works too, since Godot underneath has a proper 2D pipeline, but you will use fewer of the world tools.

Stage Engine is a desktop app for Mac and Windows with Godot bundled inside. Press play and your game runs locally at your own framerate, which for a genre that lives on frame-accurate input is the right way round.

Your project is a real Godot project. It is not a save file only this tool can read, and Godot is open source.

Building needs an internet connection, since Director 1 and asset generation come over the network. Playing does not. Free to download with a free plan; Indie is $10 a month and Pro is $50, and those buy more usage rather than a different engine.

A platformer camera is doing constant quiet work. Leading the character in the direction they are moving so you can see what is coming. Lagging slightly on landing so a fall does not lurch. Holding still in a small room instead of drifting. Looking down when you hold down.

Get it wrong and players will tell you the jump feels bad, because they cannot see the camera and they can see the character. It is one of the most common misdiagnoses in the genre.

It is also code, so it changes when you describe the problem. If a section feels claustrophobic, say so and let the camera pull back before you start rebuilding the level. Testing the cheap fix first is usually right.