What AI changes about worldbuilding
Worldbuilding has always had two jobs: inventing a world and keeping it straight. AI takes over much of the second. You design the history, the factions, and the rules; the storyteller keeps them in play, describes the right city when you arrive, and voices the right grudge when an old enemy returns.
It also changes how you build. A world on LoreWeaver is playable from its first paragraph, so you can test an idea by walking into it. The storyteller invents taverns, guards, and rumors as you go, and when it invents something good, you make it canon.
What it doesn’t do is decide for you. A world built entirely by the AI tends toward the familiar. The worlds people come back to have a specific premise, a few strong opinions, and secrets only their creator would think of.
The foundations every reply reads
Four fields go into every prompt, so they set the floor for every scene:
- Premise: the setting, its recent history, and the conflict already in motion. Write it for a storyteller who has to run the world tomorrow: specific, in the present tense, and short enough to read every time.
- Tone: the genre and mood in a line, such as “gothic mystery, slow and uneasy” or “swashbuckling and bright”.
- Style rules: explicit instructions for the replies, such as tense and point of view, reply length, how to handle dialogue, and anything to avoid.
- Openings: the scenes a session can start from. A world can offer several, and players choose one when they begin.
A premise that works: “Vell is a river city built on the bones of a drowned one. The Harbor Guild controls the docks and the divers; the Lantern Church controls the night watch; both want the Drowned Bell, which rang last week for the first time in forty years. The player has just been hired by one side and paid off by the other.”
Style rules work best as short, testable instructions rather than adjectives. A set that suits a world like Vell:
- Write in second person, present tense, and keep replies to three paragraphs or fewer.
- Let rain, river smells, and bells color every outdoor scene.
- Give each faction’s people a distinct way of speaking: guild divers curse, church wardens quote scripture.
- Never reveal what the Bell is; let characters argue about it.
- End each reply with something the player can act on.
If you’d rather start from a spark, describe your idea and choose Generate with AI. LoreWeaver builds a title, premise, tone, style rules, and opening for you to change. Character worlds work the same way, with the character’s description in place of a setting. Write {{user}} anywhere the player’s name should appear.
Lore cards: the world’s working memory
Everything that doesn’t belong in every prompt goes on a lore card. Each card has a title, a category, a description, tags, an importance rating, and an optional image. Worlds start with Character, Location, Faction, Item, Event/History, and Misc categories, and you can add your own, such as Spells, Noble Houses, or Ships, up to 50 per world.
A card joins a reply when it’s pinned, or when its title or one of its tags appears in the recent conversation. Matching is by whole words in any case, and descriptions aren’t scanned, so tags should hold names, nicknames, and the words players will actually type. Importance doesn’t trigger a card; it decides which matched cards win when space is short.
What to put on each kind of card:
| Category | Write about |
|---|---|
| Character | What they want, what they fear, how they speak, one secret, and how they feel about the player |
| Location | What you see, hear, and smell first, who is usually there, and what can happen there |
| Faction | Goals, resources, rivals, internal fractures, and what they want from the player |
| Item | What it does, what it costs to use, and who else wants it |
| Event/History | What happened, and who remembers it differently |
An example character card:
- Title: Captain Ilse Marrow
- Tags: Ilse, Marrow, Captain Marrow
- Description: Commander of Vell’s night watch and a loyal daughter of the Lantern Church, until it asks too much. Speaks in short, dry sentences and never raises her voice. Owes the player’s mentor her life and resents it. Believes the Bell rang for her brother.
Pin only the few cards every scene needs, such as a core rule of magic. Every pinned card is included in every reply, and that space comes out of the story.
Relationships you can see: LoreMaps
A world is more than a list. LoreMaps draws your lore cards as an interactive graph: characters, places, and factions as nodes, sized by importance and colored by category, with lines for how they relate. LoreWeaver suggests connections from shared tags, names mentioned in descriptions, and cards that appear together in the story. You can confirm them, draw your own, and label them with relationships such as “allied with”, “located in”, or “owns”.
The map is more than a picture. Turn on “Use map to expand story context”, and when a card enters a reply, closely connected cards can come along within a small share of the lore space. Mention the Harbor Guild, and its guildmaster may follow. LoreMaps comes with every plan.
Let the story write lore too
The storyteller invents constantly: a ferryman with a limp, a tavern called the Salt Lamb, a rumor about the bishop. Some of it deserves to become canon. On Plus and up, Emergent Lore Detection reads the story as you play and suggests new lore cards for the characters, places, and things it introduces. You keep the good ones and dismiss the rest.
On any plan, the habit is the same by hand: when a detail earns a second appearance, give it a card.
Events and rules with the Loom
Lore says what is true. The Loom decides what happens. It’s a no-code IF→THEN engine: each thread waits for its conditions during play and then acts.
- Conditions can watch for keywords, the number of actions taken, world-state flags and counters, whether a lore card came up, what the player carries, random chance, or a dice roll.
- Actions can inject an event, a line of dialogue, a scene change, or foreshadowing; pin, swap, or switch lore cards; set flags; show meters, quests, and inventory; award achievements and hints; or offer tappable choices.
A worldbuilder’s example: when the player first says “Drowned Bell”, set a flag and schedule a storm to break five actions later; when the storm arrives, swap the Bell’s lore card for the version where its secret is known. Hidden threads keep twists like that out of sight for players of your published world while still firing for them. The Loom guide covers every condition and action.
Scaling from a village to a continent
Build in rings, and only as far as the next session needs:
- The first scene. One location, three to five characters, and the problem in front of the player.
- The neighborhood. The places one road away, the factions with a stake, and the people they send.
- The region. Powers, trade, old wars, and the customs that change from town to town.
- The deep past. Gods, the origins of magic, the empire before this one. Add it when the story starts asking.
As the world grows, keep cards short and specific, split any card that covers two subjects, and use categories so you can find things. A large world doesn’t cost more per reply, because only the cards that come up are sent; pinned cards are the exception.
Common worldbuilding mistakes
| Mistake | Better |
|---|---|
| A premise that reads like an encyclopedia | A few paragraphs about the conflict happening now |
| One giant card for a whole kingdom | Separate cards for its capital, its ruler, and its army |
| Tags that are common words, like “king” or “city” | Names, nicknames, and specific terms players will type |
| Pinning every favorite card | Pinning only what every scene needs |
| Lore the player can never meet | Cards tied to someone the player can see, visit, or ask about |
| Rules written as adjectives (“make it epic”) | Instructions the storyteller can follow (“end each reply at a choice”) |
| Building the whole continent before the first scene | Building the first village, then playing |
The last one matters most. A world reveals what it needs once you’re inside it, and the scenes you play will tell you which card to write next. For more on keys, tags, and pins, see lorebooks explained.
Testing and publishing your world
Play your world before you share it. Try each opening, push on the premise, branch a session to test both sides of a choice, and watch the context inspector to see which cards fire.
When it’s ready, publish it to the Hub with a cover, a genre, tags, and a maturity rating. Players get their own copy to play, and hidden Loom threads stay hidden. You get a creator profile, follows, comments, and votes, and if you’re on the free plan, your first published world earns 3 days of Plus. Worlds also export and import as JSON, which makes a good backup. For more, see worldbuilding with LoreWeaver and AI world building.
