How to make a 2D game without learning to code

Every 2D game splits the same way. There is the layout — where the ground is, where the gap is, how far the jump has to carry, where the enemy stands so that the player sees it a beat before it matters. And there is the code — gravity, collision response, the state machine that decides whether you are running or falling or hurt.

The layout half is where most of the design lives. The code half is where most first attempts die: describing what should happen is quick, and typing it out is the slow part, especially if you have never written GDScript.

Flockbay takes both halves. Creating a project settles which kind of game you are making, 2D or 3D, read from your description and shown to you before anything is created. Pick 2D and it is the same app, the same chat and the same Godot editor: 2D is a setting the project carries, not a second product. Flockbay's AI agrees a brief with you, lays out the level with its 2D world tools, writes the code inside your project, and plays the result before it hands it over. What it cannot take is the judgement. Whether that gap is the right width is answered by playing it, and that part is yours.

More on this: Building a metroidvania when the map is the design

Before anything is built, Flockbay asks what you are making, one round of questions at a time, each with a recommendation and a line of why. Then it writes a brief: what gets built first, what comes after, and what is not in this version. Nothing is built until you approve it.

Then the first playable arrives: painted ground, a band of scenery along the horizon, and a player controller that walks, falls and jumps under the keys you press. That matters more than it sounds, because the first hour of most 2D projects goes on getting a rectangle to move without catching on the corner of a wall. Starting from something that already moves means the first question in front of you is a design question — is that gap the right width — rather than a plumbing one.

What it does not do is guess your game. It builds what the brief says, not a genre template. Everything after that is the same work every project has: deciding what your rooms are for.

More on this: AI map generator for games: a real Godot world you can keep editing

Ground is painted, by Flockbay's world tools or by you with the same Paint button around the editor's 2D view. Cells are laid and erased, and the tiles, the edges and the collision all follow from which cells are covered. Nobody picks corner pieces out of a palette; you say where the ground is and the matcher works out the rest. Because it is a pure function of that coverage, painting the same cells in a different order draws the same world, and a rebuild never reshuffles edges you already liked.

The same painting covers a platformer's blocks and a top-down game's paths. Whether ground stops a walker is declared per material, so the two are drawn identically and only one of them stops anybody.

On top of that go sprites and scenes from your project, each at an exact position, rotation and scale. A picture sits on its own drawn bottom-centre rather than on the corner of its file, so a crate stands on the ground instead of hovering by however much transparent margin came with it, and draw order follows the same point — a thing lower down the screen is in front. The Catalogue is mostly sprites, 55,073 of its 60,648 objects, searchable by name with a picture of each, and your own art works too because it is a normal Godot project underneath.

The camera is framed by three boxes in the editor's 2D view: what is in view, the dead zone the player can move inside before it follows, and how far it may scroll. The scroll limits follow the painted ground until somebody drags them.

None of this is a script. It is cells, positions and boxes in a viewport, the same way level design has worked since before there were engines. That is why the AI can lay a level out reliably, and why you can take over any single call by hand: a ledge one cell further out is one drag with Paint, and Godot's undo takes it back. A sentence gets you a room; your hand can get you the exact room.

More on this: AI 2D game generator: the scenes and the code are generated, the feel is not

You say what should happen. The player should double jump. The spikes should send you back to the last checkpoint. The key should open the red door and only the red door. Flockbay writes the GDScript that does it, inside your Godot project, in files you can open if you ever want to.

Before it hands the game back, it plays it: it runs the game, sends input events, reads stdout and the debugger, GDScript parse errors included, and captures the viewport. A jump that never leaves the ground reaches Flockbay before it reaches you.

You are not asked to read the code, and you are not asked to approve a diff you cannot evaluate. You are asked to play the game and say whether the jump feels right. It usually will not on the first try, because jump feel is a taste judgement and taste is the part you supply. So you say it feels floaty, and it gets revised, and you play it again.

For the player controller's movement, that revision is usually not new code at all. Walk and run speed, how long it takes to reach a speed and how long to lose it, air control, gravity, jump apex, body size and step length are controls on the character body, so making it feel heavier is a retune rather than a rewrite. The walk cycle advances by distance travelled, which is why the legs stay with whatever speed you settle on instead of skating.

That loop is the work. It is not a fallback for when the AI fails.

More on this: AI level generator: generate the ground, place the meaning

Flockbay is downloaded and installed on Windows, macOS or Linux. There is no browser version. For a small 2D game that might sound like unnecessary friction, and for the first ten minutes it is.

What it buys you is that the game runs on your machine, on the copy of Godot that ships inside the app, at your machine's framerate. A 2D game with a few hundred particles and a screen full of sprites is not a strain locally and is a strain in a tab. It also means the project on your disk is a normal Godot project rather than a save file on someone else's server.

Building does need an internet connection. The chat and asset generation come over the network. Playing what you built does not.

Install the app, describe a 2D game in a sentence, answer the questions, and approve a small brief. Play the first playable when it arrives. The jump will feel wrong, because a first gravity picked for nobody in particular always does. Say so, it gets retuned, play it again. That is the whole first stretch, and none of it is setup.

Then get one room right. Not a game, one room: jump distances that read clearly, one hazard, one reason to go left instead of right. Say what is wrong, or drag the ledge yourself when that is quicker. By the end of that you will know whether you enjoy this, which is more useful than a finished tutorial project you did not design.

The second afternoon is where a game starts, because by then you are not fighting the tool, you are making decisions about your game.

Easier: everything to do with space. No lighting rig, no navigation mesh, no terrain to shape, and you can see the whole level at once while you edit it. Even the camera is three boxes you drag rather than a problem to solve. That removes a large fraction of what makes a first 3D project slow.

Not easier: art volume. A 3D character can be viewed from any angle from one model. A 2D character needs a drawing for every direction it faces and every thing it does, and the frames add up fast. Flockbay can generate a picture, sprites included, but an animation set is many drawings that have to agree with each other frame to frame, so plan for frames from the Catalogue or from your own hand.

The practical response is to keep the character simple and the animation count low until the game is proven. A rectangle that moves beautifully is a better foundation than a beautifully drawn character that moves badly, and you can replace the rectangle at any point.