A no-code RPG maker that does not come with an RPG in it

The old tools work, and a lot of good games came out of them. But they arrive with opinions baked in: a tile grid, turn-based combat, a party of four, a menu layout, a specific art scale. Working with the grain is fast. Working against it is where people give up.

The tell is that games made in them are recognisable at a glance. That is not an insult, it is just what happens when the systems are the product rather than something you specify.

The grid usually gets the blame for this, and the grid is not the culprit. Tiles are a perfectly good way to build a town — every 2D Zelda is a tile world, and so is Stardew Valley. What locks a game in is the battle system, the party size, the menu layout and the stat model arriving already written, so that the design has to be negotiated with software that has already decided.

So the question is not whether you get a grid. It is whether anything about your RPG is settled before you arrive. If what those tools decided happens to be what you wanted, use them; they are mature and they are good at it. If your RPG is real-time, or has an economy nobody designed a template for, you need something where the systems get written rather than chosen.

Say whether your RPG is 2D or 3D and the tools follow. It is the same app either way, the same world tools and the same chat — 2D is a setting the project carries, not a second product.

In 2D a top-down RPG gets the thing the old tools were right about: painted ground. Flockbay paints it from the brief, and Paint in the Godot editor's 2D view lays or erases any cell you want changed. The tiles, the edges and the collision all follow from which cells are covered — the matcher works out which of sixteen drawn tiles each cell needs, cut from the nine pieces a tile pack already ships. Whether ground stops a walker is declared per material, so a path and a wall are painted identically and only one of them stops anybody.

The matcher is a pure function of that coverage, which sounds like an implementation detail and is not. It means painting the same cells in a different order draws the same world, whether Flockbay painted them or you did, and that a rebuild never reshuffles the edges you already liked — the failure that makes people stop trusting a tile tool.

Towns, props and characters go on top as sprites at an exact position, rotation and scale, out of the Catalogue Flockbay builds from, which is mostly sprites: 55,073 of its 60,648 objects. When you want one barrel exactly here, the Place tool's Asset Browser in the editor searches the Catalogue by name with a picture of each. A picture stands on its own drawn bottom-centre, so a barrel sits on the path instead of hovering by however much transparent margin its file carries, and whatever is lower down the screen draws in front.

Where this stops is worth saying plainly. A flat world has four things: ground, what is beyond it, the person, and the objects placed on it. There is no isometric camera, and no water or weather tool, because those families have no answer in a flat world — rain over a 2D town would be an effect written for that one game rather than a world tool. If your RPG wants a valley that floods and a storm that arrives, that is the 3D side.

More on this: AI city builder maker: simulation you can watch

You describe how the RPG works and Flockbay writes the GDScript in your project. Levelling that rewards use rather than kills. A reputation system that makes one town hostile. Loot tables that thin out once you outgrow a region. A dialogue tree that remembers a decision from four hours ago.

None of those are options on a menu, because there is no menu. They are behaviours described and then implemented, which is why the design does not have to fit a shape anyone anticipated.

You are not asked to read the code, though it sits in your project and you can. Flockbay runs each change itself first, sending input events and reading the debugger, so what reaches you has already run. You are asked to play the result and say whether the levelling curve feels flat, whether the town reacts the way you meant, whether the fight is too long.

More on this: AI JRPG maker: the systems are the easy half

RPGs live or die on place. The route out of the starting village, the moment the mountains come into view, the shortcut you find on your third pass through the woods. That is spatial work, and it starts in the brief: which region comes first, what is in it, and what waits for a later version.

Flockbay builds from that. On the 3D side it means terrain sculpted and painted, water that fills the valley, weather set rather than hoped for, plants, buildings, props and people placed where the brief puts them. In a flat world it means painted tile ground, a sky colour, one band of scenery along the horizon, and everything else placed on top. All of it is nodes in Godot's scene tree, and Flockbay plays it before you do.

Then you walk it, and some of what you find is pure taste: the bridge should sit further downstream, the road should bend around the hill instead of over it. You can say so, or do it. The same world tools are buttons around the Godot editor's own view, which behaves like a level editor, so you move the bridge yourself and Godot's undo takes it back. A sentence gets you a road out of the village; your hand can get you the exact bend in it.

Quest logic, NPC behaviour, combat and geography all come from Flockbay. Whether any of it is good comes from you, and that split holds for most of what you will build.

More on this: A monster collector is a spreadsheet with a world around it

Every RPG project dies the same way: the map got bigger than the number of hours available. No tool fixes that, and it would be dishonest to claim this one does. Building the world and writing the code faster removes two bottlenecks and leaves the others in place — content, balance, and the hours it takes to play all that place and judge it. It is also why the brief Flockbay writes names what is not in this version: an RPG the size of the one in your head gets the truth and a smaller first region.

What it does change is how cheap it is to find out that an idea is wrong. If the crafting system is dull, you know within an afternoon instead of a fortnight, and cutting it costs you an afternoon.

Flockbay is a desktop app for Windows, macOS and Linux. Godot ships inside it, so the game runs locally on your own machine at your machine's framerate. There is no browser version and no streaming.

Building needs an internet connection. The chat, asset generation and world data come over the network. Playing the game does not.

Flockbay is free, AI included: free hosted AI every day, or your Claude or ChatGPT plan, your own agent, or an API key.

More on this: Puzzle games need a prototype in an hour, not a fortnight