CoreChatX 2026.1.5

Fixed

• Discord -> Minecraft player mentions are now controlled by the target channel's allow-mentions.from-discord setting.
• Discord custom pings such as @staff now require at least one matching Discord role ID configured in pings.yml.
• Custom pings with missing or empty discord-roles now stay as plain text when used from Discord and do not notify Minecraft players.
• Minecraft custom pings still use use-permission; existing receive-permission checks still apply to Minecraft recipients.
• Telegram inbound mentions are now controlled by allow-mentions.from-telegram.
• Network chat from other Minecraft servers remains treated as Minecraft-originated and uses allow-mentions.from-minecraft.

Configuration

channels.yml now uses source-specific mention gates:

allow-mentions:
  from-minecraft: true
  from-discord: true
  from-telegram: true

pings.yml custom pings now support Discord role allow-lists:

custom-pings:
  staff:
    trigger: "@staff"
    use-permission: "corechatx.ping.use.staff"
    receive-permission: "corechatx.staff"
    discord-roles:
      - "123456789012345678"
    bypass-toggle: true
    token-format: "<#ff8f8f>{trigger}</#ff8f8f>"

Empty discord-roles: [] means the ping cannot be activated from Discord.

Migration

• Existing scalar values like allow-mentions: true or allow-mentions: false are replaced at startup with the new nested default section.
• Existing nested source values are preserved, and missing nested keys are added automatically.