How to Keep Your RPG World's Lore Organized as It Grows

Why do scattered lore notes stop working?

Every long campaign has the same arc. Session one, lore lives in your head. By session five, it is a Google Doc. By session fifteen, it is a Google Doc, a Discord thread where you answered a player's question once, and a few sticky notes you cannot find. None of it is connected to the NPCs and factions it describes. None of it is organized beyond the order you happened to write it in. And when a new player joins, catching them up means re-explaining half your world's history from memory, hoping you do not contradict something you wrote down months ago.

This is a structural problem, not a discipline problem -- a flat document does not scale as the history it describes keeps growing. Our AI World Builder guide covers generating factions, locations, and NPCs with AI; this article is about the lore layer specifically -- the history, legends, and world secrets that give those entities depth, and how to keep it organized as it grows.

How do nested subsections keep lore organized?

LoreKeeper's lore editor structures entries as a tree instead of a flat list. A top-level entry -- say, "The Sundering War" -- can hold its own child entries underneath it: the key battles, the treaty that ended it, the general who defected partway through. You browse the tree from a sidebar, and each entry can carry its own small icon so you can scan the list visually instead of reading every title.

When your world has grown past a handful of entries, there is also a search box that filters the tree by title -- useful mid-session when you need to find "that one NPC" without remembering exactly where you filed them.

How do lore entries reference your NPCs, factions, and locations?

This is the feature that separates a lore wiki from a wall of text. When a lore entry mentions an NPC, faction, or location that already exists elsewhere in your world, LoreKeeper renders it as a linked reference. Hover it and a small preview card appears -- the entity's type, its name, and a short description -- without navigating away from what you are reading.

Practically, this means your world's political history and the faction roster you built are not two disconnected documents. Read about the war and hover the general's name to remember who they are; read the faction's entry and the war that defined them is one click away. Our world builder guide covers how those NPCs and factions get created in the first place; this is what keeps them connected to the history you write about them afterward.

What is it actually like to write a lore entry?

Entries are written in Markdown, with edit and preview tabs side by side -- so headings, lists, bold text, and tables render as you write instead of you guessing what the final page will look like. Longer lore entries with a clear structure (a history broken into eras, a faction's roster and goals) read far better formatted than as a single unbroken paragraph.

Saving is explicit rather than automatic: switch an entry into edit mode, write, and save with one click when you are done, with a confirmation toast so you know it landed. That is a deliberate trade-off -- you are always in control of when a draft becomes the version your players can read.

Frequently Asked Questions