AI JRPG maker: the systems are the easy half

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.

Stage Engine writes the systems instead of supplying them. You describe how combat should work and Director 1 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.

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.

You build those by hand in the builder — terrain, water, weather, buildings, interiors, the people standing in them. This is the right way round, 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.

Stage Engine is 3D-first and runs Godot locally, so an overworld you can actually cross is a reasonable thing to attempt rather than something abstracted into a map screen.

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.

Desktop app for Mac and Windows, Godot bundled inside. Free to download with a free plan. Indie is $10 a month, Pro is $50, both buying more usage.

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

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 every line still has to be written.