Lore & LilacTwo shapes of tool: the wiki and the connected record
Wiki-style tools give your world a home of its own: articles, templates and categories for cultures, religions, species, histories and magic. World Anvil and Campfire are well-known examples. Campfire, for instance, advertises eighteen modules, from characters and locations to languages and magic systems, with interactive maps and spoiler controls. Notion is often used in a similar way, as a flexible database you shape yourself.
Manuscript-connected records live inside a writing tool and are tied to the chapters. Instead of writing an article about a city, you mark the city where it appears, and the record gathers what the book has said about it. Novelcrafter's Codex, with aliases and automatic mentions, and Novelium's automatically tracked story records are examples of this approach.
| Wiki-style tool | Manuscript-connected records | |
|---|---|---|
| Best for | Deep settings, shared worlds, game masters, lore that exists beyond one book | Novelists who want records that reflect what is actually on the page |
| Where facts come from | What you write in the wiki | What you write in the manuscript, plus your notes |
| Main risk | The wiki and the manuscript drift apart | Less room for lore the book never mentions |
| Setup | Often substantial, by design | Usually grows as you draft |
| Used with a separate writing app? | Normally, yes | Usually it is the writing app |
Plenty of writers use both: a wiki for deep background, and connected records for what the reader actually sees.
Maps, family trees, timelines and rules
Visual tools are where worldbuilding software earns its keep, because they show relationships that prose hides. Before choosing, decide which of these your story genuinely needs.
- Maps matter when travel time, borders or lines of sight drive the plot. Check whether you can upload a map you've drawn and pin places to it, rather than having to draw inside the tool.
- Family trees matter for dynasties, inheritance and hidden parentage. Check whether a tree updates when you change a relationship elsewhere, or whether it is a separate drawing you must keep in step.
- Timelines matter most when the order readers meet events differs from the order they happened: flashbacks, several points of view, a frame story. Look for a tool that keeps story time and reading order apart.
- Rules for magic, technology or law matter when breaking one would cost the story its stakes. A short list of rules you can check a scene against is worth more than a long essay.
Keeping canon tied to the page
The most common worldbuilding problem in a novel isn't a missing detail. It's two versions of one detail: the river runs east of the city in chapter two and west of it in chapter nineteen. The further your records sit from the prose, the easier that becomes.
Three habits help, whatever tool you use:
- Note where each fact came from. “Mara's eyes are grey (ch. 3)” is more useful than “grey”, because when you revise chapter three you know which record to update.
- Separate what is true from what characters believe. A rumour overheard in a tavern isn't canon. Mark beliefs, rumours and plans differently from facts, or your notes will start contradicting themselves.
- Check before you change. Before altering a fact, find every passage that relies on it. A late change to a magic rule can quietly undo a climax.
Some tools now automate parts of this, suggesting records from your text or flagging possible contradictions. Treat that as a second reader, not a referee. Automated checks can miss things and raise false alarms, and only you know which inconsistencies are deliberate.
Spoilers, secrets and series
Series and mysteries bring two extra needs. The first is secrets: a collaborator or beta reader shouldn't learn the traitor's name from your notes before the book reveals it. The second is continuity across books: a scar, an alliance, a death, all need to carry forward correctly.
If anyone else will see your records, look for spoiler controls and preview exactly what they see. For a series, check whether records can be shared between books, and whether you can tell what was true at the end of book one apart from what changes in book two. Campfire advertises spoiler controls; Plottr and Novelcrafter both advertise series-level story records.
How much setup is too much?
Worldbuilding is enjoyable, and that is precisely the risk. A tool with dozens of templates invites you to fill them all in, and an elaborate world can become a comfortable reason not to start chapter one. If you notice you're designing a calendar for a culture that appears in a single scene, the tool is leading and the book is following.
None of this is an argument against deep worldbuilding. Some books depend on it. It's an argument for knowing which project you're working on today.
Where Lore & Lilac fits
Lore & Lilac takes the connected approach. Its story bible holds characters, places, objects, rules and groups, with aliases. Details cite the passage that established them and are flagged when that passage changes. Each detail carries a truth scope (canon, planned, belief, rumour or inference), so a tavern rumour never overwrites a fact. The world-building tools add profiles with images, a relationships graph, family trees and maps, and series workspaces share the bible and search across books.
It isn't a full wiki. There are no article templates for every aspect of a culture, and it is built for novels rather than games or public shared worlds. If your world needs to live beyond the book, a dedicated tool such as World Anvil or Campfire may suit you better, and you can keep it alongside. See how we compare with World Anvil.
Worldbuilding tool trial checklist
Use a real chapter and three or four of your actual characters and places, not the sample project.
The ticks are just for you; nothing is saved or sent.