Why I locked the entire design before producing a single screen

There are two ways to make an RPG: start from a scene that excites you and see how far it carries, or lock the whole world down on paper and then produce it. The first is more fun. The second is the only one I know that survives chapter twelve.

What “locked” means

Locked does not mean pretty. It means measured. Right now the project’s data codex holds, counted by script rather than by eye:

• 253 bestiary entries, each with its essence card and stats.
• 70 character sheets: 5 heroes, 13 antagonists, 16 supporting cast, 6 NPCs and 30 bosses.
• 22 dungeons with an assigned room budget.
• 110 weapons across seven tiers, with a balance formula that audits itself against target time-to-kill.
• 51 points of interest on the macro map, joined by 46 routes.
• 51 script events placed across six acts.

None of that is finished. Scenes are still unsigned, drop tables are nearly empty and art lags behind. But the structure no longer moves, and that completely changes the kind of problem I face each morning.

The problem it avoids

When you design as you go, every new decision can invalidate finished work. You add a world layer and suddenly twenty enemies are at the wrong level. You change a hero’s archetype and four dungeons need rework.

With the structure locked, the outstanding work is finished content, not structure. It is the difference between “I am not sure this fits” and “I know exactly what is missing and in what order”. The second sentence can become a schedule. The first cannot.

What it cost me

Months of writing documents instead of playing. That is the honest price, and there were weeks when I doubted it was the right call. What kept me going was a silly check: every time the design answered a new question without contradicting itself, that was a week of production I would not be throwing away later.

Now the visible part begins. In this devlog I will show exactly how all that paper turns into a game you can play — including the parts that go wrong.