Helios Rust Console Bot Documentation

Raid Alert Channel Setup

Choose the shared Discord channel for players' RaidLink alerts.

Last reviewed
Maintained by
Helios RCE

An admin chooses where RaidLink posts player alerts. Players separately get their own private code and wire a broadcaster in game.

Set the channel in Discord

You need Manage Server permission. Run:

/set raid-channel channel:#raid-alerts

Choose your real channel from Discord's suggestions. Helios confirms the destination after saving it. The command is available without Premium.

There is one raid-alert channel for the entire Discord community, shared by all its Helios-connected Rust servers. Each alert names the Rust server and mentions the player. Running this command again replaces the shared destination; it does not add another channel.

Dashboard alternative

Open the dashboard, choose Manage Server → Overview, then find RaidLink Alert Channel under Shared setup and admin tools.

  1. Click Configure.
  2. Choose the Discord channel.
  3. Click Save Setting.

Although you opened a particular Rust server's dashboard, this destination is community-wide. Dashboard access follows your server's dashboard requirements; the free Discord command is an alternative.

Do not confuse this with Discord → Feeds → Event Feed. That feed announces cargo, helicopters, airdrops, and Bradley for one selected Rust server. It does not route players' RaidLink alerts.

Let players finish their setup

Share the player setup guide. Each player must choose their Rust server with /raid link, read their private code, and wire an RF Broadcaster to match it.

A channel alone cannot detect a raid. RaidLink checks powered broadcasters, not actual base damage.

Channel and DM checks

  • Helios must be able to view the destination, send messages, and embed links.
  • Players can turn on personal DM Alerts in their private RaidLink reply.
  • DMs are separate from the shared channel. A missing or unusable channel does not automatically turn DMs off.
  • Changing the shared destination does not refresh players' codes.

For a controlled setup check and more troubleshooting, see Raid Alerts. Do not trigger someone else's base to test the feed.