Helios Rust Console Bot Documentation
Discord Owner Setup for Rust Console Servers
Required Discord channels, roles, and launch checklists before enabling Helios modules.
Page Summary
- This page covers owner/admin Discord setup for the Helios Rust Console bot.
- It is for server owners who need role boundaries and channel structure before launch.
- Complete this before server connection setup (WebRCON) and feature setup.
Overview
Owner setup decides who can run Helios commands and where bot messages should go.
Related Product Pages
- Rust Console Edition Bot Overview
- Rust Console Discord Bot Overview
- Rust Console Server Automation
- Helios vs Other Rust Console Bots
Who This Is For
- Server owners
- Head admins implementing owner policy
Requirements
Administratoraccess for owner account- Ability to create roles and channels
- Final staff list for owner, admin, and moderator teams
Setup
1. Create Core Channels
| Channel | Purpose | Recommended Visibility |
|---|---|---|
#helios-ops | Admin and owner command execution | Owner + Admin only |
#helios-alerts | Critical alerts, raid pings, failures | Owner + Admin + Moderator |
#killfeed | Public or staff kill feed output | Community or staff based on policy |
#player-feed | Join and leave events | Moderator + Admin |
#helios-audit | Manual notes for wipes and destructive actions | Owner + Admin only |
2. Create Staff Roles
| Role | Permission Target | Notes |
|---|---|---|
| Owner | Administrator | Keep membership small |
| Admin | Manage Server | Daily server management and module setup |
| Moderator | Read-heavy command scope | No billing or wipe control |
3. Configure Link Roles
Use /set link-role to assign the default role granted on /link.
4. Set Notification Channels
Configure feed targets with /dcfeed add, /dcplayerfeed add, and /set raid-channel.
Commands or Controls
/set link-role
/dcfeed add
/dcplayerfeed add
/set raid-channel
Example Use Case
Owner creates #helios-ops, grants Manage Server to admins only, and keeps Administrator restricted to owners before any server connection is attempted.
Common Issues
- Too many members hold
Administrator. - Feed channels are created but Helios cannot send embeds.
- No dedicated audit channel for wipe and premium actions.
Tips / Best Practices
- Review role membership every wipe cycle.
- Keep all premium and wipe actions in a dedicated owner approval process.
- Document your final channel and role IDs in an internal runbook.
First-Time Setup Checklist
- Owner/admin/mod roles created
-
#helios-opscreated and locked down - Feed channels created with send/embed permissions
- Link role configured
- Raid alert channel configured