Small community server
Use one public killfeed channel and keep player join/leave updates moderate.
Home / Rust Console Killfeed Bot for Discord
Rust Console Feature PageRust Console Killfeed Bot for Discord
Helios gives Rust Console Edition server owners a Discord killfeed system that turns server events into readable player activity updates. Owners can use killfeeds to track PvP activity, make the server feel alive, and give players a clearer view of what is happening across the community.
It also helps staff separate public killfeed posts, player activity, and moderation alerts so PlayStation and Xbox communities do not lose important information inside one noisy channel.
Start with one feed map for staff and one for players, then expand once event volume is stable.
Quick take
A Rust Console killfeed bot works best when owners split player-facing updates from staff-only signals, then validate output after wipes, permission changes, and connection updates.
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
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 Guide.
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 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.