Advanced Worldbuilding

This chapter covers advanced worldbuilding techniques: creating timelines, documenting lore, designing factions, and building campaign arcs. It covers the Timeline, Source Reference, Campaign Event, and Session Log file types.

Creating Timelines

A Timeline is an ordered record of historical events, organized by eras and dated events. It's the backbone of your world's history.

Schema conventions:

• franchise: which franchise this timeline covers (for cross-project work)
• eras: ordered array of major periods, each with name, startYear, endYear, summary, and keyEvents
• events: all documented events in chronological order, each with era, date, type, title, description, and significance
• gaps: explicit list of undocumented periods (honest worldbuilding acknowledges what you don't know)
• sources: array of Source Reference files that contribute to this timeline
• loreEntries: array of Lore Detail files that belong to this timeline

Event types: major_battle, minor_battle, political, cultural, technological, magical, disaster, discovery, treaty, other.

Significance levels: major (world-changing), minor (significant but localized), background (contextual).

Design tip: start with the major events, then fill in the gaps. Leave some eras intentionally sparse — mystery drives engagement. The gaps are as important as the events.

Documenting Lore

Lore is the deep knowledge of your world. A Lore file is the broad topic (e.g., "The Veil"). A Lore Detail file is a specific entry within that topic (e.g., "The Saturation Point").

Lore Detail schema conventions:

• category: concept, character, location, event, faction, item, or other
• franchise: which franchise this entry belongs to
• canonStatus: canon, legends, expanded, non_canon, mixed, or unknown
• significance: major, minor, or background
• connections: array of related Lore Detail files
• contradictions: array of known contradictions with other sources
• timelineEvents: array of timeline events this entry relates to
• mechanicsTranslation: how this lore translates to game mechanics
• statsSuggestion: suggested stat values for creatures/characters

Design tip: the contradictions field is crucial. Real-world lore is messy — sources disagree, details evolve, retcons happen. Documenting contradictions makes your world feel lived-in, not sterile.

Designing Factions

Factions are organizations with goals, methods, and internal tensions. A well-designed faction has:

• A clear CE alignment (do they lean Creation or Entropy?)
• A leader with their own agenda
• Internal factions that disagree on methods
• Relationships with other factions (allies, rivals, enemies)
• Spiritual practices that reflect their values

Design tip: the best factions aren't purely good or evil. The Silver Dawn protects the living but can be rigid and judgmental. The Tech Marksman Guild is pragmatic but sometimes ruthless. Give every faction a strength and a blind spot.

Building Campaign Arcs

A campaign arc is a chain of events that drives the story forward. It uses Campaign Events to record what happened, Quests to define what needs to happen, and NPCs to populate the world.

Campaign Event conventions:

• type: quest_update, conversation, discovery, combat, decision, consequence, foreshadowing, social, travel, rest, or other
• status: active, resolved, pending, forgotten, or superseded
• importance: critical, high, normal, or low
• consequences: array of what changed as a result
• followUp: what needs to happen next
• conversationLog: array of who said what, what was revealed

Quest conventions:

• status: proposed, active, completed, or failed
• priority: critical, high, normal, or low
• objectives: array of {status, description} — track progress
• hooks: array of how the quest connects to other content
• npcsInvolved: array of NPC references

Design tip: campaign arcs should escalate. Start with local problems (a haunted village), escalate to regional crises (a Veil Tear), and culminate in world-threatening events (a Lich's army). Each escalation should feel inevitable, not arbitrary.

Session Logging

A Session Log records what happened during a play session. It's the bridge between the fiction and the mechanics.

Schema conventions:

• sessionNumber: sequential integer
• summary: 1–3 sentence overview
• events: array of {type, description, keywords, npcs, characters, location}
• decisions: array of major player decisions
• cliffhangers: array of unresolved threads
• foreshadowing: array of seeds planted for future sessions
• rewards: text describing XP, loot, achievements
• questsUpdated: array of quest references affected
• npcsUpdated: array of NPC references affected
• conditionChanges: array of {character, change, reason} — track HP, mana, conditions
• conversations: array of {topic, outcome, participants, keywords} — record dialogue
• fullLog: detailed narrative (the complete record)
• gmNotes: private GM notes

Design tip: the cliffhangers and foreshadowing fields are your continuity tools. Every session should end with at least one unresolved thread. Every session should plant at least one seed for future payoff.

Source References

A Source Reference documents where your lore comes from. It's essential for maintaining consistency across large projects.

Schema conventions:

• sourceType: wiki, book, film, tv_series, game, official_site, fan_site, sourcebook, manual, interview, user_input, or other
• franchise: which franchise this source covers
• reliability: primary (official canon), secondary (official but supplementary), fan_creation, uncertain, or contradicted
• canonStatus: canon, legends, expanded, non_canon, mixed, or unknown
• keyTopics: array of main topics this source covers
• loreEntries: array of Lore Detail files created from this source
• contradictions: array of known contradictions with other sources
• extractionNotes: what was extracted and any caveats

Design tip: always document your sources. When you're six months into a project and can't remember why a detail is the way it is, the Source Reference saves you. When two sources contradict each other, the contradictions field tells you which to trust.