A game maker for education, and what it actually teaches

Game development is taught through programming because programming is where the gate is. That has a cost that is easy to miss. A course that spends its first half on loops, variables and collision handling spends its second half on whatever time is left, which is rarely enough to reach design at all. The learners who make it through are the ones who were going to be fine anyway.

Flockbay moves the gate. Flockbay writes the GDScript inside the learner's project and builds the world it runs in, from a brief the learner approved; the learner plays it and decides whether the result is right. What is left is not a smaller subject. It is a harder and more interesting one: how a space teaches a player, how difficulty should ramp, why a mechanic that reads well on paper is boring in the hand.

This is not an argument against teaching programming. It is an argument that a game course and a programming course are different courses, and that pretending they are the same one is why so many game courses produce so few games.

More on this: Making a game with no experience: what you skip and what you do not

They specify a place. Which kind is settled before anything exists: Flockbay reads 2D or 3D from the learner's description and creates nothing until they confirm it. Then it asks 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. That brief is a design document the learner has to read and approve before anything is built, and it is worth marking on its own. Then Flockbay builds it. In a 3D project the place is terrain, water, weather, plants and characters, as real nodes in Godot's scene tree, with the behaviour the brief asked for written in GDScript: what the player can do, what the world does back. Flockbay plays it to check it runs. Then the learner presses play, on their own machine, and finds out whether it is any good.

A 2D project is the same app, the same editor and the same chat, with the ground working differently. Flockbay lays tile ground cell by cell, and the tiles, the edges and the collision all fall out of which cells are ground; a learner who wants a ledge one cell lower can paint it themselves with Paint, a button around the Godot editor's 2D view. Whether that ground stops a walker is a property of the material rather than of the drawing, so identical cells make a platformer's solid block or a top-down path. Sprites go down at an exact position, rotation and scale, placed by Flockbay or with Place in the editor. Side-on and top-down are not two modes to be taught separately either: they are what happens when a world is declared to have gravity or not, which is a more useful thing for a learner to understand than a menu would have been.

The find-out step is where the learning is, and it is the step most tools ration. When getting anything running takes a week, a learner gets perhaps three chances to be wrong in a term. When it takes a minute, they get hundreds, and being wrong quickly and repeatedly is the whole mechanism by which anyone develops taste.

The output is a real Godot project on disk. Not a file that only opens in one tool, and not a saved state on someone's server. A learner keeps what they made and can take it anywhere Godot goes.

Because the code is generated, a learner cannot pass by getting a script to compile. They have to argue for choices: why the level opens in a corridor rather than a clearing, why the enemy is slower than the player, why the music stops at that moment. Those are defensible positions, and marking them is closer to marking a design portfolio than marking a lab.

It also makes plagiarism a stranger proposition. Two learners can be handed the same generated code and produce entirely different games, because the code is not the artefact. The brief they approved and the decisions they made after every play are.

Nothing here treats learners as unable to judge quality. A fourteen year old has played more games than most people who teach the subject. What they usually lack is a way to act on that judgement fast enough for it to compound, which is the thing being removed.

Flockbay is a desktop app for Windows and Linux. It is installed on the machine and it is not available as a web tool. Building needs an internet connection because the chat, asset generation and world data come over the network; playing a finished build does not.

Flockbay is free, AI included: free hosted AI every day, or your Claude or ChatGPT plan, your own agent, or an API key. There is no seat or site licence to buy, and the hosted AI each account gets every day costs nothing, so an institution has nothing to budget for unless a learner chooses a plan for more hosted AI or connects their own AI.

The engine underneath is Godot, open source, the same engine used outside education. Learners are not being taught on a scale model of the real thing.