md_config.yml. This file controls all aspects of McDis behavior, from Discord connection to process management.
Configuration File Location
Themd_config.yml file must be located in the directory where you run mcdis run (your McDis root directory):
Generating Configuration
Create the default configuration file:md_config.yml with commented examples:
Configuration Structure
The configuration file has several main sections:Bot Token
Discord bot authentication token
Panel ID
Discord channel ID for the control panel
Language
Interface language (en/es)
Backups
Number of backups to retain (1-5)
Flask
File download server configuration
Processes
Server and network definitions
Full Configuration Example
Here’s a complete example with explanations:Configuration Sections Explained
Bot Token
- Type: String
- Required: Yes
- Description: Your Discord bot token from the Discord Developer Portal
Get your bot token from the Discord Developer Portal. See Discord Setup for details.
Panel ID
- Type: Integer
- Required: Yes
- Description: Discord channel ID where the panel will be created
Language
- Type: String
- Required: No
- Default:
en - Valid Values:
en(English),es(Spanish) - Description: Interface language for messages and responses
Backups
- Type: Integer
- Required: No
- Default:
3 - Valid Values: 1-5 (inclusive)
- Description: Maximum number of backup versions to retain per process
When this limit is reached, the oldest backup is automatically deleted when creating a new one.
Flask
-
Allow:
- Type: Boolean
- Default:
false - Description: Enable/disable Flask download server
-
IP:
- Type: String
- Default:
'0.0.0.0' - Description: IP address to bind Flask server (use public IP for external access)
-
Port:
- Type: Integer
- Default:
8000 - Description: Port for Flask server to listen on
Processes
The processes section defines all managed servers and networks:Configuration Validation
McDis-RCON validates configuration on startup:Bot Token Validation
Panel ID Validation
Language Validation
Backups Validation
Flask Validation
Process Validation
If validation fails, McDis-RCON will exit with an error message. Fix the issue in
md_config.yml and restart.Configuration Best Practices
Backup Configuration
Keep a backup copy of
md_config.yml before making changesUse Comments
Add comments to document your configuration decisions
Validate YAML
Use a YAML validator to check syntax before restarting
Version Control
Consider using Git to track configuration changes
Common Configuration Patterns
Single Server Setup
Multi-Server Network
Development Setup
Production Setup
Editing Configuration
You can edit the configuration file:Via File Manager (Discord)
Via SSH/Terminal
Applying Configuration Changes
After editingmd_config.yml:
Troubleshooting Configuration Issues
YAML syntax error
YAML syntax error
Common causes:
- Missing colon after key
- Incorrect indentation (use spaces, not tabs)
- Unquoted strings with special characters
- Missing quotes around strings
Configuration not loading
Configuration not loading
Possible causes:
- File not named
md_config.ymlexactly - File in wrong directory
- File encoding issues
mcdis run and named exactly md_config.yml.Changes not taking effect
Changes not taking effect
Cause:
Configuration is only read on startupSolution:
Restart McDis-RCON after making changes.
Special characters in process names
Special characters in process names
Cause:
Process names can only contain: letters, numbers,
., -, _, spacesSolution:
Rename process to use only allowed characters:Configuration Reference
For detailed information on specific configuration sections:Discord Setup
Bot token and panel configuration
Process Setup
Configuring servers and networks
Advanced Options
Flask, backups, and optimization
Quickstart
Step-by-step first-time setup
Example Configurations
See real-world configurations in production:AeternumBot
Complete configuration for Aeternum SMP
Template Config
Use
mcdis init to generate a template with examples