A game maker for students with a deadline

A term project is maybe forty usable hours, spread thin, competing with everything else. If you are learning a language, wiring input handling and debugging why the collider is offset, thirty of those hours are gone before the game has an idea in it. The thing you hand in is a technical exercise with a title screen.

Take the code and the construction work out and the arithmetic changes completely. You spend the forty hours deciding what the world should be, the pacing and the feel, which is what the project was supposed to be about and what anyone marking it or looking at it later actually responds to.

That is the whole pitch. Not that it is easier. That the time goes to the part that shows.

More on this: A game maker for teachers who are not programmers

You start by saying what you want to make. Flockbay reads 2D or 3D from it and makes nothing until you confirm, and plenty of student projects are the 2D one. Then it asks what it needs to know, one round of questions 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 you approve it, and if your idea is too big for a term, the brief says so and offers a smaller first version. That alone can save a term.

Then Flockbay builds the world. On the 3D side that is sculpted terrain, water, weather, plants, characters and props; on the 2D side it is tile ground, a band of scenery and sprites at an exact position, rotation and scale. A 2D game usually starts playable: ground to stand on and a player controller who walks, falls and jumps under the keys. On a forty-hour budget, not spending the first evening getting something to move is a real line item.

It writes the code too: you describe behaviour and it writes GDScript into your project, then runs the game, sends input and reads the debugger to check its own work. You do not have to read the code, though it is there and it is ordinary. What you do have to do is play the result and say what is wrong, over and over, which is the part that makes a game good. When a fix is pure taste, that ledge one cell lower, that crate by the door, the same world tools are buttons around the Godot editor's 3D and 2D view, so you can make the one change yourself and undo it if it is worse.

The game runs locally on the copy of Godot bundled with the app, at your laptop's framerate. Building needs an internet connection; playing what you built does not. That matters on a library wifi day.

More on this: Using a game maker in the classroom, honestly

A real Godot project in a folder you own. Not an export from a closed tool, not a save file on someone's server. If your course requires you to submit source, you have source. If you want to keep working on it after the module ends, in Godot directly, nothing stops you.

That also matters for a portfolio. A project that opens is worth more than a video of a project. And because Godot is open source and widely used, the thing on your disk is legible to anyone who looks at it professionally.

Being honest about one thing: if the assessment is specifically on your programming, this is the wrong tool for that assessment. Use it for the design module, the game jam, the personal project, the thing you actually wanted to make.

More on this: Idea to game, without the part in between

The download is free, and so is everything in it. 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 student discount: everything you need to build is free, and optional plans add more hosted AI.

Flockbay is a desktop app for Windows and Linux. It installs on your own laptop, which is usually easier than getting anything installed on a lab machine.

More on this: Game maker for schools: the deployment questions