A game maker for education, and what it actually teaches
By Eduardo Orellana · Updated
Flockbay is free on your own Claude or ChatGPT plan. Claude Pro or Max, or ChatGPT Plus or higher, builds a real Godot project in the Godot editor. Claude Free and ChatGPT Free do not run here. More models are optional, a credit reload at API prices. Windows today. The engine is the official Godot release. If a tool writes the code, the question becomes what is left to learn. The answer is the part that was always the hard part: systems, pacing, and the judgement to tell good from bad.
The syntax was never the subject
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; the learner builds the world by hand 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
What learners actually do
They build a place. Which kind is settled before anything exists: making a project asks 2D or 3D, shown as two pictures, and it will not create one until the learner picks. In a 3D project the place is terrain, water, weather, buildings and characters, put down directly with their hands in a builder that behaves like a level editor. Then they describe behaviour — what the player can do, what the world does back — and Flockbay writes it. Then they press play, on their own machine, and find out.
A 2D project is the same app, the same builder and the same chat, with the ground working differently. Learners drag to lay tile ground and drag to erase it, and the tiles, the edges and the collision all fall out of which cells are ground. Whether that ground stops a walker is a property of the material rather than of the drawing, so identical strokes make a platformer's solid block or a top-down path. Sprites go down by mouse at an exact position, turn and size. 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.
Judgement is the assessable part
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 world and the decisions 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.
The practical facts
Flockbay is a desktop app for Windows. 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 on your own AI: your Claude or ChatGPT plan, your own agent, or an API key. There is no education, seat or site licence, so any institutional budget is for the AI each person connects.
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.
More on this: A game maker for teachers who are not programmers
Questions
- If the AI writes the code, what is the learner learning?
- Design, systems and judgement — how a world is paced, why a mechanic works, whether the result is any good. Those were always the parts that distinguished a good game, and they were usually the parts a course ran out of time for.
- Can it be used to teach programming?
- Indirectly. The generated GDScript is visible in the project, so a class can read working code that they specified themselves. It is not a substitute for a programming course.
- Is there education pricing?
- No. Flockbay is free on your own AI: your Claude or ChatGPT plan, your own agent, or an API key.
- What are the technical requirements?
- A Windows machine that can install software, and an internet connection while building. There is no browser version and no offline mode for building.
- Do learners keep their work?
- Yes. Each project is a normal Godot project in a folder on the machine.
Related
- Game maker for schools
- Game maker for the classroom
- Game maker for students
- Game maker for kids
- Game maker for beginners
Free to download for Windows.
Download Flockbay free