An RPG game maker where the systems get written for you

People starting an RPG usually picture the map first. A village, a forest road, a ruin on a hill. That part is genuinely the fun part, and it is the part a builder should let you do directly rather than describe in a sentence.

The rest of the genre is bookkeeping. Health and damage that scale sensibly. An inventory that can hold a thing, drop a thing, and still be right after you reload. Dialogue that remembers what you already said. A quest that knows it is halfway done. None of that is creative work in the sense that placing a forest is, and all of it has to exist before the game feels like an RPG rather than a walk.

Flockbay splits along that line. You build the map. Flockbay writes the bookkeeping, as GDScript, in your project, where it is a real file you could open if you wanted to.

You start in the builder, which behaves like a level editor rather than a chat box. Before it will make anything it asks which kind of game this is — 2D or 3D, shown as two pictures, with no default — and that answer decides what is in your hands from then on.

In a 3D project, terrain gets shaped, water gets placed, weather gets set, and buildings and characters go where you put them. In a flat one, you drag over cells to say where ground is, and the tiles, the edges and the collision are all derived from that, so the village path is walkable as soon as it exists; the village on top of it is sprites placed by hand at an exact position, turn and size. The top-down shape most people picture when they say Zelda or Stardew comes from declaring no gravity, which leaves the character steering on both axes. Either way this is hand work and it is meant to be.

Then you say what should happen. A chest that gives an item. A guard who blocks the bridge until you have the pass. A boss with three phases. Flockbay writes it and you play it. If the boss dies too fast, you say so, and it changes. You are judging the result, not reading the diff.

That loop is the whole method. It is slower than a template and faster than learning GDScript, and it produces a game that is specifically yours rather than a reskin of an example project.

More on this: A character is a model plus everything that makes it move

Every RPG lives or dies on its numbers. How much a sword hurts, how long a fight lasts, how fast you level, how scarce potions are. There is no correct answer to any of those, which is why no tool can hand them to you.

What a tool can do is make them cheap to change. When the combat code is written for you, adjusting a curve is a sentence rather than an afternoon, and you can afford to try the version you were not sure about. Most balance in a role-playing game comes from playing it many times and noticing when a fight stopped being interesting.

You are the one who notices. Not writing the code does not mean not having an opinion about whether the second dungeon drags.

More on this: AI dungeon crawler maker: hand-built rooms, written systems

Flockbay installs on Windows and ships with Godot inside it. Press play and the game runs locally, at your machine's framerate. There is no streaming and no browser tab in the middle.

For an RPG this matters because RPGs get big. A world with real terrain, a day-night cycle and a couple of hundred characters going about their business is not something a browser tool will run smoothly, which is why browser tools quietly point you at the smallest version of whatever you asked for. A flat world hits the same wall later, but it hits it: a painted map with a few hundred things moving on it is still a few hundred things moving.

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

More on this: AI horror game maker: a plan for your first one

Art arrives one of three ways: generation, the web, or you. All three are normal and mixing them is normal too. A village built from generated pieces with two models you made yourself is not a compromise, it is how most small projects actually look. In a flat project there is a fourth route that is usually the first one you take: the Catalogue holds 60,648 objects and 55,073 of them are sprites, searchable by name with a picture of each before you take it.

Simple geometry can also be built directly on the 3D side when that is the honest fastest way to get playing. A grey box that is the right size tells you whether the room works, and it tells you tonight rather than after a week of modelling.

The gap worth knowing before you plan around it is animation. Flockbay can make a single flat still image on request; it cannot make a multi-frame sprite, and there is no animation editor. If your hero needs a six-frame sword swing, those frames come from you or from the Catalogue.

The useful discipline is to postpone art. A dungeon made of grey blocks is playable, and playable is the only thing that tells you whether the design is good. Dressing a bad dungeon does not improve it, it just makes the disappointment more expensive.

More on this: Making a match-3 game without writing the board logic

The download is free and there is a free plan. Flockbay is free on your own AI: your Claude or ChatGPT plan, your own agent, or an API key. There is no better engine to pay for, and no team or enterprise tier — it is a desktop app.

What you keep is a Godot project. Godot is open source and widely used, so the thing on your disk at the end is not a file that only one company can open. If you ever want to hand it to someone who does write code, you can.