dMUD: Technical Operations

This document provides guidance for administrators and developers maintaining the dMUD server.

⚙️ Server Maintenance

dMUD is designed for high availability and ease of updates.

• Hot Reloading: Most game data (Rooms, Users, Aliases, and Documentation) can be reloaded while the server is running, eliminating the need for frequent restarts.
• Data Persistence: All critical data is stored in human-readable INI and JSON formats, simplifying backups and manual audits.

🛠️ Standalone Build

For development and CI/CD environments, dMUD can be built in "Standalone Mode."

• No AI Dependencies: In this mode, the server operates without the full Assistant framework, making it lightweight and suitable for testing core game engine features.
• Mocked Agents: Agents are replaced with stubs that simulate presence without requiring LLM backend calls.

📈 Monitoring & Debugging

• Performance Metrics: The system logs execution times for high-impact operations like NPC script triggers and room transitions.
• Structured Logs: Critical server events are recorded with detailed context to help diagnose concurrency issues or state mismatches.
• Automated Testing: A dedicated test bot is available to simulate multi-user traffic and verify command integrity across all world phases.