Skip to main content

Move one DiscordSRV chat route to a replacement channel

Applies to: DiscordSRV; match the linked maintainer documentation to your installed platform and release.
Documentation checked .

Renaming a Discord channel does not create a new channel ID, but deleting and recreating one does. When moving a bridge, record the intended destination and test both directions before announcing the change.

Prepare the test

Use a private test channel and two test identities before changing the public bridge. Keep bot tokens, linking codes and staff console output out of screenshots and public support messages.

Make the change

  1. Create a private replacement text channel and grant the bot only the channel permissions required for your bridge. Confirm ordinary members can read or send there according to the communication policy you intend.
  2. Use Discord developer mode to copy the replacement channel’s ID. Preserve the existing Channels mapping from DiscordSRV config.yml, including its Minecraft-side channel key, so you change only the destination of one route.
  3. Update that one mapping using the installed configuration format. Apply it with the documented supported method and watch the console for a rejected channel, missing access warning or configuration parsing error.
  4. Send a unique harmless test message from Minecraft and a different one from Discord. Confirm each appears once in the intended destination and neither arrives in the previous public channel.

Check the result

The new channel should carry both directions with the correct author context and no duplicate bridge posts. Check a second normal player because administrator channel access can conceal permission problems affecting ordinary members.

If the test fails

Restore the recorded channel mapping if delivery fails, keeping the new channel private while investigating. Do not delete message history or regenerate the bot token to repair a wrong destination ID.

If multiple Minecraft chat channels are configured, test only the chosen route first. A global replacement can accidentally send staff chat and public chat to the same Discord destination.

References and related help

Check the official DiscordSRV documentation against your installed release before using a command or setting from another version.

No comments to display