Worldbuilding with AI: build a setting that stays consistent

Start with a rule that costs something

Worlds built from lists of kingdoms and gods tend to sit still. Worlds built from one strange rule generate scenes on their own, especially when somebody pays for that rule.

Empress Suzuran's realm is a good model. Five hundred years ago she stopped every clock: blossoms never fall, nobody ages, nobody grieves. The cost is that nothing grows either, and a stranger who makes the clocks tick once is a crisis. Corvin Ash's Hollow works the same way: a walled district where the regime's drones lose signal and its laws stop at the gate. Freedom inside, and a ruler everyone owes.

Before anything else, answer two questions: what does everyone in this world take for granted, and who pays for it?

Interview the world

Broad requests get broad answers. "Tell me about this world" returns a textbook paragraph you will forget. Narrow, practical questions return details you can use in a scene:

• "If nothing ever spoils in Shirakage, what do street vendors sell?"
• "Who smuggles medicine through the Hollow's wall, and what do they charge?"
• "What is the rudest thing you can say to a judge in this city?"

Ask for options rather than answers: "(OOC: worldbuilding break. Give me three factions that want the wall torn down, two lines each.)" Then choose one, change one, and throw the third away. Picking keeps you the author; accepting everything turns the world into the model's average guess.

Keep a canon list

A world falls apart when the capital moves or the magic changes price halfway through. When signed in, use Story memory (⋯ menu) as a world bible of a dozen short lines:

• Rule: every clock in Shirakage stopped 500 years ago; nobody ages.
• Cost: no births, no harvests; grief is illegal.
• Places: the cherry courtyard; the border shrine; the frozen market.
• Power: the Empress; the guards who never blink; the border monks.
• Taboo: speaking of the day the clocks stopped.
• Open questions: why did the user's arrival make the clocks tick?

Write the facts as settled statements, not ideas, so the model treats them as true. If you play in SillyTavern over an API key, a lorebook does the same job for bigger worlds, switching entries on when their names come up.

Let the world arrive through scenes

Models love to explain. Ten paragraphs of history in one reply is the most common way AI worldbuilding goes wrong. Two fixes:

• Play an outsider. A newcomer has a reason to ask how things work. Justice Lorian Maret's new clerk, on their first morning in Aurenne's High Court, can ask about a city run by a centuries-old dragon without it sounding like an exam.
• Ask for the world through objects. *I pick up the coin on his desk and turn it over.* gets you currency, a ruler's face and an inscription, all in one detail.

When a reply contradicts canon, edit the line rather than arguing in the story. And sometimes keep the contradiction: a map that disagrees with the guide can become a mystery.

Turn the world into a character

Once a setting feels solid, make your own character to carry it: a guide, a ruler or a narrator for that world. Put the rule and the cost in Who they are, the places in Where it starts, and a greeting that drops the player somewhere only this world could have. From then on every new story starts inside your setting, and you can share it with others from the creators page.

Questions people ask