A Scratch alternative for when the blocks stop being enough

Scratch teaches programming, and it teaches it well. Loops, conditionals, variables, events and message passing are all visible as physical shapes that only click together when they make sense. That is a real pedagogical achievement and no AI tool replaces it.

It is also free forever, needs no installation, works on a school laptop, and has a sharing culture where you can look inside any project on the site. For a classroom, for a nine-year-old, or for anyone whose goal is to understand how code works, Scratch is the right answer.

Stage Engine is not a better Scratch. It is a different thing, aimed at a different moment, and it is worth being clear about which moment that is.

Usually it arrives as a specific frustration. The sprite-and-stage model is 2D, and the game in your head is a place with distance in it. Or the block script has grown to forty blocks and scrolling it is harder than the idea it encodes. Or you want the thing to look like a game people play rather than a project people look at.

That is the point at which the standard advice is "now learn a real engine", meaning learn to write code in Unity, Unreal or Godot. It is good advice and it costs months, and a lot of people stop there.

Stage Engine exists for the other route: keep not writing the code, but stop being inside a teaching tool.

A desktop app for Mac and Windows. You download it and install it, which is the first honest difference from Scratch — there is no browser version, and there will not be one, because the game runs locally on the copy of Godot that ships inside the app.

Godot is open source and games ship on it. Your project is a Godot project, so when you eventually do want to learn to code, the thing you have been building is the thing you would learn on.

Instead of blocks, there is a builder where you place terrain, water, weather, buildings and characters by hand, and Director 1, which writes the GDScript for the behaviour. You describe what should happen and then play the result.

You lose the teaching. Blocks make the logic visible; generated GDScript does not, unless you go and read it. If the goal is a child learning to program, Scratch is doing something here that Stage Engine deliberately does not.

You lose the zero-friction start. There is an install, an account, and a machine requirement, because a 3D engine is a real program.

You lose the offline case for building. Director 1, asset generation and world data all come over the network, so building needs a connection. Playing what you built does not.

The question to ask is what the lesson is. If the lesson is programming — sequence, condition, loop, state — then blocks are the instrument and nothing here improves on them. Generated code hides exactly the thing you are trying to teach.

If the lesson is design, or level building, or finishing a project, then the calculus changes. Students who can judge a game but cannot yet write one can get much further in a term, and the work they produce is theirs to be proud of.

The practical constraints are real: it installs per machine on Mac or Windows, it needs an internet connection while building, and there is no seat or classroom pricing because it is a desktop app rather than a service. Weigh those before committing a term to it.

Someone who has made several Scratch projects, wants their next one to be 3D, and has no intention of spending a term learning a scripting language first. Also someone teaching older students who are past the point where the blocks are the lesson.

The download is free and there is a free plan. Indie is $10 a month and Pro is $50, and those buy more usage rather than a different engine. There is no classroom or seat pricing — it is a desktop app you install per machine.