Helios Rust Console Bot Documentation

How TP/Home Works for Rust Console Server Owners

Learn how TP/home should be configured in Helios for fair gameplay with role gates, cooldown policy, and post-wipe validation.

Page Summary

  • This guide explains TP/home behavior for Rust Console server owners.
  • It is for teams balancing convenience with gameplay fairness.
  • Use it when creating or revising TP/home policy.

Who This Is For

  • Owners deciding TP/home rules.
  • Admins tuning cooldown and delay settings.
  • Moderators handling teleport abuse reports.

What This Covers

  • A policy-first approach to keep TP/home fair.
  • Configuration sequence across delay, cooldown, and role gates.
  • Validation and troubleshooting checkpoints for stable enforcement.

Policy-First Setup Model

  1. Define allowed TP/home behavior by player role.
  2. Decide cooldown and delay values before launch.
  3. Define abuse escalation and override rules.

Configuration Flow

  1. Start with TP/Home Setup.
  2. Review controls in TP/Home Command Panel.
  3. Apply zone interactions with Zone Setup.
  4. Validate against event and wipe policy in Automation and Events.

Validation Checklist

  • Teleport delay works as configured.
  • Cooldown values are enforced by role.
  • Restricted roles cannot bypass policy.
  • Staff can trace abuse patterns in feed logs.

Troubleshooting Checkpoints

  • TP is too permissive: increase cooldown and tighten role gates.
  • TP fails for everyone: verify panel enablement and role requirements.
  • Rules changed after wipe: rerun full TP/home smoke tests.

Related Guides

Related Feature Pages

Next Steps

  1. Finalize role gates and cooldown policy with owner sign-off.
  2. Validate abuse controls with moderators before player rollout.
  3. Re-test TP/home behavior after each wipe cycle.