Can I edit the dungeon after it generates?

Yes, and that is the intended way to use it. The generated layout drops into the builder as an ordinary scene, so you can move walls, resize rooms and place things by hand.

Both are possible because the engine underneath is Godot, but the case it is built for is 3D. Terrain, real lighting and populated spaces are the intended shape.

Does it run in a browser?

No. It is a desktop app for Mac and Windows and the game runs locally on the bundled copy of Godot.

Who writes the enemy and trap logic?

Director 1 writes it as GDScript in your project. You say what should happen, play it, and say whether it is right.

Can I use my own art in the dungeon?

Yes. Generated assets, assets from the web and your own files all sit in the same project.

An AI dungeon generator that hands you a dungeon you can edit

A generated dungeon is a starting point, not a finished level. Stage Engine gives you the layout and then lets you move every wall in it, because the interesting part of a dungeon is the part a generator cannot guess.

What a dungeon generator is good at

Generators are very good at the boring half of a dungeon. Room counts, corridor connections, making sure the exit is reachable from the entrance, spreading loot so it is not all in one corner. That work is arithmetic. Doing it by hand for the twentieth room is how people abandon projects.

They are bad at the half that makes a dungeon memorable. The room you turn a corner into and stop. The corridor that is too long on purpose so the footsteps get uncomfortable. The moment the layout lies to you about where you are. None of that comes out of a seed, because none of it is a property of the graph.

So the honest design is to let the generator do the arithmetic and leave the rest to you. Stage Engine generates layout and then puts you in a builder where you can move a wall, widen a room, reroute a corridor and drop a set piece in the middle of it. Nothing about the generated result is locked.

Generation, then hands on it

The builder is a direct-manipulation editor, not a prompt box that regenerates the whole thing when you dislike one room. You are looking at the dungeon and changing the dungeon. If a junction feels wrong you drag it. If a room wants to be twice as tall you make it twice as tall.

This matters because regenerating is not editing. A tool that answers every complaint by rolling a new seed will never converge on the level you had in mind. It will just keep offering you different levels. The second one is not closer than the first.

Regeneration is still there when you want it, and it is genuinely useful early, when you are looking for a shape rather than refining one. The difference is that it is one option rather than the only lever.

The rules that make it a dungeon rather than a maze

Doors that need keys. Enemies that patrol a route and notice you. A boss room that locks behind you. Traps that reset. Loot tables that do not hand you the best sword in the first chest. That is code, and Director 1 writes it, in GDScript, inside your project.

You describe the rule you want in a sentence, play the dungeon, and say whether it felt right. Not writing the code does not mean not having a view on whether the key placement is fair. That judgement is yours and it is the part the tool cannot do.

Because the output is a real Godot project, the generated dungeon and the hand-placed corrections and the scripted rules all end up in the same place, as ordinary scenes and scripts. There is no separate proprietary dungeon format that only this tool can read.

Where it runs

Stage Engine is a desktop app for Mac and Windows. You download and install it, and it ships with a copy of Godot. Press play and the dungeon runs on your own machine at your own framerate.

That is the reason a dungeon with dynamic lighting, real shadows and thirty active enemies is a reasonable thing to attempt here. Browser tools are quiet about it, but the reason their examples are small and flat is that a tab is a hard performance ceiling.

Generating and building do need an internet connection, because the AI and the world data come over the network. Playing what you built does not.

Cost

The download is free and there is a free plan. Indie is $10 a month, Pro is $50. The paid plans buy more usage of the AI, not a better engine or a bigger dungeon budget.

Generating layouts is cheap in usage terms. Asking for a lot of code and a lot of art is where a plan starts to matter. It is a reasonable way to find out whether the tool suits you before spending anything.

Seeds, and why you should keep the good ones

A generator is only useful if you can get back to a result you liked. Roll twenty layouts, decide the eleventh had the right shape, and then be unable to find it again, and the tool has cost you an hour and given you nothing.

So treat generated layouts the way you would treat sketches. Keep the ones with a shape you responded to, drop them into the project, and let the ones you dislike go. Because the output is an ordinary scene in an ordinary Godot project, keeping one is just keeping a file.

That also changes how freely you can explore. When a promising result is cheap to save, you stop being careful with the reroll button, and being careless with the reroll button early is how you find a shape you would not have designed on purpose.

Questions

Can I edit the dungeon after it generates?: Yes, and that is the intended way to use it. The generated layout drops into the builder as an ordinary scene, so you can move walls, resize rooms and place things by hand.
Is this 2D or 3D?: Both are possible because the engine underneath is Godot, but the case it is built for is 3D. Terrain, real lighting and populated spaces are the intended shape.
Does it run in a browser?: No. It is a desktop app for Mac and Windows and the game runs locally on the bundled copy of Godot.
Who writes the enemy and trap logic?: Director 1 writes it as GDScript in your project. You say what should happen, play it, and say whether it is right.
Can I use my own art in the dungeon?: Yes. Generated assets, assets from the web and your own files all sit in the same project.