Skip to content

AI JRPG maker: the systems are the easy half

By Eduardo Orellana · Updated

A JRPG is a stack of interlocking systems on top of a world you want people to remember. Flockbay writes the stack and builds the world. Judging the world is the part you should be spending your time on. 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.

The main page on this subject is What is an AI game maker that writes a real Godot project?.

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 genre demands before anything is fun

More systems than almost any other genre, and most of them have to exist before a single battle can be played. Turn order. A skill list with costs and effects. Status conditions that stack and expire. Equipment that changes derived stats. A party where members join, leave and are swapped. Experience curves. Item inventory. Save points. Menus for every one of these.

That is why so many JRPG projects stall in month two. None of that is the game, all of it is required, and the person building it usually wanted to make a story about a town.

Dedicated JRPG tools solve this by shipping the systems ready-made, which is a real solution with a real cost: everything made in them plays the same, because the systems are the same and the systems are the game.

More on this: AI RPG game generator for people who want the content problem solved

Written rather than picked from a list

Flockbay writes the systems instead of supplying them. You describe how combat should work and Flockbay writes the GDScript into your Godot project. Nothing is chosen from a menu of supported options.

That means your combat can be genuinely odd. A turn order determined by the weapon you last used. Magic that costs health rather than a resource. A party where the fourth slot is a person who does not obey you. None of these are on any preset list, which is exactly why they are worth doing.

Then you play it and tune it. Battle systems are made of numbers and the numbers are wrong until someone sits and fixes them, which is you.

The world is what people remember

Ask anyone about a JRPG they loved and they will describe a place before they describe a battle system. The town at the start. The place where the music changed.

Flockbay builds them from the brief, in whichever kind of world you confirmed before the project existed: 2D or 3D. Then you walk them, because a town has to be walked through to know whether it works, and no sentence you write will tell you the square is too large. When it is, say so, or drag the edge in yourself with the tools around the Godot editor's view.

The oldest shape in the genre is the top-down one, and here it is a first choice rather than a concession. Ground is a TileMapLayer painted by cells, and its TileSet terrains give the edges and the collision, so a town square is walkable the moment it is painted. Collision is set per tile in the TileSet, which is how the square and the wall behind it sit on the same layer and only one of them stops anybody. Top-down is not a mode you are granted, either: declare no gravity and the character body steers on both axes, because down was only ever a direction gravity gave it.

The towns get dressed from the Catalogue, which is 90.8% sprites (55,073 objects out of 60,648), searchable by name with a picture of each, and placed at an exact position, rotation and scale, by Flockbay or by you. A sprite's offset puts its base on its origin, so an inn sits on the road instead of hovering by however much transparent margin its file carries, and with Y-sort draw order follows the same point, so whatever is lower down the screen is in front of what is behind it.

Go 3D instead and the scenes are built in 3D, with terrain, water or weather from a Godot plugin, and you get an overworld you can actually cross rather than something abstracted into a map screen. Same app either way.

More on this: AI life sim maker: a place, a routine, and people who keep one

Dialogue and story

Branching conversations, flags that remember what you said, characters who react to events much later — all of that is code, and all of it is described rather than written.

The writing itself is yours. A tool can implement the branch. It cannot make the line land, and a JRPG lives or dies on whether you care about four people.

More on this: An RPG game maker where the systems get written for you

Practical facts

Free to download for Windows, macOS and Linux. 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. Flockbay builds from a library of ready-made objects, or with Godot's own shapes.

Building needs an internet connection since Flockbay and generation are online. The finished game runs locally and does not.

More on this: Building a farming game, which is mostly a calendar problem

Scope, honestly, for a genre that punishes it

JRPGs are among the largest games a small team attempts, because the format implies forty hours and a continent. That expectation kills more projects in this genre than any technical problem.

The version that gets finished is usually one town, one journey out and back, and a party of three. That is a complete game and it is achievable. The continent can come after someone has played the town.

Having the systems written for you removes months of work and does not remove the content. Every map still has to be built and judged, and every line still has to be written.

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

Do I get a ready-made battle system?
No, you get one written to your description. That is more work to specify and it is why your game will not play like everyone else's.
Is it 2D or 3D?
Whichever your game is, settled before anything is created. A top-down 2D overworld and towns built from a TileMapLayer and sprites are as much the point as a 3D overworld is. What changes is how the world is built, not how much of the app you get.
Can it do branching dialogue?
Yes. Describe the branches and the flags and Flockbay writes them. The writing is yours.
Do I need to know how to code?
No. Flockbay builds the world and writes the code; you judge the result by playing it.
What does it cost?
Nothing. Free to download. 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.

Free for Windows, macOS and Linux. Walk the town, tune the battles.

Download Flockbay free