A game maker for teachers who are not programmers

The quiet reason game development is rare in schools is not equipment or interest. It is that supporting twenty-five students debugging twenty-five different scripts requires a teacher who can debug, and most teachers who would love to run this project cannot. So the project becomes a unit on game design theory with no game at the end.

Stage Engine changes what support looks like. Director 1 writes the GDScript inside each student's project. When something does not work, the student describes what is wrong and it is rewritten. You are not the debugger of last resort, because there is no queue of broken scripts to work through.

What you are is the person asking better questions about the game. Why does the first minute feel empty. What is the player supposed to learn here. Those you can already do.

The unit of work that produces good results is a place with a constraint. "A corridor that makes the player nervous." "A village that looks like people live in it." "One room, three ways through." Constraints of that shape force design decisions and produce twenty-five different outcomes.

What produces bad results is naming a genre. Ask for a platformer and you get twenty-five platformers that differ only in colour, and you will spend the assessment trying to find something to say about each.

A session fits a period. A student shapes ground, places water and a character, describes what should happen, and plays it on their own machine. The build-play-revise loop completes inside the lesson, which is what makes it possible to teach iteration rather than just tell them about it.

The code is not the artefact, which is inconvenient for a mark scheme built around code and liberating for everything else. What a student produces is a world and a set of decisions, and both can be defended out loud. Ask why the enemy is slower than the player and you get either a designer's answer or a shrug, and the difference is easy to hear.

It also changes the plagiarism picture. Two students given the same generated script produce completely different games, because the difference lives in the world and the judgement rather than in the text file.

And students can read the code if the course wants them to. It is ordinary GDScript in the project, and it works, which makes it a better reading text than most.

It is a desktop app for Mac and Windows, installed per machine. No browser version, no Chromebooks, no tablets. Building needs a live internet connection because the AI, asset generation and world data come over the network; playing a finished build does not.

There is no education pricing, no site licence and no teacher dashboard. Plans are individual: free, Indie at $10 a month, Pro at $50, and paid plans buy usage rather than features. For most classes that means the free plan.

Try it yourself on one machine on the school network before you plan a scheme of work. Twenty minutes will tell you whether the network cooperates, which is the only question that can actually sink the unit.