Timeline documents vs Lore bibles vs Quest dependency maps
Managing coherent world history across decades of MUD development requires tools that balance audit trails with accessibility. Timeline contradictions emerge when multiple builders modify canonical events without visibility into dependencies. This comparison evaluates four technical approaches—version-controlled text, collaborative wikis, graph knowledge bases, and integrated databases—based on their ability to track retcons, visualize era transitions, and connect historical data to runtime quest systems.
Git + Markdown Repository
Version-controlled plain text with native diff tracking
Best for: Technical teams requiring immutable audit trails for retcons
github.com ↗Self-Hosted MediaWiki
Collaborative web platform with category hierarchies
Best for: Distributed lore teams needing immediate browser-based editing
www.mediawiki.org ↗Obsidian with Git Sync
Graph-visualized knowledge base linking events and characters
Best for: Navigating complex non-linear timelines and relationship networks
obsidian.md ↗In-Game SQL Lore Tables
Database schema integrated with MUD engine for runtime access
Best for: Quest systems requiring real-time historical state validation
| Criterion | Git + Markdown Repository | Self-Hosted MediaWiki | Obsidian with Git Sync | In-Game SQL Lore Tables | Winner |
|---|---|---|---|---|---|
Version Control Granularity Level of detail available when reviewing historical changes to lore entries | Line-level diffs with blame attribution and branch archaeology | Page-level revision history with rollback functionality | File-level git history requiring manual conflict resolution | Schema migrations and point-in-time backup snapshots | Git + Markdown Repository |
Concurrent Editing Support Capability for multiple builders to modify lore simultaneously without data loss | Branching and merge conflict resolution required for simultaneous work | Real-time collaborative editing with edit conflict alerts | File locking or manual merge conflict management via git | Database row locking with transaction isolation | Self-Hosted MediaWiki |
Visual Relationship Mapping Ability to visualize connections between historical events, characters, and eras | Manual diagram embedding or external visualization tools required | Category trees and Semantic MediaWiki extensions available | Native graph view showing bidirectional backlinks between notes | ER diagrams require external database visualization tools | Obsidian with Git Sync |
Player Accessibility Ease of exposing read-only lore to players without technical barriers | Requires static site generator or raw repository browser access | Built-in web frontend with search and category browsing | Publish plugin or exported static site generation required | Direct integration with MUD 'lore' or 'history' in-game commands | In-Game SQL Lore Tables |
Quest Engine Integration Direct accessibility of historical data from MUD codebase for gameplay logic | Manual cross-referencing; no runtime programmatic access | API parsing required; adds network latency to game loop | No runtime access; requires manual data entry into game | Direct SQL queries from MUD codebase with JOIN capability | In-Game SQL Lore Tables |
Setup Complexity Initial installation and ongoing maintenance requirements | Low; requires git hosting and text editor only | Medium; requires PHP, MySQL, and web server administration | Low; local application with optional git client configuration | High; requires schema design and application code deployment | Git + Markdown Repository |
Data Portability Ease of migrating lore data to different platforms or formats | Universal plain text; completely vendor agnostic | XML export available; requires SQL migration for full portability | Markdown files with YAML frontmatter; widely compatible | Database-specific format; migration scripts required for platform changes | Git + Markdown Repository |
Retcon Audit Capability Ability to review when specific historical facts changed and by whom | Complete history with git blame and branch archaeology | Page history with user attribution and rollback functionality | Git history if configured; otherwise limited to file snapshots | Transaction logs dependent on database configuration | Git + Markdown Repository |
Cross-Reference Linking Native support for connecting related historical events and entities | Manual wiki-style links or relative file paths | Automatic wikilinks and category aggregation | Bidirectional backlinks and graph navigation | Foreign key relationships and JOIN table constructs | Obsidian with Git Sync |
Our Verdict
Git repositories provide immutable audit trails essential for retcon-heavy legacy MUDs but require technical overhead. MediaWiki offers immediate collaboration at the cost of server maintenance overhead. Obsidian excels at visualizing complex interconnected timelines but lacks runtime integration. In-game SQL systems enable dynamic quest dependencies but lock lore data into application-specific schemas, creating migration friction.
Use-Case Recommendations
Scenario: Small development team managing a decades-old MUD with frequent timeline revisions and continuity disputes
→ Git + Markdown Repository with Hugo static site generation
Git blame and branching allow precise tracking of when specific lore elements changed, critical for resolving continuity disputes among veteran players by showing exactly who modified canonical events and when.
Scenario: Large volunteer lore team with non-technical writers contributing to world-building
→ Self-Hosted MediaWiki
Browser-based WYSIWYG editing lowers barrier to entry for non-coders; category system organizes eras without requiring developers to process every update, enabling distributed content creation.
Scenario: Narrative-heavy RP MUD requiring real-time validation of historical prerequisites for quest availability
→ In-Game SQL Lore Tables
Quest code can query historical event tables directly via SQL to check if prerequisites occurred, enabling dynamic storylines that branch based on player actions without hardcoding conditions.
Scenario: Complex setting with non-linear time including flashbacks, alternate timelines, and temporal paradoxes
→ Obsidian with Git Sync
Graph view visualizes temporal branches and cross-era connections that linear documents obscure, aiding writers in maintaining consistency across splintered timelines through visual relationship mapping.
.