Helios Rust Console Bot Documentation

Rust Console Killfeed Troubleshooting

Diagnose and fix Rust Console killfeed issues in Helios, including silent channels, wrong routing, noisy feeds, and post-wipe failures.

Page Summary

  • This guide helps resolve killfeed issues in Helios for Rust Console.
  • It is for owners and moderators handling live feed reliability incidents.
  • Use it during outages and after wipe resets.

Who This Is For

  • Owners responsible for uptime and live-event visibility.
  • Admins diagnosing feed routing and permission issues.
  • Moderators investigating player-reported event inconsistencies.

What This Covers

  • A priority troubleshooting sequence for killfeed failures.
  • Root-cause patterns for silent, misrouted, noisy, or post-wipe-broken feeds.
  • Fast recovery actions that minimize downtime and confusion.

Prerequisites

  • Confirmed host credentials in Server Connection Guide (WebRCON).
  • Access to feed channel settings and permission controls.
  • One staff test account for feed validation checks.

Troubleshooting Workflow

  1. Confirm server health in Server Connection Guide (WebRCON).
  2. Verify channel permissions and feed mappings.
  3. Re-test one event type at a time.
  4. Reintroduce full feed set only after stable output.

Issue: Feed Channel Is Silent

  • Likely cause: permission or routing mismatch.
  • Check: bot send/embed permissions and feed channel IDs.
  • Fix: reapply mapping and rerun event smoke tests.

Issue: Events Show in Wrong Channel

  • Likely cause: overlapping mapping or stale channel selection.
  • Check: each feed source and destination mapping.
  • Fix: simplify to one mapping per channel purpose.

Issue: Feed Is Too Noisy

  • Likely cause: public and staff events mixed together.
  • Check: event categories by channel.
  • Fix: split killfeed, player flow, and staff alerts.

Issue: Feed Broke After Wipe

  • Likely cause: changed roles/channels or stale assumptions.
  • Check: role permissions, channel IDs, server status.
  • Fix: run full post-wipe feed validation checklist.

Validation Checklist

  • Run at least one test event per feed type after each fix.
  • Confirm events route to the expected public or staff channel.
  • Capture one screenshot and one output sample for your runbook.

Related Guides

Related Feature Pages

Next Steps

  1. Work through one issue category at a time and capture fixes in your runbook.
  2. Revalidate feed routing after role, channel, or host changes.
  3. Escalate with exact output examples instead of summary descriptions.