100 Discord Bots resources for MUD players

The industry standard for JavaScript-based MUD engines like Ranvier. Use it to handle message events and rich embed construction for game status updates.

Ideal for Evennia-based MUDs. Provides an asynchronous framework that integrates well with Twisted or Trio loops used in game engine networking.

A pre-built component for the Evennia MUD library that handles channel-to-channel relaying out of the box with minimal configuration.

A high-performance library for MUDs written in Rust or C++ (via FFI). Offers memory safety and low overhead for high-traffic combat logs.

Client-side integration using Lua to update a player's Discord status with their current zone, level, and health from the MUD client.

The preferred library for MUDs running on the .NET ecosystem. Supports full API coverage including the latest slash command features.

A helper library to facilitate the bot side of a bridge connecting to an older C/C++ MUD that lacks a native HTTP/JSON API.

A lightweight wrapper for sending one-way notifications from the MUD to Discord without the overhead of a full bot connection.

Standard library for Java-based MUDs like CoffeeMud. Provides a clean, functional API for handling bridge events.

Essential utility for stripping MUD color codes (e.g., [31m) and converting them to Discord-readable markdown or removing them entirely.

Trigger a webhook whenever a player is killed. Include the killer's name and the room location to drive community engagement and rivalry.

Post significant milestones (e.g., reaching level 50 or a Remort) to a dedicated 'achievements' channel using Discord embeds.

Relay in-game auction starts and bids to Discord so players can track rare item sales while away from the terminal.

Map the in-game 'bug' or 'typo' commands to a private Discord staff channel using webhooks for faster administrative response.

A standalone script that pings the MUD port and updates a Discord message or channel name to show 'Online' or 'Offline' status.

Notify staff when a new account is created. This allows greeters to log in and assist the newcomer immediately.

A scheduled task that queries the MUD database and posts the top 10 players by XP or Gold to a 'rankings' channel.

Automated posts for recurring events like 'Double XP Weekends' or 'Invasion' triggers to pull inactive players back into the game.

Use the Generic Mud Communication Protocol to send structured JSON data to a bridge bot instead of scraping raw text.

Bi-directional communication between a specific Discord channel and the in-game OOC channel. Requires careful rate limiting.

Never hardcode Discord Bot Tokens or Webhook URLs in the MUD source code. Use .env files or system environment variables.

Implement a local queue for outgoing Discord messages to prevent the MUD from being globally rate-limited by Discord's API during high activity.

Strip '@everyone' and '@here' tags from in-game chat before relaying to Discord to prevent players from pinging the entire server.

Ensure Discord API calls are made asynchronously. In older MUDs, a slow HTTP request can freeze the entire game loop for all players.

Implement exponential backoff for the bot's connection logic to avoid spamming Discord's gateway during MUD server restarts.

Sync Discord roles with MUD staff levels, allowing administrators to execute game commands (like 'reboot') directly from Discord.

Implement logic to ensure the bot ignores its own messages or other bots' messages to prevent infinite chat loops.

Map MUD color codes to Discord markdown (e.g., bold or code blocks) to maintain readability across platforms.

Maintain a local log of all messages passed through the bridge to assist in moderation disputes and identifying bot crashes.

Store Discord User IDs in the player's MUD pfile to allow for cross-platform rewards or account recovery.