Skip to main content

Keep live Discord feeds out of a Rust plugin test server

The safest copy for testing a Discord message is a fresh private world with a test-only destination. A copied plugin setting can still point at your live announcement channel. Review the directions messages can travel before starting the test.

Start from an empty set of external links

List what would normally post announcements, relay chat, take commands or grant roles. Check the game plugin, the bot and any rule in your hosting or management tools. Leave those jobs disconnected when you first start the test instance.

Start from an empty set of external links
Live connectionWhat to use in the rehearsal
Outgoing announcement webhookCreate a webhook for a private test channel if you need to test the outgoing message. Keep its full URL private.
Bot or two-way chat linkUse an isolated bot and Discord server if the test needs one. Leave inbound commands and role sync off unless they are part of the exercise.
Live channel IDs, tokens and account links in exported settingsRecreate the minimum config without these values. Read the files you intend to use before starting the feature.

Check that one event reaches one destination

The example tests only an outgoing status announcement.

  1. Verify the test webhook's channel in Discord and enter it in the test plugin settings.
  2. Send a synthetic message with a recognizable label such as ‘Birch Test closing check’. Read the intended private channel and the usual live announcement channel.
  3. Confirm exactly one copy on the test channel and none on the live channel. Review the source of extra messages before enabling another integration.
  4. Remove the test connection when you finish. If you copied any reusable files back to shared storage, check those exports contain no webhook, token or private account link.

Sources

Analytics settings

Analytics are off.

Help improve RustSC with page counts and performance measurements. Privacy details