Helios Rust Console Bot Documentation

Rust Console Raid Alerts Setup (RaidLink)

Owner setup guide for Rust Console RaidLink codes and raid notification routing with Helios.

Page Summary

  • This page covers raid alert setup with RaidLink in Helios.
  • It is for owners and admins routing raid notifications to Discord staff channels.
  • Use this with the admin alerts guide for full incident workflow coverage.

Overview

Raid Alerts use RaidLink. Players generate a 4-digit broadcaster code and Helios pings Discord when matching broadcaster frequencies are detected.

Related Product Pages

Who This Is For

  • Owners defining raid alert policy
  • Admins configuring raid alert channels

Requirements

  • Connected server in Helios
  • Manage Server permission for channel setup
  • One dedicated raid alert channel
  • Players configured with /raid link

Setup

  1. Set raid channel with /set raid-channel.
  2. Have players run /raid link server:"<SERVER>".
  3. Players set the returned 4-digit code as in-game broadcaster frequency.
  4. Confirm a test alert reaches the configured channel.
  5. Tell players to refresh code from the RaidLink button when needed.

Commands or Controls

/raid link server:"<SERVER>"
/set raid-channel channel:#raid-alerts

Example Use Case

Owner sets #raid-alerts as the guild alert channel and asks each active team to generate their own RaidLink code for the current wipe server.

Common Issues

Problem

No raid alerts are posted.

Likely Cause

Raid channel not configured or player code linked to wrong server.

Fix

Re-run /set raid-channel, then regenerate player code with /raid link.

Prevention

Validate one test raid alert after every server nickname or mapping change.

Tips / Best Practices

  • Raid checks run on a recurring poll cycle (about every 60 seconds).
  • Keep one raid channel per guild to avoid fragmented alerts.
  • Add a short player guide explaining when to refresh RaidLink code.