Helios Rust Console Bot Documentation
How Do I Add a Killfeed to a Rust Console Server?
Add a killfeed to a Rust Console server, from the WebRCON connection it depends on through channel routing and permissions, plus why a killfeed that is configured correctly can still stay silent.
- Last updated
- Related
- /killfeed
- Maintained by
- Helios RCE
Short Answer
A killfeed on a Rust Console server needs three things, and it fails if any one is missing:
- A working WebRCON connection — the killfeed is built from server events, so no connection means no events, regardless of how the killfeed itself is configured.
- A Discord channel to post into, mapped in your killfeed settings.
- Permission for the bot to post in that channel — the most commonly missed step, because nothing visibly errors when it is wrong.
If your killfeed is silent, test them in that order. Most "the killfeed is broken" reports are actually one of the first or third.
Prerequisites
- A connected server. Verify with
/cmd send command:"fps"before anything else. Manage Serverpermission in Discord.- A channel decided in advance for kill events.
Setup
- Confirm the connection works —
/cmd send command:"fps"must return a value. - Create or choose the Discord channel for kill events.
- Confirm the bot can view and send messages in that channel.
- Map the killfeed to that channel in your killfeed settings.
- Trigger a real kill on the server and confirm it appears.
Step 5 is not optional. Configuration that looks correct and a killfeed that actually posts are different claims, and only one of them matters.
Plan Your Channels Before You Start
The most common structural mistake is routing everything into one channel. Kill events are high-volume; anything sharing a channel with them becomes invisible.
| Channel | Carries | Why separate |
|---|---|---|
#killfeed | Kill events | High volume, players want it |
#player-activity | Joins and leaves | Different audience, different cadence |
#admin-feed | Admin actions | Staff only; must not be buried |
#raid-alerts | Raid events | Time-critical; must not be missed |
WARNNever route admin or raid alerts into the killfeed channel
Both are time-critical and low-volume. In a busy killfeed channel they scroll past unread, which defeats the purpose of having them. Staff will assume they are broken long before they realise they are simply buried.
Why a Configured Killfeed Stays Silent
Work through these in order — they are listed by how often they are the actual cause:
| Check | How to test | Fix |
|---|---|---|
| Connection is down | /cmd send command:"fps" | Fix WebRCON first |
| Bot cannot post in the channel | Have the bot post anything there | Grant view + send message permissions |
| Channel was renamed or deleted | Compare the mapped channel to what exists | Re-map the killfeed |
| Wrong server selected | /server list | Map the killfeed to the correct server |
| No kills have happened | Trigger one yourself | Not a fault |
After a Wipe
The killfeed itself is not map-specific, so it usually survives a wipe. What breaks is the connection underneath it, because many hosts rotate the RCON password on wipe or reinstall. If your killfeed goes quiet immediately after a wipe, check the connection before the killfeed settings. See the Wipe Day Checklist.
In-Game Killfeed
A Discord killfeed and an in-game killfeed are separate outputs and are configured separately. Turning one on does not turn the other on. See In-Game Killfeed.