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 and Linux built on Godot, where 2D or 3D is settled as the project is created. From a brief you approve, Flockbay builds a flat world from tile ground, a player controller with the camera on them, and sprites at an exact position, or a 3D one from terrain, water and weather, and writes the GDScript for behaviour. The same tools are buttons in the Godot editor for what you would rather place by hand. No default battle system, no item database, no event editor. Flockbay is free, AI included: free hosted AI every day, or 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 starts blank. Flockbay asks what your RPG is, one round of questions at a time, and writes a brief: what gets built first, what comes after, what is not in this version. Nothing is built until you approve it, and the first build is small on purpose: a town, a player controller, one system that works. Nothing in it knows what an item is until you ask for items.

That is the honest gap. Flockbay can lay out a town in minutes, but an inventory, a party and an encounter are 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: Flockbay paints the tile ground, and the tiles, the edges and the collision are all derived from which cells are 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 arrives pre-made: every system is described, built and tuned for your game. 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 Flockbay lays it.

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: rooms laid out on purpose, 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 Flockbay places from a library that is 90.8% sprites — 55,073 objects out of 60,648 — searchable by name with a picture of each, or builds with Godot's own shapes, or uses files you bring. What it will not do is generate an animated character: it makes still pictures, not sprite sheets, so the frames come from you, an artist or a library, and Godot's own animation tools in the editor put them in motion.

More on this: Flockbay vs Construct