Looking for an AI dungeon master, or a game to put one in?

The first is a chat product: you type, an AI narrates, you type again. Those exist, several are good, and none of them are what Stage Engine is. Nothing here is trying to replace a text adventure with an infinite improviser.

The second is what people usually mean when they arrive here from a game-development search. They want the thing a dungeon master actually provides in a video game: a world with rules, encounters that respond to what the player did, and a story that has somewhere to go. That is a game, and building it is what this tool is for.

Being clear about the difference early saves you a download. If it is the chat product you want, this page has told you. If it is the game, the rest of the page is about how it gets built.

Strip the improvisation away and a game master is doing four jobs. Setting a scene. Adjudicating what happens when a player tries something. Keeping the pressure right, so a session is neither trivial nor hopeless. And remembering what happened last time.

Every one of those is a system rather than a personality. Scene setting is world building, which you do by hand in the builder: terrain, weather, buildings, where the light falls. Adjudication and pacing are code, which Director 1 writes for you as GDScript inside your project. Memory is state, which is also code.

The result is a game that responds rather than an AI that talks. A guard who is more suspicious because you were seen last night is a better dungeon master than a paragraph of prose about a suspicious guard.

The convincing part of a tabletop session is that the world has opinions about you. Building that means characters with routines, factions with attitudes toward the player, and consequences that outlive the scene they happened in.

You place the characters and their world by hand, because where someone lives and what their village looks like is a taste decision. You describe the behaviour you want, and the code that drives it gets written for you. Then you play it, and if the guard is too forgiving you say so.

That loop is the job. You are not asked to read the script. You are asked to play the game and judge whether the world feels like someone is running it.

Stage Engine is a desktop app for Mac and Windows. It is a download and an install, not a website. Underneath is Godot, which is open source, and your project is a normal Godot project.

The game runs locally on the copy of Godot that ships with the app. Nothing streams and nothing renders in a tab. Building does need an internet connection, since Director 1 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, and what they buy is more usage rather than a different engine.

A narrated scene is words about a place. A built scene is a place. The difference shows up the moment a player does something the narrator did not anticipate, because a world made of rules has an answer and a world made of prose has to improvise one.

Building the world means the answer is already there. The door is locked because it is locked. The guard sees you because there is a line of sight. Nobody had to decide in the moment, which is why it holds up when a player pushes on it.

That is more work than writing a prompt and it is a different kind of thing at the end. Worth knowing which one you actually want before you spend a month on it.

Build one room first, at the size a person would actually stand in, and walk it. That tells you more about whether the place is convincing than a floor plan ever will.

Then put one character in it who does something when you arrive. A single reactive character in a well-proportioned room is the seed of the whole genre, and it is a first evening rather than a first month.

From there it grows outward: more rooms, a reason to move between them, consequences that carry from one to the next. Each step is something you describe or place, and then play.