mud

What This Skill Does

The mud skill serves as the primary interface for managing and interacting with the OpenClaw MUD (Multi-User Dungeon) engine. It provides a robust, standardized wrapper around the engine's core functionality, allowing users to execute state-changing commands, perform data validation, and manage persistent player or campaign data without needing to manually trigger scripts. By abstracting complex engine commands into a simple CLI wrapper, this skill ensures that MUD state operations—such as registering players, creating characters, or managing image generation pipelines—are executed deterministically and safely. It acts as the bridge between the high-level LLM-driven narration and the rigid, logical requirements of the underlying MUD game mechanics.

Installation

To integrate this skill into your OpenClaw environment, execute the following command via your terminal: clawhub install openclaw/skills/skills/andrew-goetz-com/mud Once installed, ensure the engine directory is correctly configured. The skill automatically checks C:\Users\openclaw\.openclaw\workspace-mud-dm\mud-agent as the primary workspace, falling back to C:\Users\openclaw\.openclaw\workspace\mud-agent if necessary. Verify your installation by running a smoke test using the script provided in the skill documentation.

Use Cases

• Campaign Management: Initializing new campaigns, managing player registrations, and maintaining character progression across sessions.
• State Validation: Periodically checking the integrity of game data and validating save/restore cycles to prevent data loss.
• Content Generation: Interfacing with the runtime image pipeline to generate, check, or record visual assets for game narrations.
• Debugging: Diagnosing synchronization issues between the MUD engine state and the persistent database.
• Engine Deployment: Automating routine maintenance tasks or updating engine configurations across multiple environments.

Example Prompts

1. "OpenClaw, register a new player 'Adventurer' with player ID 'u7' for our active demo campaign."
2. "Check the status of the image generation cooldown and generate a prompt for a dark dungeon chamber in the current campaign."
3. "Save the current state of the demo campaign to ensure our progress is persisted before I shut down the agent."

Tips & Limitations

• Determinism: Always prioritize the engine's logic for game rules. Use the AI primarily for narrative delivery and creative flair, not for calculating dice rolls or stat adjustments.
• Safety: Avoid manual editing of the raw engine files outside of the provided CLI commands to prevent corruption.
• Performance: For bulk operations, verify the image pipeline status first to avoid hitting rate limits or timeout errors.
• Security: Never expose engine configuration files or internal workspace paths to unauthorized users.