RDD setup
Connect your Minecraft server to Discord using the Raindrop bot hosted by RaindropCentral.Before you start
Install matching RCore and RDD builds and restart the server. The reviewed candidate is RDD 1.0.0-ALPHA-Build-1 with RCore 2.0.0-BETA-Build-4. Native local checks used Paper and Folia 26.2 on Java 25; declared backport support is separate from native qualification. LuckPerms or Vault and PlaceholderAPI are optional.
Register and verify
Register the Minecraft server through RCore using its versioned Central server key. Keep that key private. Verify the Central owner’s Discord account and the players’ Minecraft and Discord identities through connected accounts. Do not put a Discord bot token in Minecraft or WEB.
Invite the hosted bot
Open the server’s Discord settings on Central and choose Invite the Raindrop bot. The installer must manage the Discord server. The current invitation requests zero permissions, so grant the feature permissions below explicitly. Only Central operates the shared bot; you do not create a separate bot application.
Bind and test a route
Choose the Discord guild, primary Minecraft server and channel in WEB or /rdd admin. Start with one CHAT route and optional features disabled. Review connection checks, save, then enable the bridge. Send distinct test messages in both directions. Confirm the intended channel receives each message once before enabling more features.
Who can change what
Central checks Minecraft server ownership and the owner’s current Discord Manage Server permission before enabling a binding. Multiple Minecraft servers may share a guild only under the same Central owner. Each Minecraft server has one binding; changing an existing binding to another guild is refused. Disable it and contact Central support for supported cleanup/rebinding rather than editing database rows.