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.

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

Creating a project asks which kind of game you are making, 2D or 3D. Two pictures, no default, and nothing is created until you pick one. It is the same app either way, the same builder and the same chat — 2D is a setting the project carries, not a second product.

Pick 2D and a top-down RPG gets the thing the old tools were right about: ground you paint. You drag to lay it and drag to erase it, and the tiles, the edges and the collision all follow from which cells are covered — you say where the ground is and 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, 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, placed by hand with the mouse at an exact position, turn and size, out of a Catalogue that is mostly sprites: 55,073 of its 60,648 objects, searchable 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 you place. There is no isometric camera, no water and no weather, because those families have no answer in a flat world — rain over a 2D town is a request that cannot succeed rather than one that is queued. 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. 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 is faster to do than to describe.

So you do it directly in the builder. On the 3D side that means terrain shaped by hand, water that fills the valley you cut, weather set rather than hoped for, buildings and props placed where you want them. In a flat world it means ground painted a drag at a time, a sky colour, one band of scenery along the horizon, and everything else placed on top. Either way it behaves like a level editor, on a Windows desktop, with a mouse.

In a 2D project the camera is part of that hand work rather than a number you have to go and find. You frame it by dragging three boxes on the running game: what is in view, the dead zone the player can move inside before the camera follows, and how far it is allowed to scroll. Those limits follow the ground you paint until you drag them yourself, so a room is bounded by the ground you laid.

Quest logic, NPC behaviour and combat come from Flockbay. Geography comes from you. That split holds for most of what you will build.

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. Writing the code faster removes one bottleneck and leaves all the others in place — content, balance, and the sheer amount of place you have to build.

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. 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 on your own AI: your Claude or ChatGPT plan, your own agent, or an API key.

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