Helios Rust Console Bot Documentation

G-Portal Rust Console Setup Guide for Helios

Host-specific Helios setup guide for G-Portal Rust Console servers, including server connection (WebRCON) validation and rollout checks.

Page Summary

Who This Is For

  • Owners and co-owners managing G-Portal server operations
  • Admins handling setup and command validation
  • Staff leads preparing post-wipe relaunch checklists

What Setup Problem It Solves

G-Portal setups usually fail for one of three reasons: incorrect host details, incorrect server connection port or RCON Password, or skipped validation tests. This page gives a repeatable flow to avoid those failures.

Related Product Pages

Prerequisites

  • Helios already added to your Discord server
  • One designated owner operations channel
  • G-Portal server host, server connection port, and RCON Password confirmed from active server settings
  • Owner/admin role boundaries already defined

Setup Workflow

  1. Run Owner Setup if roles and channels are not finalized.
  2. Add the server using /server add with current G-Portal values.
  3. Validate command execution with /cmd send command:"fps".
  4. Validate player polling with /whoson.
  5. Enable initial modules in /settings server after command tests pass.
  6. Turn on killfeed and admin alerts first for staff visibility.

Commands or Controls

/server add
/server list
/server edit
/cmd send command:"fps"
/whoson
/settings server

Example Validation Sequence

/server add name:"EU Main" host:"<GPORTAL_HOST>" port:28016 password:"<PLACEHOLDER_RCON_PASSWORD>"
/server list
/cmd send command:"fps" server:"EU Main"
/whoson server:"EU Main"
/settings server server:"EU Main"

Common Issues

Problem

/cmd send fails right after adding the server.

Likely Cause

Host, port, or password mismatch.

Fix

Use /server edit, re-check G-Portal values, and run the same validation sequence again.

Problem

Commands work intermittently after restart windows.

Likely Cause

Server is in a host-side restart or maintenance cycle.

Fix

Wait for server availability, then re-run /cmd send and /whoson before re-enabling module rollouts.

Tips / Best Practices

  • Keep server naming consistent by region and mode.
  • Save a simple internal checklist after first successful setup and reuse it for additional servers.
  • Re-run health checks after wipe, host migration, or password rotation.

Related Guides