CoreChatX 2026.1.4

Fixed

• Discord -> Minecraft messages no longer force a hardcoded [Discord] sender prefix.
• Discord -> Minecraft messages can now be fully formatted from discord.inbound.format.
• Discord bridge formats can now be overridden per channel from channels.yml.
• Telegram bridge formats can now be overridden per channel from channels.yml.
• Discord -> Minecraft messages now expose {rank_prefix} as the sender's highest Discord role name.
• Added {role_color} for Discord -> Minecraft messages. It resolves to the highest colored Discord role and can be used as a MiniMessage color tag.
• Added {channel_prefix} for Discord -> Minecraft messages so custom channel tags can be kept in discord.inbound.format.
• PlaceholderAPI placeholders are now processed in discord.format for Minecraft -> Discord messages.
• Minecraft -> Discord discord.format now supports {rank_prefix}.
• Minecraft formatting codes from LuckPerms or PlaceholderAPI prefixes are stripped before messages are sent to Discord or Telegram, while the actual message text is preserved.
• Telegram outbound formats also support {rank_prefix} if the token is used.
• Inbound bridge logging now handles unexpected/unknown source ids without throwing.

Configuration

Discord -> Minecraft messages are now controlled by one format key:

discord:
  inbound:
    format: "{channel_prefix}[Discord] {role_color}{rank_prefix}</role_color>{sender_name}: {plain_text}"

Per-channel bridge formats can be set in channels.yml:

channels:
  mod:
    discord:
      outbound-format: "[MOD] {rank_prefix}{sender_name}: {plain_text}"
      inbound-format: "{channel_prefix}[Discord] {role_color}{rank_prefix}</role_color>{sender_name}: {plain_text}"
    telegram:
      outbound-format: "[MOD] {rank_prefix}{sender_name}: {plain_text}"
      inbound-format: "{channel_prefix}[Telegram] {sender_name}: {plain_text}"

If a per-channel format is blank, CoreChatX falls back to the matching global bridge format.

Available inbound tokens:

• {source}: display source name, for example Discord or Telegram
• {source_type}: raw source id, for example discord
• {channel_id}: CoreChatX channel id
• {channel_prefix}: prefix extracted from the channel format, or the configured channel prefix fallback
• {sender_name}: bridge sender display name
• {rank_prefix}: Discord sender's highest role name, blank for Telegram
• {role_color}: MiniMessage color tag from the highest colored Discord role, or white
• {plain_text} / {message}: sanitized message content

Example with role-colored prefix and message:

discord:
  inbound:
    format: "{channel_prefix}<dark_gray>[Discord]</dark_gray> {role_color}{rank_prefix}</role_color> <white>{sender_name}</white>: {role_color}{plain_text}</role_color>"

Minecraft -> Discord formats can now use PlaceholderAPI placeholders and {rank_prefix}:

discord:
  format: "[{source_server}] [{channel_id}] {rank_prefix}{sender_name}: {plain_text}"

Safety

• Bridge formats are now validated on config load.
• Unknown placeholders and invalid inbound MiniMessage syntax produce warnings instead of failing startup.
• The outbound formatter strips formatting from templates and rank prefixes, but preserves literal ampersands in the real chat message.