[{"data":1,"prerenderedAt":1869},["ShallowReactive",2],{"/learn/prep":3,"learn-related-prep":430},{"id":4,"title":5,"author":6,"body":7,"cta":417,"datePublished":418,"description":419,"extension":420,"meta":421,"navigation":422,"path":423,"seo":424,"stem":425,"tags":426,"tracking":427,"__hash__":429},"learn/learn/04.prep.md","How Do I Prep a Session in 30 Minutes?","Jon",{"type":8,"value":9,"toc":403},"minimark",[10,48,51,54,57,64,72,77,83,86,89,171,174,180,184,193,203,213,223,233,240,246,249,253,259,264,267,275,278,282,289,292,295,299,306,309,313,316,319,329,332,344,348,355,358,363,366,370,376,379,382,385,394],[11,12,13,17,18,21,22,27,28,27,32,27,36,27,40,21,44,47],"p",{},[14,15,16],"strong",{},"What you'll learn:"," How to build a repeatable 30-minute session prep workflow using Kanka's dashboard, journals, and quest tracking ",[14,19,20],{},"Kanka features used:"," ",[23,24,26],"a",{"href":25},"/features#dashboards","Campaign dashboards",", ",[23,29,31],{"href":30},"/features#journals","Session journals",[23,33,35],{"href":34},"/features#quests","Quest tracking",[23,37,39],{"href":38},"/features#calendars","Fantasy calendars",[23,41,43],{"href":42},"/features#editor","@mention system",[14,45,46],{},"Time to complete:"," 15 minutes to set up, then 30 minutes per session going forward",[49,50],"hr",{},[11,52,53],{},"Campaign building doesn't stop after session one. Every week you sit down to prep, and every week the same thing happens: you re-read old notes trying to remember what Lord Harren promised the party, search three different docs for the name of the tavern in Ashwick, and manually check whether that side quest from session 4 ever got resolved.",[11,55,56],{},"The prep time isn't spent creating. It's spent searching.",[11,58,59,60,63],{},"This tutorial shows you how to set up a ",[23,61,62],{"href":25},"campaign dashboard"," that pre-assembles your session context, so your weekly prep starts with reviewing, not hunting.",[11,65,66,67,71],{},"If you're building your first campaign from scratch, our hub guide on ",[23,68,70],{"href":69},"/learn/worldbuilding","worldbuilding for tabletop RPGs"," covers the foundational structure this workflow depends on.",[73,74,76],"h2",{"id":75},"why-does-prep-take-so-long","Why Does Prep Take So Long?",[11,78,79,82],{},[14,80,81],{},"Most session prep tools store your world passively, they don't surface what's relevant."," Flat notes, scattered Google Docs, and generic DM tools treat every piece of information equally. Nothing tells you which NPCs are active, which plot threads your players tugged on last week, or which faction deadline is three in-game days away.",[11,84,85],{},"The result? You spend 2–4 hours doing administrative recovery before you get to the creative part.",[11,87,88],{},"Here's what's actually happening during that time:",[90,91,92,109],"table",{},[93,94,95],"thead",{},[96,97,98,103,106],"tr",{},[99,100,102],"th",{"align":101},"left","Where Prep Time Goes",[99,104,105],{"align":101},"What You're Doing",[99,107,108],{"align":101},"What a Relational System Does Instead",[110,111,112,127,141,157],"tbody",{},[96,113,114,118,121],{},[115,116,117],"td",{"align":101},"Re-reading session recaps",[115,119,120],{"align":101},"Searching for NPC names and plot threads",[115,122,123,126],{"align":101},[23,124,125],{"href":42},"@mentions"," in journals auto-link every entry referenced in the recap",[96,128,129,132,135],{},[115,130,131],{"align":101},"Checking quest status",[115,133,134],{"align":101},"Opening multiple docs, scanning for updates",[115,136,137,140],{"align":101},[23,138,139],{"href":34},"Quest entries"," with Active/Completed/Failed status, filterable in one widget",[96,142,143,146,149],{},[115,144,145],{"align":101},"Finding relevant locations",[115,147,148],{"align":101},"Browsing folders, guessing file names",[115,150,151,152,156],{"align":101},"Location ",[23,153,155],{"href":154},"/features#entries","entries"," cross-referenced to characters, quests, and events",[96,158,159,162,165],{},[115,160,161],{"align":101},"Tracking time-sensitive events",[115,163,164],{"align":101},"Maintaining a separate calendar or spreadsheet",[115,166,167,170],{"align":101},[23,168,169],{"href":38},"Calendar reminders"," surface upcoming events automatically",[11,172,173],{},"If you become overwhelmed by the process of prepping, your tools are failing you, you’re not the one failing.",[11,175,176,177,179],{},"The fix isn't \"prep less.\" It's a system where the relational web between your ",[23,178,155],{"href":154}," does the retrieval work for you. Every @mention you write, every quest element you link, every calendar reminder you set — that's the cross-referencing infrastructure that future prep sessions depend on.",[73,181,183],{"id":182},"how-do-i-build-a-prep-dashboard","How Do I Build a Prep Dashboard?",[11,185,186,189,190,192],{},[14,187,188],{},"Configure four dashboard widgets once, then use them every prep session."," Open your ",[23,191,62],{"href":25}," settings and add a widget.",[11,194,195,198,199,202],{},[14,196,197],{},"Widget 1 — Active Quests."," Add an entry list widget filtered to your ",[14,200,201],{},"Status:Active"," tag. This shows every open quest. Your campaign's living table of contents — the backbone of a living world that updates as the story evolves.",[11,204,205,208,209,212],{},[14,206,207],{},"Widget 2 — Seed entries."," Add an entry list widget filtered to ",[14,210,211],{},"Status:Seed",". These are the half-formed ideas from previous sessions, an NPC name you dropped, a rumor you improvised, a location the party asked about. Seeds are your creative backlog.",[11,214,215,218,219,222],{},[14,216,217],{},"Widget 3 — Recent Sessions."," Add a journal list widget showing the last 10 ",[23,220,221],{"href":30},"session journals",". These are your prep starting point every single week.",[11,224,225,228,229,232],{},[14,226,227],{},"Widget 4 — Campaign Calendar."," Add a ",[23,230,231],{"href":38},"calendar widget"," showing the current in-game date with upcoming reminders. Faction deadlines, NPC birthdays, seasonal festivals, anything time-sensitive surfaces here without manual tracking.",[234,235,239],"preview",{"url":236,"alt":237,"asset":238},"images/screenshots/learn/dashboard-wireframe.png","Dashboard setup","","\n\nCustomise your dashboard for session prep\n\n",[11,241,242],{},[243,244,245],"em",{},"Four widgets. Thirty minutes. Everything you need to prep the next session is already here.",[11,247,248],{},"This dashboard is the single entry point for every prep session. Configure it once. The widget filters handle the rest.",[73,250,252],{"id":251},"whats-the-actual-workflow","What's the Actual Workflow?",[11,254,255,258],{},[14,256,257],{},"Five steps, same order, every week."," The first three steps are review. Only Step 4 requires creative work.",[260,261,263],"h3",{"id":262},"step-1-review-last-session-5-min","Step 1: Review Last Session (5 min)",[11,265,266],{},"Open the most recent journal entry on your dashboard. Read through your @mentions, they're the threads your players pulled on. Note which characters, locations, or quests got the most attention.",[11,268,269,270,274],{},"The @mentions do double duty here. Every entry name you typed with @ in last session's recap is now a live link. Click through any that seem important. The ",[23,271,273],{"href":272},"/features#relations","entry relations"," panel shows you who's connected to what without re-reading five sessions of backstory.",[11,276,277],{},"Write prep notes as Articles on the relevant entries, not in a separate document. This keeps context co-located with the NPC or location it's about.",[260,279,281],{"id":280},"step-2-triage-seed-entries-5-min","Step 2: Triage Seed entries (5 min)",[11,283,284,285,288],{},"Check your ",[14,286,287],{},"Seed entries"," widget. For each seed, decide: expand it, archive it, or leave it for later.",[11,290,291],{},"If players engaged with a seed last session, flesh it out. Add 2–3 properties and one relation to another entry. A seed NPC gets a goal and a connection to a faction. A seed location gets a parent location and one notable feature.",[11,293,294],{},"If nobody bit? Leave it. Seeds are cheap to create and free to ignore.",[260,296,298],{"id":297},"step-3-update-active-quests-5-min","Step 3: Update Active Quests (5 min)",[11,300,301,302,305],{},"Open each active ",[23,303,304],{"href":34},"quest",". Update the status if the story branched. Add new quest elements, maybe the party picked up an unexpected ally, or a new location became relevant.",[11,307,308],{},"Check quest prerequisites. If a quest depends on something the party hasn't done yet, note it. If a quest resolved last session, mark it Completed and move on.",[260,310,312],{"id":311},"step-4-prep-the-next-scene-10-min","Step 4: Prep the Next Scene (10 min)",[11,314,315],{},"Based on Steps 1–3, identify the most likely next encounter. Where are the players headed? Which NPC are they likely to talk to?",[11,317,318],{},"Write a brief Article on the relevant location or character entry: \"What happens when the party arrives.\" Two to three sentences. A scene hook, not a full script.",[11,320,321,322,325,326,328],{},"Create any new seed entries for NPCs or locations that might appear. Use the ",[14,323,324],{},"Quick Creator"," (press 'N') to add them without leaving your current page. Tag them ",[14,327,211],{},".",[11,330,331],{},"If this step takes more than 10 minutes, be wary of overprepping. The scene hook is enough, your players will take it somewhere you didn't plan anyway.",[11,333,334,21,337,343],{},[14,335,336],{},"Try this now:",[23,338,342],{"href":339,"rel":340},"https://app.kanka.io/register?utm_source=learn&utm_campaign=prep",[341],"nofollow","Set up a free Kanka campaign"," and build your first prep dashboard. The four-widget layout takes about 15 minutes to configure.",[260,345,347],{"id":346},"step-5-calendar-check-5-min","Step 5: Calendar Check (5 min)",[11,349,350,351,354],{},"Advance the in-game date on your ",[23,352,353],{"href":38},"campaign calendar",". Check what reminders fire this session. Note any time-sensitive plot threads: a faction ultimatum expiring, a festival starting, an NPC's deadline arriving.",[11,356,357],{},"Link your new session journal to the current calendar date. This transforms your session recaps into chronological, cross-referenced campaign history. Six months from now, you can check the calendar to see exactly what happened on any given in-game day. That's lore consistency enforced by the system, not your memory.",[234,359,362],{"url":360,"alt":361,"asset":238},"images/screenshots/learn/dashboard-calendar-sundisk.png","Dashboard calendar widget","\n\nA calendar keeps you on top of time\n\n",[11,364,365],{},"It should now look something like this.",[73,367,369],{"id":368},"how-does-this-get-faster","How Does This Get Faster?",[11,371,372,375],{},[14,373,374],{},"The workflow accelerates as your relational web grows."," By session 10, Steps 1–3 take 5 minutes total because the system surfaces everything: active quests are already filtered, seed entries are already tagged, and your journal @mentions already link to every relevant entry.",[11,377,378],{},"The 30 minutes is the ceiling, not the floor. A campaign with 50+ cross-referenced entries and consistent tagging makes the dashboard do most of the cognitive work.",[11,380,381],{},"Run this workflow the same day each week to build the habit. Sunday afternoon works for most groups. The consistency matters more than the specific day.",[11,383,384],{},"One more thing: the same campaign wiki that powers your prep can also serve your players between sessions — if you design the player-facing experience deliberately. That's a different workflow, and we cover it in our guide on building a campaign wiki players will actually use.",[11,386,387,393],{},[23,388,390],{"href":339,"rel":389},[341],[14,391,392],{},"Start your free campaign →"," Unlimited entries, unlimited campaigns, no paywalls.",[11,395,396,397,402],{},"If you have any questions, join us over on our ",[23,398,401],{"href":399,"rel":400},"https://kanka.io/go/discord",[341],"Discord","!",{"title":238,"searchDepth":404,"depth":404,"links":405},2,[406,407,408,416],{"id":75,"depth":404,"text":76},{"id":182,"depth":404,"text":183},{"id":251,"depth":404,"text":252,"children":409},[410,412,413,414,415],{"id":262,"depth":411,"text":263},3,{"id":280,"depth":411,"text":281},{"id":297,"depth":411,"text":298},{"id":311,"depth":411,"text":312},{"id":346,"depth":411,"text":347},{"id":368,"depth":404,"text":369},"Prepping in 30 minutes","2026-04-10","Campaign building shouldn't take your entire day. A repeatable 30 minute session prep workflow built on dashboards, quest tracking, and last week's journal","md",{},true,"/learn/prep",{"title":5,"description":419},"learn/04.prep",[427,428],"prep","session","VH6j5YaMc-fLlt2P-etktS_nthc4A7pG1X9_jzXRSj8",[431,1041,1408],{"id":432,"title":433,"author":6,"body":434,"cta":238,"datePublished":418,"description":1033,"extension":420,"meta":1034,"navigation":422,"path":69,"seo":1035,"stem":1036,"tags":1037,"tracking":1038,"__hash__":1040},"learn/learn/00.worldbuilding.md","Worldbuilding for Tabletop RPGs: Start Small, Build What You Need",{"type":8,"value":435,"toc":1025},[436,464,466,470,473,484,487,494,501,505,511,514,582,585,599,606,609,621,625,631,634,645,648,661,674,677,689,693,699,706,709,778,784,791,805,809,819,822,828,838,898,905,909,915,921,941,947,954,957,962,966,972,983,990,1000,1005,1013],[11,437,438,440,441,21,443,27,446,27,449,27,451,27,455,27,458,21,461,463],{},[14,439,16],{}," How to worldbuild reactively — expanding only where players push — instead of burning out before session 1 ",[14,442,20],{},[23,444,445],{"href":154},"entry hierarchy",[23,447,448],{"href":272},"Relations",[23,450,43],{"href":42},[23,452,454],{"href":453},"/features#collaborative","Permissions",[23,456,457],{"href":25},"Dashboards",[23,459,460],{"href":30},"Journals",[14,462,46],{}," 15 minutes to set up your starting structure",[49,465],{},[467,468,433],"h1",{"id":469},"worldbuilding-for-tabletop-rpgs-start-small-build-what-you-need",[11,471,472],{},"The number one reason GMs abandon worldbuilding projects is they built too much before anyone sat down to play. The conventional advice to design your pantheon, sketch your continents, write your creation myth, front-loads months of creative work before a single session happens. Most campaigns never survive contact with players anyway.",[11,474,475,476,479,480,483],{},"This is the \"Worldbuilder's Trap\": the belief that a world has to be ",[243,477,478],{},"complete"," before it can be ",[243,481,482],{},"used",". The opposite is true. The most resilient campaign worlds are built reactively by expanding only where players push, deepening only where the story demands.",[11,485,486],{},"Session 1. The party arrives in the starting village. A player asks: \"What god does this village worship?\" You haven't built a pantheon. You improvise: \"Solara, goddess of the hearth.\" Three sessions later, a cleric player asks about Solara's rival deity, and you can't remember whether you said \"Solara\" or \"Solaris,\" or what domain you implied.",[11,488,489,490,493],{},"The problem isn't that you improvised. It's that you had no system to ",[243,491,492],{},"capture"," the improvisation and connect it to everything else.",[11,495,496,497,500],{},"This guide covers the methodology that prevents two common failure modes, overbuilding and losing continuity, by using a ",[23,498,499],{"href":154},"relational entry system"," that grows with your campaign instead of demanding everything upfront.",[73,502,504],{"id":503},"what-should-you-build-first","What Should You Build First?",[11,506,507,510],{},[14,508,509],{},"Build the smallest playable unit: one location, three NPCs, and one conflict."," Everything else can wait.",[11,512,513],{},"This method works in concentric circles:",[90,515,516,532],{},[93,517,518],{},[96,519,520,523,526,529],{},[99,521,522],{"align":101},"Circle",[99,524,525],{"align":101},"What to Build",[99,527,528],{"align":101},"When",[99,530,531],{"align":101},"entry Count",[110,533,534,550,566],{},[96,535,536,541,544,547],{},[115,537,538],{"align":101},[14,539,540],{},"1 — Starting Point",[115,542,543],{"align":101},"One settlement, three NPCs, one quest hook, one rumor pointing outward",[115,545,546],{"align":101},"Before session 1",[115,548,549],{"align":101},"5–8",[96,551,552,557,560,563],{},[115,553,554],{"align":101},[14,555,556],{},"2 — Immediate Region",[115,558,559],{"align":101},"Surrounding geography, neighboring settlements, the faction or threat driving Arc 1",[115,561,562],{"align":101},"Sessions 2–5",[115,564,565],{"align":101},"15–25",[96,567,568,573,576,579],{},[115,569,570],{"align":101},[14,571,572],{},"3 — Wider World",[115,574,575],{"align":101},"Political structures, distant empires, pantheons, historical events",[115,577,578],{"align":101},"Sessions 6+ (only when referenced)",[115,580,581],{"align":101},"As needed",[11,583,584],{},"Each circle's entries reference the previous circle's entries. The blacksmith in Circle 1 was born in the mining town in Circle 2. The mining town's economy depends on trade routes controlled by the empire in Circle 3. Building outward deepens existing connections rather than adding disconnected content.",[11,586,587,588,591,592,594,595,598],{},"Use ",[23,589,590],{"href":154},"Location entries"," with nesting for Circle 1: the starting settlement as parent, key buildings as children. Link NPCs to those Locations via ",[23,593,448],{"href":272}," (\"Owner,\" \"Patron,\" \"Guard\"). Create a single ",[23,596,597],{"href":34},"Quest entry"," for the starting hook and link its instigator and relevant locations as quest elements.",[11,600,601,602,605],{},"The discipline: name things immediately, detail them later. A location called \"The Thornwood\" with no description is more useful than no location at all. A Character entry with nothing but \"Innkeeper\" in the ",[14,603,604],{},"Type"," field is enough to start.",[11,607,608],{},"Circle 1 should take no more than 60 minutes. If an entry has zero connections after two sessions, set it aside, it's not a living part of the world yet.",[11,610,611,612,616,617,328],{},"For the full walkthrough on spatial structure such as how deep hierarchies go, when to create new locations, how uploaded maps connect to your entry hierarchy, see ",[23,613,615],{"href":614},"/learn/hierarchies","How to Organize Fantasy Locations: Hierarchies That Scale",". For the NPC creation pattern that makes every character findable and connected from birth, see ",[23,618,620],{"href":619},"/learn/characters","NPC Management for Game Masters",[73,622,624],{"id":623},"how-do-details-stay-connected","How Do Details Stay Connected?",[11,626,627,630],{},[14,628,629],{},"The difference between notes and a living, breathing world is that a world knows its own connections."," A document full of NPC profiles is static. You have to remember that the blacksmith's daughter joined the thieves' guild, that the guild operates out of the abandoned temple, that the temple was abandoned because of the plague 40 years ago. In a flat note system, those connections exist only in your head.",[11,632,633],{},"In a relational system, updating one entry ripples context to every connected entry. When you write that Mira trained under Grandmaster Torvald, both Mira and Torvald reflect that connection. Open Torvald's page during prep and you see that Mira is his student without searching.",[11,635,636,637,640,641,644],{},"This is the core architectural principle: ",[14,638,639],{},"entries reference each other, not just coexist."," Each new entry increases the context density of every entry it touches. Prep time ",[243,642,643],{},"decreases"," over time because the web does the memory work.",[11,646,647],{},"Two tools make this work:",[11,649,650,652,653,656,657,660],{},[14,651,448],{}," with custom labels (\"Trained Under,\" \"Rival Of,\" \"Operates In\") and ",[14,654,655],{},"Mirror Relations"," enabled, so every connection is automatically bidirectional. The ",[23,658,659],{"href":272},"Relation Explorer"," visualizes the full connection web during prep revealing narrative threads you didn't consciously plan.",[11,662,663,665,666,670,671,673],{},[14,664,125],{}," in every text field. Type ",[667,668,669],"code",{},"@"," followed by any entry name in ",[23,672,221],{"href":30},", descriptions, or quest briefings. Every @mention creates a traceable reference: the \"Mentioned In\" interface shows everywhere an entry appears across the entire campaign wiki. Lore consistency scales beyond human memory.",[11,675,676],{},"Session 8. A player asks: \"Didn't that merchant say he was from the same village as the guard captain?\" You type the merchant's name, see his Relations tab: yes, \"Former Neighbor\" relation to the guard captain, linked to the village of Ashenmoor. You also notice Ashenmoor was recently tagged \"Status:Threatened.\" The merchant hasn't heard the news. You have a plot hook you didn't plan  because the system surfaced the connective tissue that made it possible.",[11,678,679,680,684,685,328],{},"Don't create connections you can't justify in-world. Relational clutter is worse than relational sparsity. For the full workflow on building, labeling, and maintaining entry relations at scale, see ",[23,681,683],{"href":682},"/learn/living-web","How to Link Characters, Locations, and Plot Into a Living Web",". For applying this specifically to political factions, see ",[23,686,688],{"href":687},"/learn/factions","How to Build Factions That Drive Conflict",[73,690,692],{"id":691},"what-should-players-see","What Should Players See?",[11,694,695,698],{},[14,696,697],{},"Players should see exactly what their characters have discovered, no more, no less."," The biggest UX mistake GMs make with digital tools is treating them as either fully private or fully public. The answer is granular: entry-by-entry, section-by-section, session-by-session.",[11,700,701,702,705],{},"The permission layer transforms a GM's personal wiki into a ",[23,703,704],{"href":453},"collaborative worldbuilding"," tool. Done well, players browse the campaign wiki between sessions, re-read what they know, discover connections between things they've encountered, and feel a growing sense of mastery over the world. But they never see the secret patron behind the thieves' guild.",[11,707,708],{},"The key pattern: public entry + private Articles = mystery that players can engage with without spoiling. A Character entry is visible, players see the NPC's name, appearance, role, but an Article titled \"True Allegiance\" on that same entry stays admin only. The fog of war holds.",[90,710,711,724],{},[93,712,713],{},[96,714,715,718,721],{},[99,716,717],{"align":101},"Permission Layer",[99,719,720],{"align":101},"What It Controls",[99,722,723],{"align":101},"Example",[110,725,726,739,752,765],{},[96,727,728,733,736],{},[115,729,730],{"align":101},[14,731,732],{},"entry visibility",[115,734,735],{"align":101},"Whether the entry exists for players at all",[115,737,738],{"align":101},"Hide the dungeon they haven't found",[96,740,741,746,749],{},[115,742,743],{"align":101},[14,744,745],{},"Article visibility",[115,747,748],{"align":101},"Secrets attached to otherwise public entries",[115,750,751],{"align":101},"Admin only \"Secret Mission\" article on a public NPC",[96,753,754,759,762],{},[115,755,756],{"align":101},[14,757,758],{},"Relation visibility",[115,760,761],{"align":101},"Which connections players can see",[115,763,764],{"align":101},"Public \"Guild Leader\" relation, hidden \"Secret Patron\" relation",[96,766,767,772,775],{},[115,768,769],{"align":101},[14,770,771],{},"Mention redaction",[115,773,774],{"align":101},"@mentions of private entries auto display as [redacted]",[115,776,777],{"align":101},"Write freely in session notes; the system handles what shows",[11,779,587,780,783],{},[14,781,782],{},"\"View As\" member switching"," before each session to experience the wiki from any player's perspective. This catches accidental reveals.",[11,785,786,787],{},"Reveal permissions progressively: after a major story beat, flip an Article from private to visible. The wiki becomes a record of discovery, not just a reference. For the complete guide to building a player-facing wiki experience with dashboards, organization, and the structural reasons players avoid wikis see ",[23,788,790],{"href":789},"/learn/players","Why Don't Your Players Use the Wiki You Built?",[11,792,793,800,801,328],{},[23,794,797],{"href":795,"rel":796},"https://app.kanka.io/register",[341],[14,798,799],{},"Try this in your own campaign →"," Per-entry permissions work on the ",[23,802,804],{"href":803},"/pricing","free tier",[73,806,808],{"id":807},"how-do-you-keep-it-organized","How Do You Keep It Organized?",[11,810,811,814,815,818],{},[14,812,813],{},"Organization in worldbuilding isn't about folders it's about retrievability."," The goal is finding any piece of your world in under 10 seconds during a live session. That changes the design principle: organize by ",[243,816,817],{},"context",", not just by type.",[11,820,821],{},"Two organizational layers survive long campaigns:",[11,823,824,827],{},[14,825,826],{},"entry types handle the \"what.\""," Characters, Locations, Organizations, Quests, Kanka's built-in taxonomy means you never decide where an NPC \"goes.\" A Character is always a Character. A city is always a Location. This structural clarity eliminates \"where did I put that note?\"",[11,829,830,833,834,837],{},[14,831,832],{},"Tags handle the \"why.\""," Tags are the ",[23,835,836],{"href":154},"cross referencing"," layer that connects entries by narrative relevance. Tag an NPC, a Location, and a Quest with \"Arc:TheDragonWar\" and you've created an instant filter showing everything relevant to that storyline regardless of entry type.",[90,839,840,852],{},[93,841,842],{},[96,843,844,847,850],{},[99,845,846],{"align":101},"Organizational Principle",[99,848,849],{"align":101},"What It Solves",[99,851,723],{"align":101},[110,853,854,865,876,887],{},[96,855,856,859,862],{},[115,857,858],{"align":101},"entry types (permanent)",[115,860,861],{"align":101},"\"What is this thing?\"",[115,863,864],{"align":101},"A Character is always a Character",[96,866,867,870,873],{},[115,868,869],{"align":101},"Tags (fluid)",[115,871,872],{"align":101},"\"Why does this matter right now?\"",[115,874,875],{"align":101},"\"Arc:TheDragonWar\" + \"Status:Active\" + \"Faction:KingsGuard\"",[96,877,878,881,884],{},[115,879,880],{"align":101},"Location hierarchy",[115,882,883],{"align":101},"\"Where is this in the world?\"",[115,885,886],{"align":101},"Continent > Region > City > District",[96,888,889,892,895],{},[115,890,891],{"align":101},"Dashboard widgets",[115,893,894],{"align":101},"\"What do I need for next session?\"",[115,896,897],{"align":101},"Filtered lists of active quests, seed entries, recent journals",[11,899,900,901,904],{},"Use 3–5 tags per entry maximum. Create a tag taxonomy early: \"Arc:[Name]\", \"Status:[State]\", \"Faction:[Name]\" as prefixes prevent sprawl. Configure ",[23,902,903],{"href":25},"dashboard"," widgets with filtered entry lists, a \"Current Arc NPCs\" widget, an \"Active Quests\" widget, a \"Seed Notes\" widget. The dashboard becomes the session-prep command center.",[73,906,908],{"id":907},"when-does-worldbuilding-happen","When Does Worldbuilding Happen?",[11,910,911,914],{},[14,912,913],{},"The best worldbuilding happens in three distinct moments: before session 1, during sessions, and between sessions."," Most advice focuses on pre-campaign building. In practice, a lot of meaningful worldbuilding happens reactively.",[11,916,917,920],{},[14,918,919],{},"Moment 1: The Seed Phase (pre-campaign)."," Build Circle 1. Set up the starting location, three NPCs, one quest. Establish your tag taxonomy. Time: 60–90 minutes.",[11,922,923,926,927,930,931,933,934,936,937,940],{},[14,924,925],{},"Moment 2: The Capture Phase (during sessions)."," A player asks a question you haven't prepped. You improvise an answer. The discipline is capturing that answer immediately, press ",[14,928,929],{},"'N'"," or click ",[14,932,324],{}," to create a seed entry in under 10 seconds. Name, type, one tag, done. Then write ",[667,935,669],{}," and the entry name in your ",[23,938,939],{"href":30},"session journal"," to link it to its narrative origin. Speed matters more than completeness.",[11,942,943,946],{},[14,944,945],{},"Moment 3: The Weave Phase (between sessions)."," Spend 15–30 minutes doing three things: flesh out seed entries from last session, add Relations between new and existing entries, review \"Mentioned In\" lists for key NPCs to spot emergent connections.",[11,948,949,950,953],{},"The critical insight: Moment 2 feeds Moment 3, which enriches Moment 2 of the next session. The more you capture, the more connections emerge. The more connections exist, the easier improvisation becomes. Prep time should ",[243,951,952],{},"decrease"," per session as the relational web grows.",[11,955,956],{},"The test: can you prep the next session using only your campaign wiki, without re-reading raw session notes? If yes, the system is working. Session prep gets shorter every week because the web is doing the recall for you.",[11,958,959,960],{},"For the concrete 5 step repeatable workflow that turns this rhythm into a 30 minute habit, see ",[23,961,5],{"href":423},[73,963,965],{"id":964},"what-does-a-living-world-look-like","What Does a Living World Look Like?",[11,967,968,971],{},[14,969,970],{},"A living world is one where the GM is surprised by their own creation."," Not because they forgot what they wrote but because the connections between entries surface narrative possibilities they didn't consciously plan. The merchant's hometown is threatened. The cleric's deity has a rivalry with the faction's patron god. The abandoned temple is linked to the same plague that orphaned two NPCs in different cities. None of these were designed. They emerged from the accumulation of relational decisions made over months of play.",[11,973,974,975,978,979,982],{},"After 10, 20, 50 sessions, the campaign wiki isn't a reference document, it's an emergent narrative engine. The ",[23,976,977],{"href":272},"entry relationships"," have grown dense enough that prep means browsing connections, not inventing from scratch. The question shifts from \"what should happen next?\" to \"what ",[243,980,981],{},"wants"," to happen next, given everything that's already connected?\"",[11,984,985,986,989],{},"This is where reactive worldbuilding proves its value. A pre-built world has the depth its creator imagined. A reactively built world has the depth its players ",[243,987,988],{},"demanded",", which means every detail is load-bearing, every NPC is relevant, every location has been touched by play. There's no dead content.",[11,991,992,993,995,996,999],{},"Use the ",[14,994,659],{}," and ",[14,997,998],{},"Campaign Wide Connections Web"," as primary prep tools in mature campaigns. Browse the visual web for underused connections, orphaned entries, and narrative threads. The relational dataset is the most valuable artifact your campaign produces.",[11,1001,1002,1003,328],{},"The living world depends on connection density. For the detailed guide on building, labeling, and maintaining that web from your first entry to your hundredth session, see ",[23,1004,683],{"href":682},[11,1006,1007],{},[23,1008,1010],{"href":795,"rel":1009},[341],[14,1011,1012],{},"Start building your world for free, no entry limits →",[11,1014,396,1015,1018,1019,1024],{},[23,1016,401],{"href":399,"rel":1017},[341],"! We also have ",[23,1020,1023],{"href":1021,"rel":1022},"https://blog.kanka.io",[341],"more tutorials"," on our blog.",{"title":238,"searchDepth":404,"depth":404,"links":1026},[1027,1028,1029,1030,1031,1032],{"id":503,"depth":404,"text":504},{"id":623,"depth":404,"text":624},{"id":691,"depth":404,"text":692},{"id":807,"depth":404,"text":808},{"id":907,"depth":404,"text":908},{"id":964,"depth":404,"text":965},"Stop building worlds you'll never use. Start with one town, expand from play, and let a relational system keep it all connected. Free, no entry limits.",{},{"title":433,"description":1033},"learn/00.worldbuilding",[1038,1039],"worldbuilding","hub","cGiqMRkQ137bcI6hmW4NKxDVQIdGHe5crMAzJ51bN_0",{"id":1042,"title":615,"author":6,"body":1043,"cta":1398,"datePublished":418,"description":1399,"extension":420,"meta":1400,"navigation":422,"path":614,"seo":1401,"stem":1402,"tags":1403,"tracking":1406,"__hash__":1407},"learn/learn/01.hierarchies.md",{"type":8,"value":1044,"toc":1393},[1045,1066,1069,1076,1085,1089,1095,1098,1158,1161,1164,1172,1174,1177,1183,1186,1196,1206,1209,1216,1220,1226,1233,1240,1243,1286,1289,1292,1309,1314,1316,1319,1323,1329,1332,1338,1341,1344,1350,1356,1358,1361,1368,1383,1385],[11,1046,1047,1049,1050,21,1052,27,1054,27,1058,27,1060,21,1063,1065],{},[14,1048,16],{}," How to structure locations so any place in your world is findable in under 10 seconds, whether you have 15 entries or 500. ",[14,1051,20],{},[23,1053,590],{"href":154},[23,1055,1057],{"href":1056},"/features#maps","Maps",[23,1059,448],{"href":272},[23,1061,1062],{"href":154},"Tags",[14,1064,46],{}," 20 minutes",[11,1067,1068],{},"Every campaign hits the same wall. You've got 40 locations in a flat list, a player asks \"wait, is the Iron Bazaar in Thornmere or Ashenmoor?\" and you're panicking, scrolling through entries trying to remember. Both cities have markets, why didn't you give them more detail when you wrote it down!. The problem is that list doesn't encode spatial relationships. You built a filing cabinet when you needed a map of your world's geography.",[11,1070,1071,1072,1075],{},"The fix isn't more notes. It's a ",[23,1073,1074],{"href":154},"location hierarchy"," that mirrors how your world actually works: continents contain regions, regions contain settlements, settlements contain districts and buildings. When you nest locations inside each other, browsing Thornmere's entry shows you every sub-location at a glance. The structure answers the question before you finish typing.",[11,1077,1078,1079,1081,1082,1084],{},"This tutorial covers the hierarchy depth that handles 95% of campaigns, when to create new locations, and how uploaded maps connect to your ",[23,1080,445],{"href":154},". If you haven't read our hub article on ",[23,1083,70],{"href":69},", start there, it introduces the concentric circles model we'll build on here.",[73,1086,1088],{"id":1087},"how-deep-should-hierarchies-go","How Deep Should Hierarchies Go?",[11,1090,1091,1094],{},[14,1092,1093],{},"Three to four levels of nesting handle 95% of campaign worlds."," More than that creates navigation overhead that costs more than it saves.",[11,1096,1097],{},"Here's what works for most campaigns:",[90,1099,1100,1112],{},[93,1101,1102],{},[96,1103,1104,1107,1109],{},[99,1105,1106],{"align":101},"Level",[99,1108,723],{"align":101},[99,1110,1111],{"align":101},"Location Type",[110,1113,1114,1125,1136,1147],{},[96,1115,1116,1119,1122],{},[115,1117,1118],{"align":101},"1 — Continent/World",[115,1120,1121],{"align":101},"The Sunward Reaches",[115,1123,1124],{"align":101},"Continent",[96,1126,1127,1130,1133],{},[115,1128,1129],{"align":101},"2 — Region/Province",[115,1131,1132],{"align":101},"Thornmere Province",[115,1134,1135],{"align":101},"Region",[96,1137,1138,1141,1144],{},[115,1139,1140],{"align":101},"3 — Settlement",[115,1142,1143],{"align":101},"Thornmere City",[115,1145,1146],{"align":101},"City",[96,1148,1149,1152,1155],{},[115,1150,1151],{"align":101},"4 — District/Building",[115,1153,1154],{"align":101},"The Iron Bazaar, Castle Ward, Docks District",[115,1156,1157],{"align":101},"Market, Fortress, District",[11,1159,1160],{},"This structure maps to how players actually think about space. \"We're heading to the Iron Bazaar\" triggers a mental chain: that's in Thornmere City, in Thornmere Province, somewhere in the Sunward Reaches. The hierarchy encodes that chain so you don't have to remember it.",[11,1162,1163],{},"The exception is dungeon-heavy campaigns. If you're tracking individual rooms in a megadungeon, add a fifth level — but the dungeon itself stays a Location at level 4, with rooms as children. You're still within the guideline.",[234,1165,1168,1169],{"url":1166,"alt":1167,"asset":238},"images/screenshots/learn/sunward.png","Sunward Reaches","\n\nLocation tree in Kanka showing The Sunward Reaches > Thornmere Province > Thornmere City > Iron Bazaar / Castle Ward / Docks District, with Ashenmoor as a sibling of Thornmere City\n",[1170,1171],"br",{},[11,1173,365],{},[11,1175,1176],{},"A few things make this hierarchy work harder for you:",[11,1178,1179,1180,1182],{},"Every Location can have a ",[14,1181,604],{}," — City, Dungeon, Building, Wilderness, Natural Feature. This isn't just labeling. It enables cross-hierarchy filtering: \"show me all Dungeons regardless of which region they're in.\" That filter saves serious time when your world grows past 100 entries.",[11,1184,1185],{},"Create parent Locations before children, even if the parent is just a name with no description yet. A region called \"Thornmere Province\" with nothing but a name is better than three orphaned cities you'll have to reorganize later.",[11,1187,992,1188,1191,1192,1195],{},[14,1189,1190],{},"Nested Layout Toggle"," during prep to see the full tree structure. Switch to ",[14,1193,1194],{},"Flatten Layout Toggle"," during sessions, flat lists are faster to scan when a player catches you off-guard.",[11,1197,1198,1199,1201,1202,1205],{},"Not everything fits a parent-child model, though. Trade routes between Thornmere and Ashenmoor, border disputes, military alliances, these are lateral connections, not hierarchical. Use ",[23,1200,273],{"href":272}," for these. Set up a \"Trade Route\" relation between two cities, a \"Border Dispute\" between two regions. These cross-references turn static geography into a political and economic web, a ",[23,1203,1204],{"href":154},"living world"," where the spatial layer connects to everything else.",[11,1207,1208],{},"Parent-child hierarchy handles spatial containment. Relations handle everything else: trade, conflict, alliance.",[11,1210,1211,1212,1215],{},"This section establishes the spatial skeleton of your ",[23,1213,1214],{"href":453},"campaign wiki",". But a skeleton is empty without inhabitants. The next question: when do you actually create these locations?",[73,1217,1219],{"id":1218},"when-do-you-add-new-locations","When Do You Add New Locations?",[11,1221,1222,1225],{},[14,1223,1224],{},"Create a location when players are about to visit it, or when an existing entry references it."," Not before.",[11,1227,1228,1229,1232],{},"The concentric circles model from the ",[23,1230,1231],{"href":69},"hub article"," gives you the timing. Circle 1 locations, the starting settlement and its key buildings, exist before session 1. Circle 2 locations emerge during sessions 2–5 as the party explores outward. Circle 3 locations get created only when an NPC names them or a quest points there.",[11,1234,1235,1236,1239],{},"The discipline is resisting the urge to build every location on your map before session one. A location that players never visit is part of the lore, but not part of your player's world. Worldbuilding is fun, but if you're being a bit utilitarian, don't use too much of your ",[23,1237,1238],{"href":30},"session prep"," time without producing any play value. A location created in response to player action is guaranteed to be relevant.",[11,1241,1242],{},"A new location needs only three things at creation:",[90,1244,1245,1255],{},[93,1246,1247],{},[96,1248,1249,1252],{},[99,1250,1251],{"align":101},"Field",[99,1253,1254],{"align":101},"Why It's Required",[110,1256,1257,1267,1276],{},[96,1258,1259,1264],{},[115,1260,1261],{"align":101},[14,1262,1263],{},"Name",[115,1265,1266],{"align":101},"You can't reference what you can't name",[96,1268,1269,1273],{},[115,1270,1271],{"align":101},[14,1272,604],{},[115,1274,1275],{"align":101},"Enables filtering across the hierarchy",[96,1277,1278,1283],{},[115,1279,1280],{"align":101},[14,1281,1282],{},"Parent Location",[115,1284,1285],{"align":101},"Prevents orphans and places the location in spatial context",[11,1287,1288],{},"Everything else can wait. Description, population, political affiliations, you can add those when the party approaches or when you're prepping the session that features it.",[11,1290,1291],{},"For locations mentioned in conversation but not yet visited, create a seed entry. You can create a tag called \"Status:Seed\" so you know it's a placeholder and you can come back to it later to add content. Don't flesh it out until the party is two sessions away. This is how your world grows organically without overwhelming your prep schedule.",[11,1293,1294,1295,1297,1298,1301,1302,1305,1306,1308],{},"Press ",[14,1296,929],{}," or click the ",[14,1299,1300],{},"Create"," button to create locations mid-session. Name, Type, Parent, done in under 15 seconds. Then add one ",[667,1303,1304],{},"@mention"," linking the new location to whatever spawned it: the NPC who mentioned it, the quest that leads there, the ",[23,1307,939],{"href":30}," where it first appeared. That single link ensures the location is never disconnected from its narrative origin.",[234,1310,1313],{"url":1311,"alt":1312,"asset":238},"images/screenshots/learn/quick-creator-location.png","Médina Map","\n\nQuick Creator showing a new location being created with Name, Type, and Parent Location fields filled in\n\n",[11,1315,365],{},[11,1317,1318],{},"When you write location descriptions, write from the arriving party's perspective. What do they see, hear, smell? This turns your wiki from a dry reference document into something you can read aloud at the table. \"The salt wind hits you before you see the harbor\" is more useful mid-session than \"Thornmere is a coastal trading city.\"",[73,1320,1322],{"id":1321},"how-do-maps-fit-in","How Do Maps Fit In?",[11,1324,1325,1328],{},[14,1326,1327],{},"Maps are the visual layer over your location hierarchy — not a replacement for it."," A beautiful map shows where things are. The hierarchy shows what those places contain, who lives there, and how they connect.",[11,1330,1331],{},"Upload maps you've created in any tool: Inkarnate, Wonderdraft, Dungeon Scrawl, or hand-drawn and scanned, directly to Kanka. Then add interactive pins linked to your Location entries. Clicking a pin shows the full location profile: geography and lore unified. Your players see the map; clicking a city pin shows them everything you've made visible about that city.",[11,1333,1334,1335,1337],{},"The two systems complement each other. The map provides spatial intuition: distances, terrain, borders at a glance. The ",[23,1336,445],{"href":154}," provides relational depth, who rules there, what factions operate, which quests point to that region. Neither replaces the other.",[11,1339,1340],{},"Here's how to get the most from map integration:",[11,1342,1343],{},"Upload maps at the highest reasonable resolution. Players will zoom in during sessions, and blurry maps break immersion faster than any lore inconsistency.",[11,1345,587,1346,1349],{},[14,1347,1348],{},"Map Groups"," to organize pins into logical clusters: \"Cities,\" \"Dungeons,\" \"Points of Interest,\" \"Secret Locations.\" This keeps your map readable as pin count grows.",[234,1351,1353,1354],{"url":1352,"alt":1312,"asset":238},"images/screenshots/learn/map.png","\n\nMap with grouped pins showing Cities (visible to all) and Secret Locations (admin-only) groups\n",[1170,1355],{},[11,1357,365],{},[11,1359,1360],{},"Pin placement is an ongoing activity. Add pins as new locations enter play. Don't try to pin everything on day one, that's the same overbuilding trap we talked about with location entries. Let the map grow alongside the campaign.",[11,1362,1363,1364,1367],{},"For campaigns spanning multiple scales or timelines, use ",[14,1365,1366],{},"Map Layer"," hierarchy for multi-scale mapping. Your world map serves as the base layer. Different layers of detail are here to add… layers relevant to any different set of circumstances. Think adding/removing historical borders. They use the base image and adapt it to your time context.",[11,1369,1370,1371,1374,1375,1378,1379,1382],{},"Locations are where your world's geography lives. But they're also where ",[23,1372,1373],{"href":687},"factions operate",". Linking ",[14,1376,1377],{},"Organization"," entries to their territorial Locations transforms static geography into a political landscape which is exactly what the ",[23,1380,1381],{"href":687},"next article in this series"," covers.",[49,1384],{},[11,1386,396,1387,1018,1390,1024],{},[23,1388,401],{"href":399,"rel":1389},[341],[23,1391,1023],{"href":1021,"rel":1392},[341],{"title":238,"searchDepth":404,"depth":404,"links":1394},[1395,1396,1397],{"id":1087,"depth":404,"text":1088},{"id":1218,"depth":404,"text":1219},{"id":1321,"depth":404,"text":1322},"Hierarchies That Scale","Organize fantasy locations from continent to single room. A D&D world building hierarchy that stays searchable as your campaign grows past 200 entries",{},{"title":615,"description":1399},"learn/01.hierarchies",[1404,1405],"locations","hierarchy","hierarchies","2M86haCiSih-pe9hDwgh63rtypWIDiJ0vhdXFMAf-74",{"id":1409,"title":1410,"author":6,"body":1411,"cta":1860,"datePublished":418,"description":1861,"extension":420,"meta":1862,"navigation":422,"path":619,"seo":1863,"stem":1864,"tags":1865,"tracking":1866,"__hash__":1868},"learn/learn/02.characters.md","NPC Management for Game Masters: Track Characters That Actually Matter",{"type":8,"value":1412,"toc":1849},[1413,1433,1435,1438,1448,1451,1458,1462,1468,1474,1477,1483,1537,1541,1544,1553,1566,1582,1585,1587,1591,1594,1665,1672,1680,1684,1694,1705,1709,1712,1765,1772,1777,1779,1783,1786,1812,1818,1822,1833,1839,1841],[11,1414,1415,1417,1418,21,1420,1423,1424,27,1427,1429,1430,1432],{},[14,1416,16],{}," How to create NPCs that stay useful across dozens of sessions, connect them to your world, and find them instantly mid-game. ",[14,1419,20],{},[23,1421,1422],{"href":154},"Character"," entries, ",[23,1425,1426],{"href":272},"Entry Relations",[23,1428,43],{"href":42},", Property Kits ",[14,1431,46],{}," 15 minutes for your first three NPCs",[49,1434],{},[11,1436,1437],{},"Session 6. A player says: \"We want to go back and talk to that blacksmith from session 2.\" You created him on the fly, name: \"Brom.\" No other details. In a flat note system, you search \"Brom\" and find a single line. What did he look like? What did he know? Where was his shop?",[11,1439,1440,1441,1444,1445,1447],{},"Now picture the alternative. Brom's ",[23,1442,1443],{"href":154},"Character entry"," shows a Location relation (\"Shop in Thornmere's Market District\"), his @mentions in the session 2 journal (\"Brom mentioned strange noises from the old mine\"), and a single Tag (",[667,1446,211],{},"). In Kanka, Tags are an incredibly convenient way to group entries that don’t always fit under the same umbrella, like Gods. They might be creatures, they might be Characters, but giving them that Deity Tag makes it oh so much easier to find them. You have everything you need to improvise a rich follow-up — because the system captured the connective context around Brom, not just his name.",[11,1449,1450],{},"That's the difference between storing NPCs and actually managing them. This guide covers the creation pattern that makes every Non-Player Character findable, connected, and worth keeping.",[11,1452,1453,1454,1457],{},"If you're building your world from the ground up, our ",[23,1455,1456],{"href":69},"Worldbuilding Fundamentals hub"," covers the broader structure this fits into.",[73,1459,1461],{"id":1460},"how-many-npcs-do-you-need","How Many NPCs Do You Need?",[11,1463,1464,1467],{},[14,1465,1466],{},"Three deep NPCs with real connections beat twenty shallow names in a spreadsheet."," The \"NPC bloat\" problem isn't about memory. It's about signal to noise ratio.",[11,1469,1470,1471,1473],{},"A campaign with 200 NPCs where 180 have nothing but a name is harder to search than a campaign with 20 where each one links to ",[23,1472,1404],{"href":154},", factions, and plot. The litmus test: if an NPC doesn't have at least one Relation to another entry, they're not yet fully integrated into your world..",[11,1475,1476],{},"Start with three for session 1: a quest-giver, an ally, and an obstacle. Create every other NPC reactively: only when a player engages with a background character enough to make them worth tracking. Don't build profiles for unnamed tavern patrons. Build them for Brom, the blacksmith your players decided to care about.",[11,1478,1479,1480,1482],{},"Here's the ceiling and floor for ",[23,1481,1238],{"href":30},":",[90,1484,1485,1495],{},[93,1486,1487],{},[96,1488,1489,1492],{},[99,1490,1491],{"align":101},"Guideline",[99,1493,1494],{"align":101},"Rule",[110,1496,1497,1505,1513,1521,1529],{},[96,1498,1499,1502],{},[115,1500,1501],{"align":101},"Session 1 minimum",[115,1503,1504],{"align":101},"3 NPCs (quest-giver, ally, obstacle)",[96,1506,1507,1510],{},[115,1508,1509],{"align":101},"Session 1 maximum",[115,1511,1512],{"align":101},"10 named NPCs",[96,1514,1515,1518],{},[115,1516,1517],{"align":101},"Creation trigger",[115,1519,1520],{"align":101},"A player interacts with the character",[96,1522,1523,1526],{},[115,1524,1525],{"align":101},"Archive trigger",[115,1527,1528],{"align":101},"If repeatedly no relations after multiple sessions, consider merging, archiving, or connecting",[96,1530,1531,1534],{},[115,1532,1533],{"align":101},"Background characters",[115,1535,1536],{"align":101},"Don't create entries for unnamed crowds",[260,1538,1540],{"id":1539},"the-three-point-creation-pattern","The Three-Point Creation Pattern",[11,1542,1543],{},"Every NPC gets three things at birth. No more, no less.",[11,1545,1546,1549,1550,1552],{},[14,1547,1548],{},"1. A Type field."," Not a physical description, a role. \"Innkeeper,\" \"Guard Captain,\" \"Fence.\" During play, you're scanning for function, not eye color. Put the role in the ",[14,1551,604],{}," field on the Character entry. It shows up in search results and hover previews, so you can spot the right NPC without clicking through.",[11,1554,1555,1558,1559,1561,1562,1565],{},[14,1556,1557],{},"2. One Relation."," Link the NPC to a Location or Organization. Click ",[14,1560,448],{}," on the Character's overview, add a connection to wherever they operate. Brom gets linked to Thornmere's Market District. Now searching for that Location also surfaces Brom, ",[23,1563,1564],{"href":272},"cross-referencing"," happens automatically.",[11,1567,1568,1571,1572,1575,1576,1578,1579,1581],{},[14,1569,1570],{},"3. One @mention."," Write ",[667,1573,1574],{},"@Brom"," in the ",[23,1577,939],{"href":30}," where they first appear. That's it. The ",[23,1580,43],{"href":42}," auto-links to Brom's full profile and adds the journal to his \"Mentioned In\" list. Over time, this list becomes Brom's story: every scene he appeared in, every plot thread he touched, aggregated without extra work.",[11,1583,1584],{},"[Screenshot: Character entry for \"Brom\" showing Title field (\"Blacksmith\"), one Relation to \"Thornmere - Market District,\" and a Mentioned In list with two session journal links]",[11,1586,365],{},[260,1588,1590],{"id":1589},"the-character-card-pattern","The Character Card Pattern",[11,1592,1593],{},"For NPCs who stick around past their first scene, apply a Property Kit with 3–5 lightweight fields. Create the template once, then apply it to every new NPC with a click.",[90,1595,1596,1608],{},[93,1597,1598],{},[96,1599,1600,1603,1606],{},[99,1601,1602],{"align":101},"Property",[99,1604,1605],{"align":101},"Purpose",[99,1607,723],{"align":101},[110,1609,1610,1621,1632,1643,1654],{},[96,1611,1612,1615,1618],{},[115,1613,1614],{"align":101},"Motivation",[115,1616,1617],{"align":101},"What drives them",[115,1619,1620],{"align":101},"\"Revenge against the Guild\"",[96,1622,1623,1626,1629],{},[115,1624,1625],{"align":101},"Secret",[115,1627,1628],{"align":101},"What they're hiding",[115,1630,1631],{"align":101},"\"Works for the Merchant Consortium\"",[96,1633,1634,1637,1640],{},[115,1635,1636],{"align":101},"Attitude Toward Party",[115,1638,1639],{"align":101},"Current disposition",[115,1641,1642],{"align":101},"\"Suspicious, trusts no one new\"",[96,1644,1645,1648,1651],{},[115,1646,1647],{"align":101},"Voice Note",[115,1649,1650],{"align":101},"One-line speech cue",[115,1652,1653],{"align":101},"\"Speaks slowly, avoids eye contact\"",[96,1655,1656,1659,1662],{},[115,1657,1658],{"align":101},"Status",[115,1660,1661],{"align":101},"Campaign lifecycle tag",[115,1663,1664],{"align":101},"\"Active / Seed / Archived\"",[11,1666,1667,1668,1671],{},"Set up the kit by clicking on ",[14,1669,1670],{},"Property Kits"," in your sidebar.",[11,1673,1674,1675,1679],{},"For NPCs who are merchants or carry plot-relevant items, add entries to their ",[23,1676,1678],{"href":1677},"/features#inventory","inventory",". Each item can either link to an Item entry, or remain free text for now, creating another relational thread your players can pull on.",[73,1681,1683],{"id":1682},"how-do-npcs-connect-to-everything","How Do NPCs Connect to Everything?",[11,1685,1686,1689,1690,1693],{},[14,1687,1688],{},"An NPC's value isn't in their profile it's in their connections."," A 500-word backstory that connects to nothing is less useful than a one-line character with entry ",[23,1691,1692],{"href":272},"relationships"," to two Locations, one Organization, and three other Characters.",[11,1695,1696,1697,1700,1701,1704],{},"The connections are what make NPCs findable, surprising, and useful during play. When you search a Location, related NPCs surface. When you open an Organization, its members appear. When you check a Character, their allies and enemies show up. This is ",[23,1698,1699],{"href":272},"auto-linking"," doing the memory work for you, it helps your campaign become a living index your ",[23,1702,1703],{"href":25},"Campaign Dashboard"," showcases.",[260,1706,1708],{"id":1707},"the-connection-minimum","The Connection Minimum",[11,1710,1711],{},"After an NPC has appeared in 2+ sessions, they earn three Relations:",[90,1713,1714,1726],{},[93,1715,1716],{},[96,1717,1718,1721,1724],{},[99,1719,1720],{"align":101},"Relation Type",[99,1722,1723],{"align":101},"What It Creates",[99,1725,723],{"align":101},[110,1727,1728,1741,1753],{},[96,1729,1730,1735,1738],{},[115,1731,1732],{"align":101},[14,1733,1734],{},"Location",[115,1736,1737],{"align":101},"Where they operate",[115,1739,1740],{"align":101},"Brom → \"Runs shop in\" → Thornmere City",[96,1742,1743,1747,1750],{},[115,1744,1745],{"align":101},[14,1746,1377],{},[115,1748,1749],{"align":101},"Who they serve or oppose",[115,1751,1752],{"align":101},"Brom → \"Secretly reports to\" → Thieves' Guild",[96,1754,1755,1759,1762],{},[115,1756,1757],{"align":101},[14,1758,1422],{},[115,1760,1761],{"align":101},"Who they know",[115,1763,1764],{"align":101},"Brom → \"Owes a debt to\" → Captain Aldara",[11,1766,1767,1768,1771],{},"Use custom Relation labels that tell a story. \"Owes a debt to\" is more useful mid-session than \"Connected to.\" Enable ",[14,1769,1770],{},"Reciprocal link"," on the Character entry so connections are always bidirectional, linking Brom to the Thieves' Guild automatically creates the reverse link on the Guild's page.",[234,1773,1776],{"url":1774,"alt":1775,"asset":238},"images/screenshots/learn/brom.png","Brom","\n\nBrom is connected to Thornmere City, the Thieve's guild, and has a relation to Captain Aldara\n\n",[11,1778,365],{},[260,1780,1782],{"id":1781},"identity-fields-players-ask-about","Identity Fields Players Ask About",[11,1784,1785],{},"Fill the fields your table actually references during play:",[1787,1788,1789,1796,1806],"ul",{},[1790,1791,1792,1795],"li",{},[14,1793,1794],{},"Pronouns"," — dedicated field on every Character entry",[1790,1797,1798,1801,1802,1805],{},[14,1799,1800],{},"Age",": While the Age field is free text, you can create a reminder after the character is created, and it can be linked to your ",[23,1803,1804],{"href":38},"fantasy calendar",", which will then show their age in relation to the ‘present’.",[1790,1807,1808,1811],{},[14,1809,1810],{},"Appearance Traits"," — keep it to one sentence; players remember \"missing left hand\" better than a paragraph",[11,1813,1814,1815,1817],{},"The ",[14,1816,1658],{}," field on Character entries works as an archival tool. Deceased NPCs keep all their Relations as historical context: a dead NPC's connections still tell the story of who they were, while someone missing might signal that they are part of the next hook.",[260,1819,1821],{"id":1820},"deeper-connection-tools","Deeper Connection Tools",[11,1823,1824,1825,1828,1829,1832],{},"For dynasty or lineage NPCs, use ",[23,1826,1827],{"href":154},"Family entries"," with member tracking instead of just Character-to-Character Relations. Premium campaigns get ",[14,1830,1831],{},"Family Tree Visualization"," for visual genealogy mapping.",[11,1834,1835,1836,1838],{},"Individual NPC connections are the atoms of your ",[23,1837,1214],{"href":154},". At scale, these connections form emergent patterns — faction alliances, regional power structures, narrative themes.",[49,1840],{},[11,1842,396,1843,1018,1846,1024],{},[23,1844,401],{"href":399,"rel":1845},[341],[23,1847,1023],{"href":1021,"rel":1848},[341],{"title":238,"searchDepth":404,"depth":404,"links":1850},[1851,1855],{"id":1460,"depth":404,"text":1461,"children":1852},[1853,1854],{"id":1539,"depth":411,"text":1540},{"id":1589,"depth":411,"text":1590},{"id":1682,"depth":404,"text":1683,"children":1856},[1857,1858,1859],{"id":1707,"depth":411,"text":1708},{"id":1781,"depth":411,"text":1782},{"id":1820,"depth":411,"text":1821},"Track Characters That Actually Matter","Stop losing NPCs in scattered notes. Link every character to their location, faction, and quest so context surfaces the moment a player asks. Free, any system",{},{"title":1410,"description":1861},"learn/02.characters",[1866,1867],"characters","npcs","mlQuav-3rER_vh8okVfSLSmWk8SWIZBcqT7Wsm-UiTQ",1775837391771]