AI worldbuilding, with a world that actually stays put.

You ask an AI for a fantasy world and it delivers: a mist-wrapped coastline, a capital carved into a cliff, a rival kingdom three days east across the salt flats. It is a great start. Then you play for an hour, and the salt flats are suddenly to the north, the coast is inland, and the three-day ride takes an afternoon. The world was never really a place. It was a description that changed every time the story looked away.

That is the gap between generating a world and being able to live in one. Making a cool setting is the easy part. Keeping it geographically consistent while you actually adventure in it, over dozens of sessions, is the hard part, and it is the part most tools skip.

A language model writes each new beat by re-reading a window of recent text. That window is large but finite. When your adventure grows longer than it, the opening scenes fall out of view, and with them go the details that anchored the map: which town was north of the river, how far the mountains were, which road led where. From the model's side of the screen, that geography is simply no longer on the page.

So a basic AI game master does the only thing it can. It improvises the world fresh each turn from whatever is still visible. Ask where the capital is twice, an hour apart, and you can get two different answers, because nothing is recording the first one. The setting feels solid in the moment and turns to fog the moment you need it to be consistent.

A bigger context window does not fix this. It pushes the wall further out, but a long campaign still crosses it, and the model still wastes attention re-reading old scenes to reconstruct a map it never actually kept. What a persistent world needs is not more text in view. It needs the geography stored as fixed data, outside the window, so it cannot drift.

Auferet keeps a world map: an endless plane of named locations, each with fixed coordinates. As places are discovered or established in your story, the game master writes them onto the map, and from then on it reads from the map instead of guessing. The capital sits where it was placed. The rival kingdom stays east.

Because every location has real coordinates, the game master can compute the exact straight-line distance and compass direction between any two of them. A two-day ride stays a two-day ride. When you set out north, you arrive at what is actually north. Travel stops being a vibe and becomes something the world can measure, which is what makes a journey across your setting feel like crossing an actual place rather than teleporting between descriptions.

The map does not replace the storytelling. It underwrites it. The game master still narrates the road, the weather, and who you meet, but it does so on top of a geography that is fixed and looked up, not re-invented each turn. That is the difference between a world you read about once and a world you can navigate for a hundred sessions.

The flow is simple. You tell Auferet the kind of world you want, from a drowned city of canals to a frontier moon colony, and it generates a starting setting and a scenario to begin in. From your first steps, the places you visit are recorded on the persistent world map, so the geography starts stable and stays that way.

As you play, the world fills in. New towns, ruins, and landmarks get their own coordinates the moment they matter, world facts collect in the Event Library, and the people you meet are kept in the Character Library so they return later with their history intact. If you already have a setting of your own, upload it and play inside your own canon instead of a world the AI invented on the fly.

The honest test is the same one that catches most tools: play a long session, travel across your world, then double back. If north is still north and the far city is still the same distance away, the world is real. That consistency is the thing Auferet is built to get right, so that a world you generated in a minute is still standing a hundred sessions later.