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

Procedural dungeons are the default answer and they are worse than people admit. A generated corridor is a corridor nobody chose, and after twenty of them the player stops looking at the walls. The dungeons anyone remembers were laid out by a person who wanted you to turn left.

Stage Engine defaults the other way. You build the dungeon by hand in the builder: rooms, corridors, height changes, a hall that opens up after three tight passages, a window that shows you where you are going before you can get there.

That is not more work than it sounds. Laying out a room is minutes with a cursor. It is also the part where being non-technical costs you nothing, because it is spatial judgement rather than programming.

If you want generation in the mix — a randomised layer over hand-built rooms, or a wing that shuffles — that is a system, and systems are written for you. But it is a decision you make rather than the tool's default.

Combat with the specific feel you want: turn based, real time with a wind-up, or something in between. Enemies that path, notice you, lose you and search. Loot with rarity and a drop table. Character progression, equipment, status effects that stack in a defined way.

Then the unglamorous half: doors and keys, a map that fills in as you explore, a save that restores the state of every chest, and a death that sends you somewhere sensible.

Director 1 writes all of it as GDScript in your project. You ask in plain words and you play the result. If the enemy gives up searching too fast, say so.

The genre spans all three and the tool does not have modes. The camera and controller are code, so they are written to whatever you ask for rather than picked from a list.

This matters more than it sounds, because the camera decides what a dungeon feels like. A grid-based first person crawler and a third person action dungeon are the same rooms with completely different tension, and you should be able to try both.

Lighting deserves a mention of its own. In a dungeon it is the primary tool for pacing, because what you cannot see is what makes a corridor tense. A torch with a small radius changes a room more than any amount of geometry.

Stage Engine is a desktop app for Mac and Windows with Godot bundled inside it. Your dungeon runs on your machine at your framerate. Real-time lighting, a torch that actually lights, and a hall large enough to feel exposed in are all normal rather than expensive.

Building needs an internet connection because Director 1, asset generation and world data come over the network. Playing what you built does not.

Free to download with a free plan; Indie is $10 a month and Pro is $50, which buy more usage rather than a different engine.

A dungeon is a rhythm before it is a place. Tension, release, a reveal, a moment where you can see how far you have come. The rooms are how you produce that rhythm and it is why laying them out yourself matters more here than in almost any other genre.

The practical version is that you should walk your dungeon end to end regularly, with nothing in it, just to feel the shape. Corridors that were fine on a plan are exhausting to actually traverse. A hall that looked grand feels small once you are standing in it.

This is the sort of judgement that has no technical component whatsoever, and it is the difference between a dungeon and a set of rooms.

You will not get combat right on paper. Every game that feels good in a fight got there by someone playing the same encounter two hundred times and adjusting wind-up times, recovery frames and reach.

That is normally out of reach for a non-programmer, because each adjustment is a code change. Here each adjustment is a sentence and a fight, which means you can actually run the two hundred passes.

And describing the problem is enough. "I keep getting hit during the recovery and it feels unfair" is a complete report. Working out which number that implicates is not your job.