An AI map generator that hands you a world you can keep editing

Type a prompt, get an island. It looks good in the thumbnail. Then you try to put a road through it and discover the map is an image, or a mesh with no structure, or a file only the generator can read. The generation was the whole product and everything after it is your problem.

That is the wrong shape for making a game. A map is not a deliverable, it is the thing you will edit fifty times while the game finds out what it wants to be. The valley is too wide. The mountains block the view from the start position. The lake needs to be somewhere the player passes early. None of that is knowable before you walk it.

Stage Engine treats generation as a starting point rather than a result. Terrain comes in as real terrain data in a real Godot project, and every tool that shaped it is still there when the generation finishes.

Height. Terrain in Stage Engine is heightmap-driven, which is the boring technical answer and also the reason it stays editable. A generated landscape is a field of elevations with materials on top, not a sculpture that arrived fused. Raise it, lower it, smooth a ridge, cut a pass through a range.

Water follows the land rather than sitting on top of it. You can draw the outline of a lake or a coast and have it fill to the shape you drew. Weather and sky are their own layer, so the same terrain at dusk in fog is a different place from the same terrain at noon.

Real-world elevation data is available too, which is the fastest route to a map that feels like somewhere. Ground that was shaped by actual geology reads differently from ground shaped by noise, and players notice the difference long before they can name it.

Generation gets you a landscape. It does not get you a place. Placing the town, deciding where the path goes, choosing what the player sees when they crest the first hill — that is design, and it is faster to do it with your hands than to describe it in a sentence and hope.

So the builder is a builder. You are moving things in a 3D view, standing where the player will stand, and judging it. This is the part of the work that stays yours, and it is the part that makes one generated island different from every other generated island.

Director 1 handles the code. When the map needs behaviour — a boat that crosses the water, weather that changes on a schedule, a region that triggers something when the player enters it — you say what should happen and Director 1 writes the GDScript inside your project.

Stage Engine is a desktop app for Mac and Windows with Godot bundled inside it. Press play and the world runs on your own hardware. There is no streaming, no render queue and no browser tab deciding how much of your GPU you are allowed.

That is the practical reason a generated map here can be a landscape rather than a diorama. Browser-based world tools steer you toward small flat scenes because that is what they can serve. Running locally removes the reason to keep it small.

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

A landscape becomes a map when a player can navigate it. That takes landmarks: a peak visible from most of the valley, a river that always runs the same way, a road that tells you someone else has been here. Without them a generated world is beautiful and disorienting, and players get lost in a way that is not fun.

These are placement decisions, so you make them by hand. Stand at the point where the player will enter the region and ask what is visible. If the answer is nothing distinctive, move something until it is not.

Behaviour attached to the map is code. A river that carries a boat, a road that spawns traffic, a region that changes the weather when you enter it, fast travel between marked points. Describe it and Director 1 writes the GDScript into your project, then you play it and say whether it is right.