Helios Rust Console Bot Documentation
Admin Feed
Send tracked staff actions to a private Discord channel.
- Last reviewed
- Maintained by
- Helios RCE
Use an Admin Feed to review supported item and kit grants involving tracked in-game Moderators, Admins, and Owners. Keep its destination private to staff. Setup requires Manage Server; Admin Feed requires Premium.
The feed can identify grants made through Helios and supported in-game Admin or Kit Manager give logs. It depends on Helios knowing the recipient's in-game auth level. A grant to a normal player is not a useful test of this feed. Keep staff notes for context such as the reason for a grant; this feed does not record every Discord moderation action or dashboard edit.
From the dashboard
- Open the intended Rust server in the dashboard.
- Choose Discord → Feeds, expand Feeds, then expand Admin Feed.
- In New Destination, choose a private staff channel. Leave Start sending immediately checked to enable it.
- Confirm Scope → This Rust server only, then click Add Destination.
- Check the saved row above the new-destination form. Confirm its channel, scope, and Send this destination checkbox.
New Admin Feed destinations use the selected Rust server. Older destinations may show All connected servers, as the saved row does in this screenshot. Opening one Rust server's dashboard does not narrow an existing shared destination's scope. Read the row before editing or removing it.
To edit an existing destination, change its channel, scope, or enabled checkbox and click that row's Save. Add Destination creates a new row; it does not save edits to an existing one. Uncheck Send this destination and save to pause a destination. Remove deletes that destination.
The screenshot shows existing testing settings. Use your own staff channel rather than copying the example destination.
From Discord
/adminfeed add server:<choose your server> channel:#staff-log
/adminfeed list
To remove a destination, run /adminfeed remove and choose the feed from autocomplete.
Check delivery
Helios needs View Channel, Send Messages, and Embed Links in the destination. Check channel-specific permission overrides as well as the bot's role permissions.
A saved destination confirms routing, not that an event has occurred. After the next supported grant to a tracked staff player, check the destination and the server label on the message. If it is missing, confirm the Rust connection is active, Premium is active, the row is enabled, the scope includes that server, and the recipient's in-game auth level is known to Helios. An ordinary player join or a Discord role edit does not test Admin Feed delivery.
See the Discord Hub for other feeds and channel tools.
