Helios Rust Console Bot Documentation

Rust Console Killfeed in Discord

Route Rust Console kills to Discord channels from the Helios dashboard or with /dcfeed.

Last updated
Maintained by
Helios RCE

This page is for Discord channel routing — sending kills to a text channel in your Discord. For the messages players see in Rust chat, see In-game killfeed templates.

The fastest way to set this up is the Killfeed module in the Helios dashboard. Everything here can still be done with /dcfeed in Discord, covered at the bottom of this page.

Open the Discord channels tab

  1. Go to the Helios dashboard and sign in with Discord.
  2. Find your server under Connected game servers and click Manage Server.
  3. In the Modules sidebar, choose Killfeed, then select the Discord Channels tab.

The Discord Channels tab showing a configured killfeed channel with its scope and status

Every destination is listed with the channel it posts to, its Scope, and its Status. Scope is what to check first when a channel is quiet or noisy: All connected servers means that one channel receives kills from every server you have connected, while This game server keeps it to one.

Add a channel

Click Add Channel in the module header.

The Add Discord Killfeed Channel dialog with the channel picker and the receive-kills-from scope

  • Discord text channel — only text and announcement channels Helios can actually access are listed. If the channel you want is missing, Helios cannot see it, which is a permissions problem rather than a Helios one.
  • Receive kills from — this game server, or every connected game server.

Click Add Channel. The destination appears in the list and the channel count in the header goes up.

INFONote

The channel picker only showing accessible channels is useful diagnostically. If a channel is absent from the dropdown, fix Helios's access to it before doing anything else — adding it another way will still produce a silent channel.

Related feeds

Killfeed is one of several Discord feeds. The others are still set up with their own commands:

/dcplayerfeed add|remove|list
/adminfeed add|remove|list
/set online-channel
  • /dcplayerfeed routes player join and leave events.
  • /adminfeed routes staff actions and is premium.
  • /set online-channel maintains a live player-count channel.

Tips

  • Keep the public killfeed separate from staff-only feeds. Mixing them makes moderation history hard to read later.
  • Use dedicated channels rather than posting into general chat — a busy server will bury conversation.
  • If you run several game servers, decide deliberately between one shared channel and one channel per server. Scope is set per destination, so you can mix both.
  • Audit destinations after any Discord restructure, since a deleted or renamed channel silently stops receiving.

Common issues

The channel is added but stays silent

Helios's role is missing send or embed permission on that channel. Grant channel-level permissions, then run one test kill.

The channel I want is not in the dropdown

Helios cannot see it. Only text and announcement channels it has access to are listed — fix access first.

One channel is getting kills from the wrong server

Its scope is set to All connected servers. Expand the destination and change it to This game server.

PvE deaths are missing

Include PvE kills is off. It lives on the In-game Feed tab but applies to both feeds.

Doing the same thing in Discord

/dcfeed add|remove|list

Requirements are the same either way: a connected server, Manage Server permission in Discord, and Helios able to post in the target channel.

TIPTip

The dashboard and /dcfeed read and write the same destinations. Add a channel in Discord and change its scope on the dashboard, or the other way around.