Flockbay vs RPG Maker

RPG Maker: a 2D, tile-based editor with a database of items, skills and enemies, an event editor for logic, and a working battle system on day one. Decades old, enormously documented, with a stock and third-party asset library nothing else in the genre matches. Bought once.

Flockbay: a desktop app for Windows built on Godot, where you pick 2D or 3D as the project is created. A flat project gives you tile ground you drag on and drag off, a character with the camera on them, and sprites placed by hand; a 3D one gives you terrain, water and weather. Flockbay writes the GDScript for behaviour. No default battle system, no item database, no event editor. Flockbay is free on your own AI: your Claude or ChatGPT plan, your own agent, or an API key.

RPG Maker wins this, clearly. Its defaults are a complete small RPG: a party, a menu, a battle screen, saves. You can be walking around a map you made inside an hour, and the systems underneath already work.

A new project here is playable in seconds rather than an hour. Pick 2D and there is already a sky, a band of scenery, ground with a ledge, and a person who walks, falls and jumps under the keys you press. But read that list again: what is playable is a person moving. Nothing in it knows what an item is, and nothing takes a turn.

That is the honest gap. Painting a town takes minutes, and giving it an inventory, a party and an encounter is a conversation with the thing that writes the code plus several rounds of playing what comes back. If your measure is "a working RPG by tonight", that is the whole comparison and RPG Maker is the answer.

More on this: AI RPG generator: what generation is good for, and what it is not

RPG Maker's shape is its strength and its limit. Everything in it assumes a grid of tiles and a party-based encounter. Push outside that and you are fighting the tool with plugins, and the further out you go the more the game feels like a tool doing something it was not designed for.

Flockbay has no genre assumption to fight. A top-down tile RPG is one of the ordinary things it makes: you drag to lay ground and drag to erase it, and the tiles, the edges and the collision are all derived from which cells you covered. If that RPG grows a chase sequence or a base you defend, that is a request rather than a workaround.

The cost of no assumptions is that nothing is done for you. Freedom and blank space are the same thing looked at from two sides.

More on this: An AI RPG maker that leaves the engine in place

RPG Maker's event editor is explicit. Conditions, branches, switches and variables, all visible, all inspectable. Complicated events become long, but you can always point at the row that misfired.

Flockbay has an AI instead. You describe the behaviour and it writes GDScript into your project. Complicated behaviour does not become a longer list, but the logic is only inspectable if you go and read the code, which you can, because it is a normal Godot project.

The loop is different too. In an event editor you assemble until it is right. Here you describe, play, and complain. The complaining is the skilled part and it stays with you.

The old advice was to sketch your first location and look at what you drew. Rooms and corridors seen from above meant RPG Maker; a horizon meant you needed something else. That test has stopped sorting anything, because a floor plan of rooms and corridors is exactly what tile ground is for here, and you make it by dragging.

The test that still works is a list. Write down what your game needs on the first evening — a party, an inventory, a shop, turn order, saves, a menu you can drive from the keyboard. If you want those handed to you already working, before you have made a single decision of your own, that is RPG Maker's entire proposition and it is a strong one.

If you would rather describe them and tune them by playing, because your combat is not turn-based or your inventory has one rule nobody else's has, then the empty project is the point rather than the price. The second question is temperament. If event pages sound satisfying, that is another point for RPG Maker. If they sound like homework, the described-and-played loop is likely to suit you better.

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

Connectivity: RPG Maker works with the wifi off. Flockbay needs a connection to build, because the chat, asset generation and world data all come over the network. Playing what you built does not, since the game runs locally on the bundled Godot.

Portability: an RPG Maker project opens in RPG Maker. A Flockbay project is a Godot project, and Godot is open source, so it opens without us and can be handed to a programmer unchanged.

Art: RPG Maker has the ecosystem, and its stock and third-party sets are drawn to fit its exact format, which is a real head start. Here you place from a catalogue that is 90.8% sprites — 55,073 objects out of 60,648 — searchable by name with a picture of each, and Flockbay builds from a library of ready-made objects, or with Godot's own shapes, or you bring your own. What it will not do is animate a character for you: there is no 2D animation tool, and the app does not return a sprite sheet.

More on this: Flockbay vs Construct