Fictional worlds collapse under their own lore unless factions, bloodlines, artefacts and betrayals live on a map you can actually interrogate. Writers bury continuity in wikis, scrap notes and Discord lore channels that disagree by Tuesday. A magic system's rules collide with a genealogy someone forgot. Collaborators invent NPCs that break three prophecies because nobody saw the dependency graph. linkchart becomes a fantasy character relationship map and world bible board: persons, companies (houses, guilds), items (artefacts), addresses (realms) and events linked by sworn to, forged, betrayed and prophesied. Continuity becomes a place you visit, not a vibe you hope for.
Why a real link chart for worldbuilding
Most people start this work with tools that were never designed for networks. Documents narrate. Spreadsheets tabulate. Whiteboards photograph poorly and refuse to scale. A dedicated fantasy character relationship map approach treats every person, place, asset and event as a node — and every meaningful connection as an edge you can label, question and revise.
That shift matters because decisions in worldbuilding are rarely about a single record. They are about patterns: who introduces whom, which address keeps appearing, which phone bridges two clusters, which event changed the shape of the network. linkchart exists so those patterns stay visible while you work, not only in the final slide.
Writers and GMs searching for a fantasy character relationship map, faction alliance chart or worldbuilding link board need structured lore entities. linkchart.art keeps bloodlines, artefacts and betrayals consistent across drafts.
Who this map is for
Novelists and game masters tracking characters, factions, artifacts, and secrets across a fictional world.
The signature move on the canvas: Give secrets and prophecies their own nodes so plot landmines stay visible to the author without dumping them into every character sheet.
What belongs on the map
Every fantasy character relationship map gets noisy when the wrong things dominate the board. Prioritise these domain-specific anchors before decorative extras:
- Characters and alternate identities
- Houses, guilds, and kingdoms
- Artifacts and locations of power
- Secrets, oaths, and prophecy events
Sample relationship labels
Prefer short, scannable edge text. Useful starters for this domain include: sworn to, betrayed, secret child of, wields, exiled from, prophecy binds.
Your first week on this canvas
Map the protagonist’s known world first, then the true world in a second layer of edges labelled as secret. Add faction hubs and the artifact that actually drives book one. Midweek, stress-test: if a side character dies, which plots break? Share a spoiler-free viewer with a beta reader if needed. By week’s end, continuity errors should be harder to ignore. Document why each card earned its place so the worldbuilding board does not drift into decoration. Before the week closes, freeze a viewer link for one outsider and capture their first three questions as backlog edges or notes.
What not to do
Do not keep the “real” genealogy only in your head while the map shows the public lie — encode both. Avoid infinite pantheon expansion before book one’s cast is stable. Never spoil your own tension by clarifying every mystery on the public layer. Resist swapping tools mid-draft without exporting the graph. If an edge cannot be explained in one plain sentence, it is not ready for a briefing view of your worldbuilding map.
What success looks like
Worldbuilding stays coherent under draft pressure: factions, bloodlines, and secrets have a place to live. When you revise chapter twenty, the canvas still remembers chapter three’s oath. When someone new opens the worldbuilding canvas, they should grasp the live question, the strongest links, and the next check within minutes. That is the operational definition of a successful fantasy character relationship map on linkchart.
How to use linkchart for worldbuilding
You do not need a special template to begin. Open the linkchart app, create a map, and build outward from the question you must answer. The workflow below is a proven path for people doing worldbuilding who want speed without losing structure.
- Create a map per region or story arc to avoid one unreadable continent blob.
- Add protagonists, houses and gods as person or company cards with canon notes.
- Link artefacts and places that constrain plot — who can hold what, where.
- Capture wars, coronations and curses as events that rewire alliances.
- Mark secrets the reader does not know yet as hidden notes with access discipline among coauthors.
- Share viewer maps with collaborators or RPG tables as needed.
As the map grows, resist the urge to make it decorative. Beauty comes from clarity: consistent card titles, honest labels, and notes that explain uncertainty. A slightly ugly accurate chart beats a pretty misleading one every time — especially when worldbuilding work has consequences.
Entity types that shine for this use case
linkchart supports investigation-ready cards you can reuse across domains. For worldbuilding, start with these and expand only when a new type earns its place on the canvas:
Person Company Address Event Phone Vehicle
Person and organisation cards carry identity. Addresses anchor geography. Phones and communication profiles expose bridges between clusters. Events give you time. Vehicles and items capture the physical world that worldbuilding narratives often depend on. Together they form a vocabulary you can teach a teammate in minutes.
Real-world scenarios
Dynastic succession subplot
Three heirs claim a throne through different maternal lines. Person cards and marriage edges make the legalist reading obvious; event cards for a disputed wedding and a battlefield oath create the dramatic reading. An item card for the crown's binding relic sits with who last touched it. The chapter outline writes itself from contested links rather than vibes about 'political tension'. Canon versus draft tags stop playtest ideas from corrupting the world bible your editor will eventually read.
Magic artefact with cursed custody chain
A blade cannot be held by the same bloodline twice. Mapping owners as persons, houses as companies, and possession events prevents you from breaking your own rule in book three. Address cards for vaults explain why a heist location matters. Coauthors stop accidentally inventing a fourth owner who voids the curse logic. Artefact custody rules and dynastic claims remain consistent across books because dependencies are inspectable. RPG tables receive redacted viewer graphs while GM-only secret edges stay properly partitioned.
Faction diplomacy for a campaign book
Guilds, temples and pirate courts trade favours. Company cards with alliance and embargo edges, plus event cards for broken treaties, give Game Masters a living board. Vehicle cards for airships and person cards for envoys keep travel plots grounded. Sessions improvise on structure instead of inventing geopolitics from scratch each night. RPG tables receive redacted viewer graphs while GM-only secret edges stay properly partitioned. Canon versus draft tags stop playtest ideas from corrupting the world bible your editor will eventually read.
Across these scenarios the constant is the same: when worldbuilding information stays trapped in siloed files, people argue about memory. When it lives as a labelled network, people argue about evidence — which is exactly where productive work happens.
Field practices that keep maps trustworthy
- Tag canon versus draft edges so playtest ideas do not corrupt the bible.
- Keep a legends cluster for myths that characters believe but are false.
- Name maps after questions ('Who can claim the Drift Throne?') for focus.
- Export subgraphs as series bibles for editors.
Common pitfalls
- Do not force every tavern regular onto the world map.
- Avoid contradiction by editing silently — mark retcons as events.
- Never assume readers need the full graph; it is a makers' tool first.
Compared with slides, whiteboards and generic diagram tools
Slide software is excellent for presenting a finished argument and poor at hosting an evolving network. Whiteboards are wonderful for a one-hour workshop and hostile to long-running worldbuilding work. Generic diagrammers can draw boxes and arrows, yet they rarely treat investigative entities as structured records with fields your team actually fills in. linkchart sits in the gap: fast enough for a working session, structured enough for a case file, visual enough for a briefing.
FAQ: Worldbuilding
Is this only for fantasy?
No — sci-fi houses, megacorps and AI lineages map with the same discipline.
Can RPG tables use viewer maps?
Yes — show players a redacted graph; keep GM-only edges private.
How do prophecies fit?
As event or item cards linked to the persons they constrain, with fulfilment status in notes.
Replace our wiki?
Wikis hold prose; linkchart holds relationships. Most teams want both.
Related ways to use linkchart
Ready to build your own fantasy character relationship map? Open linkchart, place your first cards, and let the network tell the story you have been trying to hold in your head.
Ethics, privacy and good judgement
Any powerful mapping tool can be misused. For worldbuilding, draw a bright line between legitimate analysis and voyeurism. Collect only what you need. Share only with people who have a role. When working with personal data, follow the laws and policies that apply to your organisation or community. linkchart is a canvas — responsibility for what you place on it remains yours.
Especially when maps include minors, victims, or confidential sources, default to minimisation. Use initials, role titles or delayed identifiers when full names are unnecessary for the analytical task. A precise network with careful labelling beats a sensational wall of private detail.