Helios Rust Console Bot Documentation
Rust Console Raid Alerts: RaidLink Setup
Set a shared raid-alert channel and help players connect their private code to an in-game RF Broadcaster.
- Last reviewed
- Related
- /raid link
- Maintained by
- Helios RCE
RaidLink alerts a player when Helios detects a powered RF Broadcaster on their private frequency. The admin chooses a Discord channel; each player sets up their own broadcaster in game.
A RaidLink alert is a signal from the broadcaster, not proof that a base took damage. It does not block a raid or protect the base.
Before you start
- Connect your Rust server to Helios using Getting Started.
- An admin needs Manage Server permission to choose the Discord destination.
- Helios needs permission to view that channel, send messages, and embed links.
- Players need an RF Broadcaster, power, and an appropriate trigger in game.
Both Discord commands below are available without Premium.
1. Choose the channel — admin
/set raid-channel channel:#raid-alerts
Choose the channel from Discord's suggestions and check Helios's confirmation.
This is one shared channel per Discord community, not a different channel for every Rust server. Alerts identify the Rust server they came from.
You can also use Overview → Shared setup and admin tools → RaidLink Alert Channel → Configure on the dashboard. Choose the channel and click Save Setting. See channel setup.
2. Get a private code — each player
/raid link server:"US Main"
Choose the Rust server your base is on. Helios privately shows your four-digit Code, Server, and DM Alerts status.
Keep the code private. Someone who knows it could power a broadcaster on that frequency and cause a misleading alert.
- Running the command again for the same server shows the same code.
- Choosing a different server replaces your setup with a new code.
- Refresh Code replaces the code for your current server.
- DM Alerts switches personal direct messages on or off. They start off.
You have one active RaidLink per Discord community. If you replace or refresh it, update the in-game broadcaster to the new frequency.
3. Wire your broadcaster — each player
- Place an RF Broadcaster in your base.
- Set its frequency to your private code.
- Connect power through your chosen trigger, such as a sensor or detector.
- Check that the broadcaster receives power when the trigger activates.
Do not leave it permanently powered: Helios can report it repeatedly while the signal stays active. Choose a trigger that suits what you actually want to detect. A visitor or teammate activating a sensor can cause an alert too.
4. Check your own setup
When you are in game and can safely test your own wiring:
- Activate your own trigger and confirm the broadcaster receives power.
- Give Helios time to check the active signal.
- Check the raid-alert channel for the correct player and Rust server.
- If you enabled DMs, check those separately.
- Turn the test signal off afterward.
Helios normally checks roughly once a minute. This is not a guaranteed 60-second delivery time: server connection, command queues, and Discord delivery can take longer. A short pulse can finish between checks and be missed.
After a map wipe, rebuild the electrical setup and check it again. The map wipe does not itself expire your Discord code, but it removes the old base and broadcaster.
Troubleshooting
| Problem | What to check |
|---|---|
| No channel alert | Check the shared destination and Helios's channel permissions. |
| One player receives nothing | Check the selected Rust server, current private code, frequency, trigger, and power. |
| Alerts keep repeating | The broadcaster may be constantly powered. Check the wiring and turn the signal off. |
| A short test produces nothing | The signal may have ended between checks. Check your own setup with a signal that remains active long enough to be observed. |
| Alert arrives late | Check the server connection; checks and delivery are not instant. |
| DMs do not arrive | Turn on DM Alerts and check Discord allows messages from Helios. |
| Setup stopped after changing servers or refreshing a code | Read the current code and update your broadcaster. |
| Setup stopped after a wipe | Rebuild and check the broadcaster and power. |
DM delivery is independent of the shared channel. A channel problem does not necessarily stop a player's enabled DMs.
Common questions
Can I get alerts without a broadcaster?
Not with RaidLink. It watches powered broadcaster frequencies, so players must complete the in-game setup.
Does the code expire each wipe?
A map wipe does not automatically expire it. Choosing another server or pressing Refresh Code replaces it.
Is this Offline Raid Protection?
No. RaidLink sends notifications. Offline Raid Protection applies protection rules to configured zones when its requirements are met. Neither a RaidLink alert nor installing a broadcaster guarantees your base is safe.
Does Event Feed use the same channel?
No. Event Feed Settings announce world events for a selected Rust server. RaidLink uses the separate, community-wide raid-alert destination.