A game maker for beginners that does not start with a tutorial

Ask someone who tried to make a game and gave up where they stopped, and it is almost never at the idea. It is somewhere around hour six, in a text file, trying to work out why the character falls through the floor. The idea was fine. The world they had in their head was fine. What ended it was a class of problem that has nothing to do with the game and everything to do with the language it was written in.

That is worth naming clearly, because most tools sold to beginners solve the wrong half. They simplify the engine. They give you fewer options, smaller scenes, a shorter menu, and call the result approachable. You still have to assemble behaviour out of blocks or events, which is programming with the syntax filed off, and you still hit the same wall a few weeks later with less underneath you when you do.

Flockbay takes the code away entirely rather than making it smaller. Flockbay writes the GDScript, inside your project. You do the world, the design and the judging. Nothing about the engine is reduced to make that work.

More on this: The best game engine for beginners depends on one question

You download the app for Windows, install it, and start a new project. The first thing it asks is which kind of game, 2D or 3D, shown as two pictures. There is no default and nothing is created until you pick one. What opens either way is a builder — a view of a world you can move around in and place things into. Not a blank code editor, and not a chat box with a cursor blinking in it.

Pick 2D and the first minute is already a game. There is a sky, a band of scenery along the horizon, ground with a ledge cut into it, a platform floating off to one side, and a person who walks, falls and jumps under the keys you are already pressing. For a beginner that is the useful place to be standing, because the first thing asked of you is not a tutorial, it is an opinion: the jump is floaty, that platform is too far out. Widening the ground is dragging across it — ground is a tile layer, so you drag to lay cells and drag to erase them, and the tiles, the edges and the collision all follow from which cells are ground.

Pick 3D and the first hour is shaping instead. You raise some ground. You put water in the low part. You drop in a character. Then you say what should happen: the character can walk and jump, the water slows them down, night falls after ten minutes. Flockbay writes that. You press play and the game runs on your machine, and you find out whether ten minutes is too long.

It usually is. That is the loop. You play, you decide it is wrong, you say what is wrong, it changes. Nobody expects you to get the numbers right in your head, which is the other thing beginner tutorials quietly assume.

More on this: A beginner engine that does not have to be outgrown

Not writing the code does not mean not making the decisions. It means the decisions you make are about the game. Is the jump satisfying. Is the forest too empty. Does the first minute tell the player what kind of game this is. Those are the questions that separate a game people play from a game people close, and none of them are answered by knowing a language.

This is the part beginners are usually told they are not ready for, and it is backwards. You have played games your whole life. You know when something feels wrong long before you know why. That instinct is the qualification, and it is the one part of this that cannot be handed to a tool.

So the work is real, and it is work you can actually do on day one. You will play your own game and dislike it. You will go back in. That is not a sign you picked the wrong tool.

More on this: How building a game with AI actually goes

The engine is Godot, which is open source and which commercial games ship on. Your project is a real Godot project sitting in a folder on your disk. That matters for a beginner in one specific way: the thing you learn on is not a toy version of the thing professionals use, so the first time your ambition outruns the tutorial you are not forced to start again somewhere else.

Flockbay is a desktop app, so the game runs locally at your machine's framerate. Building needs an internet connection, because the chat, asset generation and world data all come over the network. Playing what you have built does not.

The download is free and so is the builder. Flockbay is free on your own AI: your Claude or ChatGPT plan, your own agent, or an API key. Flockbay builds from a library of ready-made objects, or with Godot's own shapes. Every beginner is using the same engine as everyone else.

More on this: A game maker for kids, with the grown-up details up front