ConsoleDiscord

# ConsoleDiscord ConsoleDiscord connects your Minecraft server console with Discord. - Mirrors your server log into a Discord text channel. - Lets you run console commands from Discord via `/mc` (slash command) or `!mc` (text command). Perfect if you want to monitor and administer your server from Discord without opening the server console every time. --- ## Features - 🔁 **Log streaming** Sends your server log to a configurable Discord channel. - 💬 **Commands from Discord** Execute console commands directly from Discord: - Slash command `/mc` - Optional text command `!mc` in a specific channel - 🔐 **Access control** Limit access to specific Discord user IDs and/or to a single command channel. - ⚙️ **Configurable log interval** `log-flush-ticks` controls how often buffered log lines are sent to Discord. - 🧪 **Debug logging** Optional debug logging for JDA status changes (`debug-status-logging`). - 🔄 **Reload without restart** `/cdr reload` reloads the config and reconnects to Discord if needed. --- ## Requirements - **Server:** Paper / Bukkit-compatible server - **Minecraft:** 1.21.x (api-version: `1.21`) - **Java:** 21 - **Discord:** Your own bot - Bot token - Permissions to: - Read and send messages in the log/command channels - Use slash commands (for `/mc`, if enabled) --- ## Installation 1. **Drop the jar** Put `ConsoleDiscord-1.0.0.jar` into your server’s `plugins/` folder. 2. **Start the server** On first startup, the plugin will create a `config.yml` file in its folder. 3. **Edit the config** (`plugins/ConsoleDiscord/config.yml`) ```yaml bot-token: "YOUR_DISCORD_BOT_TOKEN" # Text channel for server logs log-channel-id: "123456789012345678" # Optional: channel where /mc and !mc may be used command-channel-id: "" # Who is allowed to use /mc and !mc (user IDs). # If empty, everyone is allowed. allowed-user-ids: - "123456789012345678" # How often (in ticks) buffered log messages are flushed to Discord log-flush-ticks: 40 # Log JDA status changes (connect, disconnect, etc.) to the server log debug-status-logging: false