Helios Rust Console Bot Documentation

Rust Console Admin Alerts Setup Guide

Route raid notifications and high-priority Rust Console events to a staff channel, so admins see incidents while they happen instead of hearing about them later.

Last reviewed
Applies to
Helios 2026.8
Related
/set raid-channel
Maintained by
Helios RCE

Discord killfeed channel list

Overview

Admin alerts are the high-signal notifications your staff act on: raids in progress, and the live events worth escalating. The point is one channel a moderator can actually watch, rather than incidents buried in a busy killfeed.

Requirements

  • Connected server with healthy server connection (WebRCON)
  • A staff-only alert channel
  • Manage Server permission
  • Raid alerts set up when using raid notifications

Setup

  1. Create one dedicated alert channel (for example, #helios-alerts).
  2. Route raid notifications to it with /set raid-channel.
  3. Have players claim their raid codes with /raid link — see Raid Alerts for the full player-side flow.
  4. Validate one controlled test alert.
  5. Document the escalation owner for each staff shift.

WARNRaid pings mention players

The raid channel is where Helios pings the player who was raided. If you want a channel only staff can read, be aware the raided player cannot see their own alert there — most servers use a public #raid-alerts channel for raid pings and keep a separate staff channel for everything else.

Commands or Controls

/set raid-channel channel:#helios-alerts   # where raid pings land
/raid link server:"<SERVER>"               # players claim their code
/events                                    # server event controls
/automation-events                         # scheduled event controls

Example Use Case

Owner routes all raid notifications to #raid-alerts, then assigns one admin per shift to monitor and action incoming pings. Anything that needs a decision gets escalated in the staff channel, with the raid ping linked as the record.

Common Issues

Problem

No alerts appear even though setup commands ran successfully.

Likely Cause

Alert channel permissions or server mapping are incorrect.

Fix

Re-run /set raid-channel, confirm Helios can post in the channel, and validate with a fresh test event. If only one player is affected, the problem is almost always their broadcaster rather than your routing — see the raid alerts troubleshooting table.

Tips / Best Practices

  • Keep the staff channel staff-only to preserve signal quality.
  • Re-validate alert routing after wipe, host migration, or server rename.
  • Expect up to 60 seconds of delay on raid alerts; the broadcaster poll runs on a one-minute cycle.
  • Link this page in your internal incident runbook.

Related Guides