Helios Rust Console Bot Documentation

How to Set Up a Rust Console Killfeed Bot

Practical walkthrough for setting up Rust Console killfeed routing in Helios with channel architecture, validation, and troubleshooting checkpoints.

Page Summary

  • This guide shows how to set up a Rust Console killfeed bot in Helios.
  • It is for owners and moderators who need readable live event visibility.
  • Use this flow before expanding to advanced event routing.

Who This Is For

  • Owners launching their first killfeed setup.
  • Admins rebuilding feed channels after wipe.
  • Moderators who rely on feed data for incident handling.

What This Covers

  • Recommended channel structure for readable feed output.
  • Killfeed setup steps from server connection validation (WebRCON) to live routing.
  • Validation and troubleshooting checkpoints for stable output.

What You Need Before Starting

Recommended Channel Structure

  1. #killfeed-public for player-safe kill updates.
  2. #player-activity for joins, leaves, and flow signals.
  3. #staff-alerts for high-noise or sensitive signals.

Setup Walkthrough

  1. Confirm server health with /server list and /cmd send command:"fps".
  2. Configure killfeed channel mapping in Killfeed Overview.
  3. Configure Discord routing with Killfeed in Discord.
  4. Add in-game formatting only after Discord routing is stable in In-Game Killfeed.
  5. Run a live activity check with moderators present.

Validation Checklist

  • Kill events appear in the intended channel.
  • Join/leave events do not flood kill-only channels.
  • Staff-only alerts stay out of public channels.
  • Feed messages are readable during peak activity.

Common Troubleshooting Checkpoints

  • No feed output: verify channel permissions and server connection status (WebRCON).
  • Messages in wrong channel: re-check feed mapping and channel IDs.
  • Too much noise: split event types into separate channels.

Related Guides

Related Feature Pages

Next Steps

  1. Keep one feed channel map for public, player activity, and staff alerts.
  2. Validate feed routing under peak activity before announcing changes.
  3. Save a post-wipe feed checklist in your moderation runbook.