Skip to content

Latest commit

 

History

History
executable file
·
321 lines (256 loc) · 17.6 KB

File metadata and controls

executable file
·
321 lines (256 loc) · 17.6 KB

LuminariMUD Technical Documentation Master Index

Last Updated: 2026-08-14 Version: 1.4

Documentation Overview

This master index provides a comprehensive guide to all technical documentation for LuminariMUD. Documents are organized by category and purpose to help developers, builders, and administrators quickly find the information they need.

Quick Links


Setup & Getting Started

Essential First Steps

Configuration & Installation


Architecture & Core Systems

System Architecture

Database & Persistence

Communication & Protocols


Game Systems

Product Requirements

Core Mechanics

Advanced Systems

Building & Scripting

Utility Systems


Development Guides

Core Development

Performance & Optimization

Troubleshooting


Building & Content Creation

Building Guides

World File Formats

Equipment & Items

  • CRAFTING_SYSTEM_NOTES.md - Crafting system design notes (partial; verify against src/craft/)
  • gear_guide.md - Combined gear stat distribution (equipment balance, loot generation, stats by wear location)

Administration & Operations

Admin Tools

  • Incident response - Source-backed diagnosis, containment, and recovery
  • Admin README - Legacy administration overview
  • FAQ.md - Legacy gameplay/administration FAQ; current operator commands are linked at its top

Utilities

Legal & Licensing


Project Management

Planning & Tracking

Project Documents

  • Ongoing projects - Active work and retained handoffs: production autosave and memory follow-up, artifact placement, AI conversation history, SKORE phases 3-4, event-system merge, and in-game backlogs
  • artifact-placement-plan.md - World-building brief for placing artifacts in player-facing content, the artifact system's one remaining open item
  • AI_TODO_IDEAS.md - AI conversation history implementation plan
  • DO_SKORE_PROJECT.md - Skore system phases 3-4
  • IDEA_LIST.md - Player and staff feature idea backlog

Historical Records


Document Categories

By Audience

For New Developers

  1. README.md
  2. onboarding.md
  3. SETUP_AND_BUILD_GUIDE.md
  4. development.md
  5. ARCHITECTURE.md
  6. CONTRIBUTING.md

For System Administrators

  1. deployment.md
  2. DEPLOYMENT_GUIDE.md
  3. incident-response.md
  4. DATABASE_INTEGRATION.md
  5. TROUBLESHOOTING_AND_MAINTENANCE.md

For Content Builders

  1. OLC_ONLINE_CREATION_SYSTEM.md
  2. SCRIPTING_SYSTEM_DG.md
  3. ultimate-mud-writing-guide.md
  4. Building guides in world_game-data/
  5. world/STARTER_AREA.md

For Core Contributors

  1. DEVELOPER_GUIDE_AND_API.md
  2. PERFORMANCE_OPTIMIZATIONS.md
  3. TESTING_GUIDE.md
  4. All system documentation

By Technical Depth

Introductory (Beginner)

  • README.md
  • FAQ.md
  • CODE_OF_CONDUCT.md
  • ultimate-mud-writing-guide.md

Intermediate

  • DEPLOYMENT_GUIDE.md
  • OLC_ONLINE_CREATION_SYSTEM.md
  • GAME_MECHANICS_SYSTEMS.md
  • Building guides

Advanced

  • ARCHITECTURE.md
  • CORE_SERVER_ARCHITECTURE.md
  • DEVELOPER_GUIDE_AND_API.md
  • PERFORMANCE_OPTIMIZATIONS.md

Reference

  • DATABASE_INTEGRATION.md
  • SCRIPTING_SYSTEM_DG.md
  • COMMAND_SYSTEM_AND_INTERPRETER.md
  • PROTOCOL_SYSTEMS.md

Finding Information

Quick Search Tips

  1. By Feature: Look in systems/ directory
  2. By Task: Check guides/ directory
  3. By Problem: See TROUBLESHOOTING_AND_MAINTENANCE.md
  4. By Code: Refer to DEVELOPER_GUIDE_AND_API.md

Document Naming Convention

  • README.md - Root repository overview only
  • README_<directory>.md - Subdirectory overview documents
  • *_SYSTEM.md - System documentation
  • *_GUIDE.md - How-to guides
  • *_TODO.md - Planning documents
  • *_TASK_LIST.md - Work tracking

Documentation Standards

  • All docs use Markdown format
  • Code examples follow GNU C23 and the established source style
  • Internal links use relative paths
  • External links include descriptions

Notes

Current Audit Boundary

The Phase 00 transition audit is recorded in docs-audit.md. It verifies the required project entry points, the special-procedure documentation delivered in Phase 00, and the operational health/deployment surface. Older subsystem documents remain independently maintained and must be retraced before behavioral edits.

Contributing to Documentation

  1. Follow markdown best practices
  2. Include code examples where relevant
  3. Keep technical accuracy paramount
  4. Update this index when adding new docs
  5. Test all commands and code examples

This index is maintained as part of the LuminariMUD project. For corrections or additions, please submit a pull request or contact the development team.