PvP-first servers
Use longer cooldowns and restricted role access to reduce teleport abuse.
Home / Rust Console TP Home Bot for Discord
Rust Console Bot Use CaseRust Console TP Home Bot for Discord
Helios helps Rust Console Edition server owners manage TP and home workflows through Discord-based commands and server rules. It is designed for owners who want teleport systems that fit their community without forcing staff to manually handle every player request.
Owners can tune cooldowns, delays, permissions, and player expectations so TP/home stays useful for PlayStation and Xbox communities without turning into a moderation problem.
Use the linked setup guides to get this running quickly, then test with staff before going live.
Quick take
TP home works best when owners define cooldowns, delays, and role gates first, then test the full player flow before opening it server-wide.
At a glance
- This page covers Rust Console TP/home bot setup from Discord.
- It is for owners balancing teleport convenience with fair gameplay rules.
- Use linked docs to configure cooldowns, role gates, and post-wipe validation checks.
What this feature solves
- Controls TP/home enablement, delay, and cooldown settings per server.
- Supports role-gated teleport access and optional feed logging.
- Keeps teleport behavior aligned with wipe policy and moderation rules.
Who this is for
- Owners introducing TP/home convenience without breaking server balance.
- Admins tuning cooldowns and permissions based on community rules.
- Support staff helping players understand teleport limits.
Example balance checklist
- Set base cooldown and delay values before enabling open player access.
- Apply required-role controls for high-impact teleport scenarios.
- Retest TP/home behavior after wipes, map changes, or role-policy updates.
Common server-owner scenarios
Community-focused servers
Use more permissive settings but keep delay and abuse monitoring in place.
VIP-aware servers
Grant role-based benefits with explicit limits and documented exceptions.
Post-wipe reset servers
Run full TP/home validation before opening access to the player base.
Validation and troubleshooting checkpoints
- Retest cooldown and delay behavior after every wipe or major policy change.
- Audit required-role settings whenever staff permissions are updated.
- Review feed logs for repeated abuse patterns and adjust rules quickly.
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 require a role for TP/home usage?
- Yes. Helios supports required-role controls for TP/home access.
- How do I reduce TP abuse?
- Increase cooldowns, use role gates, and monitor feed logs for repeated misuse.
- Should TP/home be tested after wipe?
- Yes. Re-test cooldowns, bind flow, and role behavior after wipe changes.
Roll out TP/home with policy-first controls.
Set role boundaries, validate behavior in staff tests, then open access gradually.