Can I keep killfeed separate from player join and leave events?

Yes. Helios supports separate routing so killfeed and player activity do not compete in one channel.

Do I need WebRCON connected for reliable feed data?

Yes. Stable WebRCON is required for dependable live command and feed behavior.

Should I publish every event type to public channels?

Not always. Keep sensitive or high-noise signals in staff channels and publish only player-safe events publicly.

Home / Rust Console killfeed bot setup for Discord and in-game visibility

Rust Console Feature Page

Rust Console killfeed bot setup for Discord and in-game visibility

Helios helps owners keep kill events, join/leave signals, and staff activity readable across Discord and in-game feed channels.

Start Setup Open Docs

Start with one feed map for staff and one for players, then expand once event volume is stable.

Quick take

A Rust Console killfeed setup works best when you split player-facing and staff-facing output early, then validate feed noise, moderation value, and uptime before adding more event types.

At a glance

This page answers how to structure Rust Console killfeed outputs so they stay readable under load.
It covers channel architecture, role-aware routing, and testing before full rollout.
Use the linked docs to configure Discord feed and in-game feed controls in order.

What this feature solves

Removes mixed-channel noise by splitting public and staff feed streams.
Gives moderators consistent event context for support and cheating review.
Keeps incident visibility high during raids, wipes, and peak hours.

Who this is for

Owners who need clean event telemetry without manual message copying.
Moderators and admins handling disputes, reports, and active incidents.
Community servers wanting transparent activity visibility for players.

Example feed output formats

[Killfeed] KillerName eliminated TargetName with LR-300 at Grid F6.
[Player Feed] PlayerName connected from PlayStation and joined Team Alpha.
[Staff Alert] Rapid PvP spike detected near Outpost, review raid channel.

Recommended rollout sequence

Set Discord killfeed channel and verify message readability first.
Enable player activity feed in a separate channel to avoid collision with kill logs.
Configure in-game feed templates only after Discord routing passes smoke tests.

Common server-owner scenarios

Small community server

Use one public killfeed channel and keep player join/leave updates moderate.

High-activity wipe server

Split killfeed, player activity, and staff alerts to protect readability under load.

Moderation-heavy server

Prioritize staff timeline fidelity so reports can be investigated quickly.

Creator-friendly server

Use cleaner public feeds and keep sensitive signals in internal moderation channels.

Validation and troubleshooting checkpoints

Check channel permissions whenever feeds go silent after role updates.
Test feed output after wipe changes and after any host connection maintenance.
Keep one staff-only channel for noisy or sensitive incident events.

Related setup docs and cluster pages

Share-ready talking points

Quick summary to share

Share this summary when teammates or community admins ask the same setup question.

Lead with the direct recommendation, then add one practical reason.
Include one setup or troubleshooting link so the reader can act immediately.
Keep wording tied to real setup steps and visible checks.

Useful next links

Use these follow-up links based on what the team needs next.

Setup path: Start Here and WebRCON Connection.
Troubleshooting path: Troubleshooting Playbooks.
Comparison path: Comparison Hub.

Evidence kit (ready for real assets)

Screenshot

Channel map examples

Add public-versus-staff feed routing captures with labels for each event stream.

Output

Feed message samples

Add before/after readability samples from the same event window.

Scenario

Moderation timeline

Add incident timeline examples where feed data accelerated moderator response.

Attribution

Review and support notes

Add attributed owner/staff feedback with server type and date context.

Frequently asked questions

Can I keep killfeed separate from player join and leave events?: Yes. Helios supports separate routing so killfeed and player activity do not compete in one channel.
Do I need WebRCON connected for reliable feed data?: Yes. Stable WebRCON is required for dependable live command and feed behavior.
Should I publish every event type to public channels?: Not always. Keep sensitive or high-noise signals in staff channels and publish only player-safe events publicly.

Need a Rust Console killfeed setup that stays readable during peak activity?

Build the channel map first, test with live events, and only then scale feed coverage to all event types.

Launch Setup Compare Options