Rust Console Raid Alerts: RaidLink Setup

Raid alerts tell a player their base is being hit while it is happening, even if they are not in game. An owner sets one Discord channel with /set raid-channel, each player claims a personal 4-digit code with /raid link, and wires an RF Broadcaster into their base on that frequency. When the broadcaster goes live, Helios posts a RAID DETECTED ping in the raid channel and — if the player turned it on — sends them a direct message.

Setup takes about five minutes for the owner. Players do their own part in game.

Part	Who does it	Control
Choose the Discord channel raid pings land in	Owner / admin	/set raid-channel
Claim a personal broadcaster code	Each player	/raid link
Turn personal DM alerts on or off	Each player	DM Alerts button
Rotate a code that leaked	Each player	Refresh Code button

---

Prerequisites

• A Rust Console server already connected to Helios over WebRCON. If that is not done yet, start at Connect Your Server.
• The Manage Server permission in Discord to run /set raid-channel.
• A Discord channel Helios can post in. A public #raid-alerts channel works fine — the ping mentions the player who was raided.
• Players need enough electrical parts in game to power an RF Broadcaster from a trigger.

Raid alerts are on the free tier. There is no premium requirement.

---

Step 1 — Set the raid alert channel (owner)

Run this once per Discord server:

/set raid-channel channel:#raid-alerts

Helios confirms with "RaidLink alerts will now be sent to #raid-alerts."

The raid channel is set per Discord server, not per Rust server. If you run several Rust servers in one Discord, every raid ping lands in the same channel and names which server it came from.

---

Step 2 — Claim a RaidLink code (each player)

Any member can run this — no admin permission needed:

/raid link server:"US Main"

The server option autocompletes from the servers connected to your Discord, so players pick the one their base is on. Helios replies privately with:

• Code — a 4-digit number, for example 4821. This is the broadcaster frequency.
• Server — the server the code is bound to.
• DM Alerts — a button that toggles direct messages on or off.
• Refresh Code — a button that rotates the code to a new number.

Running /raid link again for the same server returns the same code rather than a new one, so a player can look theirs up any time without breaking the setup already in their base. Picking a different server issues a fresh code and replaces the old one — a player has one active RaidLink at a time, so moving servers means rewiring the broadcaster.

DM alerts are off by default. Press DM Alerts once to turn them on.

---

Step 3 — Wire the broadcaster in game (each player)

Inside the base:

1. Place an RF Broadcaster and set its frequency to the 4-digit code from Discord.
2. Power it through a trigger rather than leaving it permanently on — a HBHF sensor, a laser detector, or a pressure pad on the approach to the base are all common choices.
3. Test the trigger once and confirm the broadcaster receives power.

---

Step 4 — Validate before you rely on it

1. Have a player trigger their own broadcaster.
2. Wait up to 60 seconds — Helios polls broadcasters on a one-minute cycle, so an alert is not instant.
3. Confirm a RAID DETECTED message appears in the raid channel and mentions the right player and server.
4. If they enabled DM alerts, confirm the direct message arrived too.

Do this once after every wipe. Bases are rebuilt from scratch at wipe, so the broadcaster wiring is gone even though the Discord code is not.

---

How Helios Detects a Raid

Useful to know when you are debugging a missing alert:

1. Every 60 seconds Helios sends rf.listboardcaster to each connected server.
2. The server replies with a list of active broadcaster frequencies.
3. Helios reads every [NNNN MHz] entry out of that reply.
4. Any frequency matching a claimed RaidLink code triggers a ping to the raid channel, plus a DM if that player enabled them.

That means the alert is driven by the broadcaster being powered, not by damage to your base. It fires because your trigger fired.

---

Commands

/set raid-channel channel:#raid-alerts   # owner, once per Discord server
/raid link server:"US Main"              # any player, once per server

---

Troubleshooting

Problem	Likely cause	Fix
No alerts at all, for anyone	The raid channel was never set, or Helios cannot post in it	Re-run /set raid-channel and check the channel permissions allow Helios to send messages
One player gets nothing	Broadcaster frequency does not match their code, or it never receives power	Have them re-run /raid link to read their code, then re-check the frequency and the trigger wiring
Alerts fire constantly	The broadcaster has permanent power	Rewire it behind a trigger so it is only powered during an actual event
Alert arrives late	Normal — polling runs every 60 seconds	Nothing to fix; expect up to a minute of delay
Alert names the wrong server	The code was claimed against a different server	Re-run /raid link and pick the correct server — this issues a new code, so update the broadcaster to match
No DM, but the channel ping works	DM alerts are off, or Discord DMs from server members are blocked	Toggle DM Alerts on, and check Discord privacy settings
Nothing works after a wipe	The in-game broadcaster is gone with the old base	Rebuild the broadcaster on the same code — the Discord code survives the wipe

---

Frequently Asked Questions

Are raid alerts free? Yes. Both /set raid-channel and /raid link are on the free tier.

How fast is the alert? Up to 60 seconds. Helios polls each connected server once a minute, so an alert lands somewhere between immediately and a minute after the broadcaster fires.

Does every player need their own code? Yes. Each player claims their own code and the ping mentions whoever owns it. A player holds one active RaidLink at a time — running /raid link against a different server replaces their previous code.

Do I need a separate channel per Rust server? No. The raid channel is set once for the whole Discord, and each alert says which server it came from.

What if someone learns my code? Press Refresh Code in the /raid link reply. You get a new 4-digit code and the old one stops triggering — then update the broadcaster in your base to match.

Do codes expire? No. A RaidLink code stays claimed until the player refreshes it.

Can I get raid alerts without the electrical setup? No. RaidLink works by watching broadcaster frequencies, so the in-game broadcaster is required. For raid activity you can see as an admin without any player setup, use the killfeed and game feeds instead.

Is this the same as offline raid protection? No. Raid alerts tell you a raid is happening. Offline raid protection stops raids on offline players entirely. Plenty of servers run both.

---

Video Walkthrough

---

Related Guides

• Raid Alert Channel Setup — the /set raid-channel reference page.
• /raid link command reference
• Admin Alerts — routing raid and incident alerts to a staff-only channel.
• Killfeed & Alerts hub — kill notifications and live game feeds.
• Offline Raid Protection — protect bases while their owners are offline.

Next Steps

1. Set the raid channel with /set raid-channel.
2. Post the /raid link instructions where your players will see them.
3. Run one live test and confirm both the channel ping and the DM.
4. Add "rebuild the broadcaster" to your wipe-day announcement.