Wiki Release: 2026.09.5 · UltimateClans: 9.1.4 · Documentation branch: 9 · Discord
Discord Module configuration#
The Discord Module has a small public configuration because connection identity/endpoints are handled by the integration implementation rather than by asking server owners to paste a bot token or raw Discord webhook into config.yml.
Config.Discord.message_format#
Controls how messages received from the linked Discord CHAT channel appear to members in Minecraft.
Default behavior includes a Discord prefix, sender name, message body and hover information. The supported replacement fields are:
| Field | Meaning |
|---|---|
{player} | Discord sender name supplied by the bridge |
{message} | Discord plain-text message |
{role} | Role field supplied by the bridge |
{server} | Server field supplied by the bridge |
{uuid} | Discord sender user ID |
Example simplified format:
<green>[Discord] <dark_purple>{player}<gray>: <white>{message}
Keep the placeholders exactly as shown. They are replaced by the module after a Discord message reaches the authenticated clan socket.
Config.Permissions.edit#
This section controls the UltimateClans internal role permission for managing the Discord integration.
Defaults:
name: Discord-Edit
default_value: true
applicable_roles:
- moderator
- admin
At module initialization, the permission is applied to the matching default UltimateClans roles. Changing the Bukkit permission does not replace this clan-role check.
Config.Icon#
Controls the Discord Module shortcut inserted into the UltimateClans GUI.
Important fields include:
material/texture— visual item;glow— enchanted glow effect;slot— default15;page— defaultclan_settings;mimeslots— optional fill/slot behavior;modeland NBT data — custom item model/data support;left_click_action/right_click_action— default to opening the clan Discord command;click_sound— optional GUI sound.
The GUI icon is only an entry point. The normal command and internal role permission checks still apply.
commands.yml#
Player command#
The module registers the discord subcommand into UltimateClans.
Relevant settings:
Commands.player.permission:uclans.player.discord;Commands.player.alias:discord;cooldownandvalue: command framework controls;disabled_worlds/disabled_regions: optional command restrictions;Commands.discord.registerandCommands.discord.unregister: aliases/help entries for the clan operations.
Client administration command#
The standalone command root is configured as discord_register with Bukkit permission:
uclans.discord_register.admin
Its functional client-association syntax is:
/discord_register client <discord_id>
Language files#
language/Lang_EN.yml and language/Lang_ES.yml contain the user-facing setup, connection, error, link, unlink and cooldown messages.
They include separate messages for conditions such as:
- client not registered;
- connection refused;
- connection/IP limits;
- temporary IP block;
- missing authentication information;
- client deregistration;
- plan/clan access suspension;
- CHAT or NOTIFICATION link/unlink success;
- message cooldown.
Keep message placeholders such as %UUID% and {seconds} intact when translating.
What you do not configure here#
The normal administrator setup does not require placing the Discord bot token, its database credentials or a raw Discord webhook URL in the UltimateClans module configuration. Those belong to the managed companion integration and are not part of the public Minecraft configuration workflow.