Owner checkpoint
Owner confirms policy, scope, and rollback path before staff run live tests.
Home / Rust Console player activity feed in Discord
Rust Console Bot Use CaseRust Console player activity feed in Discord
Helios helps owners and moderators monitor player flow and combat activity with cleaner feed routing.
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
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
Built for Rust Console owner workflows
Linked setup path
Each workflow points back to Helios setup docs so owners can move from overview pages into the exact configuration steps they need.
Daily staff use
These pages focus on owner, admin, moderator, and player workflows that come up during wipes, incidents, and routine support.
Role-aware rollout
Helios pages consistently point owners toward permission checks, staff validation, and phased launch instead of broad first-day rollouts.
Clear next steps
Every feature cluster links back to setup docs, related feature pages, and troubleshooting paths so staff can act when something breaks.
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.