Can I separate player joins/leaves from killfeed?

Yes. Helios supports separate routing for killfeed and player activity channels.

Do I need WebRCON for reliable feed data?

Yes. A healthy WebRCON connection is required for reliable live event ingestion.

Can this help moderation workflows?

Yes. Staff can use activity timelines to support incident response and player reports.

Home / Rust Console player activity feed in Discord

Rust Console Bot Use Case

Rust Console player activity feed in Discord

Helios helps owners and moderators monitor player flow and combat activity with cleaner feed routing.

Start Setup Open Docs

Use the linked setup docs to configure this workflow with owner-safe rollout and staff-ready support steps.

Quick take

For reliable moderation visibility, split player activity, killfeed, and incident alerts into separate channels and validate feed output after every wipe.

At a glance

This page covers Rust Console player activity feed routing in Discord.
It is for owners and moderation teams who need clear, searchable activity timelines.
Use linked guides to separate killfeed, player activity, and staff-only incident signals.

What this feature solves

Routes player joins, leaves, and kill events into dedicated Discord feed channels.
Supports split feed design for public visibility and staff-only moderation context.
Improves incident review by preserving a readable timeline of player activity.

Who this is for

Moderators handling support, cheating reports, and raid follow-up.
Owners who need better visibility into player engagement and server health.
Admin teams that want feed channels structured by intent.

Example routing checklist

Create separate channels for public killfeed, player activity, and staff alerts.
Validate each feed stream with test events before announcing to players.
Review channel permission changes after wipes to prevent silent feed failures.

What this looks like in a real server

Owner checkpoint

Owner confirms policy, scope, and rollback path before staff run live tests.

Staff validation

Admins and moderators run a short smoke test with screenshots and output capture.

Go-live gate

Module goes live only after expected behavior is verified and support notes are published.

Operational trust grid

Setup ease

Use one checklist and keep first deployment scope narrow.

Support clarity

Track expected output and known failure patterns for fast triage.

Uptime confidence

Re-run validation after wipes, host changes, and permission edits.

Workflow depth

Expand only when the current workflow is stable and documented.

Related setup docs and cluster pages

Evidence kit (ready for real assets)

No fabricated proof

Drop real screenshots, command output, testimonials, and case-study metrics into these modules when they are available.

Evidence slot: setup state

Setup panel or channel-routing screenshot with a short caption about why this state matters.

Evidence slot: validation state

Validation screenshot showing healthy status after rollout checkpoints.

Evidence slot: output sample

Operational output sample from real command runs, trimmed to the lines owners need to verify.

Sample command output

/example command here
Expected status: healthy
Owner note: link this to the exact validation step.

Sample configuration block

Channel: #staff-alerts
Role gate: Admin+
Validation window: after wipe + post-change smoke test

"Add a verified owner quote here once approved for publication."

Capture with: role, server size, host, date, and workflow scope.

"Add a support outcome note with one measurable operational change."

Capture with: reviewer identity, affected workflow, and evidence link.

Before

Record baseline metric (for example response time, setup errors, or support volume).

After

Record measured result and date range from the same workflow context.

Scope

Document server type, host, staff size, and feature set so claims stay comparable.

Limits

State tradeoffs or caveats to keep proof balanced and trustworthy.

Case-study structure

Before: Describe the concrete operational pain point.

Implementation: List the rollout sequence and checks used.

After: Add measured outcomes and unresolved constraints.

Evidence publication checklist

Attach screenshot IDs, output snippets, reviewer attribution, and the exact period observed.

Link each claim to one evidence block so off-site citations can verify context quickly.

Frequently asked questions

Can I separate player joins/leaves from killfeed?: Yes. Helios supports separate routing for killfeed and player activity channels.
Do I need WebRCON for reliable feed data?: Yes. A healthy WebRCON connection is required for reliable live event ingestion.
Can this help moderation workflows?: Yes. Staff can use activity timelines to support incident response and player reports.

Build a player activity timeline your moderators can trust.

Split feed channels by purpose, validate output under load, and keep a clear troubleshooting path.

Launch Setup Compare Options