Skip to content

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

By Eduardo Orellana · Updated

Classic RPG makers give you a grid, a battle system and a house style you cannot leave. Flockbay builds a world from a brief you approve, flat or 3D, and writes the systems for it on top of Godot. No code is needed, and you can still reshape any town or road by hand in the Godot editor. Free AI to start: Flockbay's AI and your own Claude, ChatGPT, agent or API key are free for your first build; after that, a plan keeps you building. It runs on Windows, macOS and Linux, on the official Godot engine.

AppImage, x86_64. Ubuntu 22.04, Debian 12, Fedora 39 or newer.

Intel or AMD Chromebook, with Linux turned on.

Download for macOSDownload for WindowsDownload for Linux

What the traditional RPG maker decided for you

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.

A flat RPG keeps the one thing the old tools got right

Say whether your RPG is 2D or 3D and the tools follow. It is the same app either way, the same editor 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 Godot's TileMap panel lays or erases any cell you want changed. The terrains of the layer's TileSet give the edges and the collision, so a path and a wall are painted the same way and only the one with collision stops anybody.

The layer is data in your project rather than something regenerated, which sounds like an implementation detail and is not. Changing one cell changes that cell and nothing else, whether Flockbay painted it or you did, so edges you already liked are never redrawn behind your back — 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, ask for it by name, or move it yourself in Godot's 2D view. Y-sort draws whatever is lower down the screen in front, and a sprite's offset sets where it stands, so a barrel sits on the path instead of hovering by its file's transparent margin.

Where this stops is worth saying plainly. A flat project is built from 2D nodes: a TileMapLayer for the ground, sprites, and a Camera2D. There is no water or weather plugin to lean on in a flat world — rain over a 2D town is an effect Flockbay writes for that one game. If your RPG wants a valley that floods and a storm that arrives, that is the 3D side, with a terrain or weather plugin.

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

Systems get written, not picked from a list

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

Flockbay builds the world, and the exact spot is yours

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 buildings, props and people placed where the brief puts them, with terrain, water and weather from a Godot plugin or from nodes it writes. In a flat world it means a TileMapLayer, a background colour, Parallax2D layers 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 go around the market instead of through it. You can say so, or do it. Godot's own editor is there in the Standard and Full views, 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: AI monster collector game maker: a spreadsheet with a world around it

Scope is the thing that kills RPGs

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.

The practical details

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 your account come over the network. Playing the game does not.

Free AI to start: Flockbay's AI and your own Claude, ChatGPT, agent or API key are free for your first build; after that, a plan keeps you building.

More on this: AI isometric game maker: a camera decision, not an art style

A starting project for this is the RPG game templates. The design note that goes with it is how the Japanese RPG took shape.

Questions

Can I make a turn-based RPG?
Yes. Turn-based is a set of rules to describe rather than a mode to select, so it is no more or less supported than real-time.
Is it 2D or 3D?
Whichever your game is, and neither is a mode of the other. A 2D project gets painted tile cells, a character body with the camera on it, and sprites at an exact position. A 3D one is built from 3D scenes, with terrain, water or weather from a Godot plugin when it needs them. Same app, same editor, the same chat.
Does it do isometric?
No. Isometric is being worked on as a fixed 3D camera and it is not shipped, so nobody should plan an RPG around it yet. A 2D project here is flat, and a 3D one is a world you move a camera through.
Do I need to know GDScript?
No. Flockbay writes it inside your project. Your job is to play the game and judge whether the systems feel right.
Can I import my own character art?
Yes, and it is a normal Godot project underneath, so ordinary files work. The Catalogue is the other route — mostly sprites, 55,073 of its 60,648 objects. The gap worth knowing about is animation: a single flat picture can be generated on request, a multi-frame animated character cannot, so those frames come from the Catalogue or from you.
How is this different from an RPG Maker template?
A template gives you working systems you must design around. Here the systems are written to your description, which is slower to start and has no ceiling.

Free to download for Windows, macOS and Linux.

Download Flockbay free