DyDiscord

DyDiscord — Minecraft and Discord Made Simple

Link your accounts. Share your chat. Connect your community.

DyDiscord is a Minecraft–Discord integration plugin for survival, SMP and community servers. Connect player accounts, bring conversations together and follow your server through your own Discord bot.

DyDiscord combines private account linking, two-way chat, Minecraft-to-Discord roles, configurable rewards, giveaways and staff tools in one plugin. Version 1.4.0 adds support tickets answered from Discord, a staff /whois, server health alerts, Discord-to-Minecraft groups and image links in chat, and is lighter on busy servers, while preserving existing account links, custom settings and translations.

New in 1.4.0

Support tickets. /ticket <message> opens a thread in your tickets channel. Staff reply in the thread and the player reads it in game, even after rejoining. /ticket close closes it.

Staff lookups. The Discord command /whois <player> privately shows a player's linked account and when they were last seen. Only members with Manage Server, or the roles you choose, can use it.

Health alerts. Low TPS, high memory use and player-count milestones are posted to a staff channel, with a cooldown per kind.

Discord roles to LuckPerms groups. Linked players get a LuckPerms group while they hold a Discord role. Groups given by hand are never removed, and staff groups need your explicit permission.

Images in chat. Discord images, files and stickers appear in Minecraft as clickable [image] links.

Lighter and faster. Fewer Discord events, faster chat relay and message rendering, quicker reloads and quieter background work.

Every new option starts off.

Added in 1.3.0

Player names and heads. With chat.webhook.enabled, Minecraft chat is posted through a channel webhook under the player's name and rank, with their head as the picture. The bot needs Manage Webhooks; without it chat is sent as the bot as before.

Advancements and first joins. chat.events.advancement announces the advancements Minecraft announces in chat, and chat.events.first-join welcomes new players. Both start off.

Added in 1.2.0

Cheat checks. /cheatcheck <player> puts a title on the player's screen, a warning in chat and a sound, repeated until the check ends. A linked player gets a Discord message, by DM or in a channel, asking them to join your voice channel. The player stays in place and can only use the commands you allow. Leaving during a check can run console commands such as a ban. Staff see every step in game and in a Discord log.

Player reports. /report <player> <reason> tells online staff and posts the report, with the reported player's location, to a Discord channel. An optional role is mentioned.

Required linking. With linking.require-to-join, players without a linked account cannot join; the kick screen shows their linking code and your invitation. Operators can be let through.

Nickname and ban sync. Linked members can carry their Minecraft name as their Discord nickname. Bans can follow from Minecraft to Discord, from Discord to Minecraft, or both.

Folia. The same JAR runs on Bukkit, Spigot, Paper, Purpur and Folia.

DyHomes logs. Warps created, moved and deleted, homes made public and, if you want them, every DyHomes teleport.

Version 1.1.0 added the status card, DyClaim and DyRTP logs, PlaceholderAPI, German, Spanish and Russian, MiniMessage and the developer API.

Choose your server build

Install one JAR per server. Both packages provide the same features for Bukkit, Spigot, Paper, Purpur and Folia, with Minecraft 1.20.x–26.x as the current compatibility range. Stop the server and back up the full DyDiscord folder before replacing the JAR. Existing accounts do not need to be linked again.

Java 17 bytecode; use the runtime required by your server. Proxy platforms are outside the current support claim. Optional integrations must support your selected server too. Compatibility notes · Upgrade guide · Downloads

Why DyDiscord?

Your bot, your community. Use your own Discord application and keep account linking, chat and console output in separate channels. The bot runs inside Minecraft; no separate bot process or external database is required.

Private account management. Players link through a private Discord form and view their account details privately. Unlinking requires confirmation. The account panel and private slash commands share the same account system.

Choose what you use. Enable either chat direction, event messages, role synchronization, rewards or console access as needed. You can turn off the panel and keep command-based account access.

Five languages. English, Turkish, German, Spanish and Russian messages are included, and commands use English words. Help and TAB follow the effective language and permissions. Explicit game/player language choices are respected; otherwise game messages follow the client or bot language.

Link accounts, your way

Players run /dydiscord link, then enter their temporary, single-use code through Discord /link or the account panel. The panel keeps Link Account → Unlink → My Account in one card, using your server icon or a custom image.

Each Minecraft account links to one Discord account. Linking never grants Minecraft permissions or OP. Account records remain in local SQLite storage across restarts and supported upgrades.

Share the conversation

Forward public Minecraft chat to Discord, Discord chat to Minecraft, or both. Message formats and optional join, leave and death embeds are configurable; player messages are not translated.

Minecraft ranks can come from LuckPerms, with Vault Chat as a display fallback. Discord messages use the member's server display name and highest eligible role, including its primary color. Players can use /dydiscord chat on|off to show or hide incoming Discord chat for themselves.

Forwarded messages do not create Discord mention notifications. Bot/webhook messages, edits and attachments are not relayed. Unknown Minecraft chat listeners pause outbound forwarding to protect private or moderated conversations; those systems need a supported integration.

Keep Discord roles in step

Give linked members configured Discord roles without requiring LuckPerms. With LuckPerms, map real direct, inherited and temporary Minecraft group memberships to Discord role IDs. Temporary ranks are checked while players are offline, and unlinking or changed rules retain the information needed to clean up old managed roles.

Synchronization runs Minecraft → Discord only. Only configured roles are managed; unrelated roles stay untouched. The bot needs Manage Roles and sufficient role hierarchy. Privileged, integration-managed and console-access roles are blocked from automatic distribution.

Reward participation

Optional first-link and boost rewards run your installed providers' console commands. Use your existing rank, economy or website system to provide temporary ranks, currency, items or site credit. DyDiscord does not bundle those providers, and command dispatch does not prove an external reward was delivered.

Create persistent button giveaways with optional linked-account or role requirements. DyDiscord records entries and draws winners; the owner delivers the prizes. Discord server information, player lists, configured addresses and useful links help members find what they need.

Follow your server from Discord

Relay actual server output to a separate console channel. Optionally authorize trusted Discord roles to run Minecraft console commands. Log forwarding and command execution have separate switches. Public console channels are allowed, so anyone with channel access can read the output.

The relay shows real server output without extra technical acceptance/rejection replies. Normal shutdown attempts a short yellow notification before disconnecting; bot restarts and reloads do not send it. Delivery cannot be guaranteed during crashes or network failures.

A separate status card keeps one message up to date with the server state, and an optional log channel follows DyClaim, DyRTP and DyHomes activity.

Familiar commands

The long /dydiscord admin path remains available.

Get started

1. Install one of the packages and start your server to generate the files.
2. Create your own Discord bot, invite it and configure token and guild-id in plugins/DyDiscord/bot.yml.
3. Reload valid settings, choose the channels you need and run /dyda doctor.
4. Enable the required Discord intents for the features you use. Message commands, console input and incoming Discord chat need Message Content Intent; member-event features need Server Members Intent.

Settings and messages include short English comments. Anonymous bStats statistics can be turned off with metrics.enabled: false. Back up the complete data folder before upgrades; restoring local data does not undo Discord role changes or reward commands already executed.

Source and support

Documentation · Report an issue · Discord support · License

By Claww / DyPlugin.