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.

Flockbay changes what support looks like. Flockbay writes the GDScript inside each student's project. Flockbay builds the world too, and before it hands anything back it runs the game, sends it input and reads the debugger, GDScript parse errors included. When something still 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 says what they want to make, Flockbay reads 2D or 3D from it and creates nothing until they confirm. Then it asks its questions, one round at a time, each with a recommendation, and writes a brief: what gets built first, what comes after, what is not in this version. Nothing is built until the student approves it, and that brief is where your constraint becomes concrete. Then Flockbay builds it, terrain, water and a character in 3D, checks that it runs, and the student plays it on their own machine.

A 2D game's first build is usually playable straight away: ground to stand on and a player controller who walks, falls and jumps. So the judging starts early in the lesson rather than at the bell. A student who wants one ledge exactly so can paint those cells themselves, because the same world tools are buttons around the Godot editor's view, with undo. Either way 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.

More on this: A game maker for students with a deadline

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 brief they approved, a world built to it, and a set of decisions after every play, and all of it 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 brief 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 Windows and Linux, installed per machine. No browser version and no tablets, and Chromebooks only where IT turns on their Linux environment. 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 site licence to buy and no teacher dashboard. Flockbay is free, AI included: free hosted AI every day, or your Claude or ChatGPT plan, your own agent, or an API key. For a class, the app itself costs nothing.

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.