Helios Rust Console Bot Documentation

Offline Protection

Owner setup guide for /orp settings, player ORP creation flow, and zone behavior in Helios.

Overview 🚀

/orp is the admin command for Helios Offline Protection. It lets staff configure how ORP zones behave per server, review existing zones, and wipe zones when needed.

Important: players do not create ORP zones with /orp. Staff use /orp to configure the system, and players create or replace their own ORP zone in-game through the ORP quick-chat with "Can I Build Here"

Who This Is For 🎯

  • Owners setting up ORP for one or more servers
  • Admins adjusting ORP rules after wipe or balance changes
  • Staff reviewing, verifying, or removing ORP zones

Requirements 📌

  • Connected server in Helios
  • Manage Server permission in Discord
  • Premium enabled for the target server
  • Server-side custom zone commands available, because Helios creates and edits ORP zones through zone commands
  • For Clan mode: clan data set up in Helios and clan members linked correctly

How ORP Works

  1. Staff configure ORP with /orp settings.
  2. A player uses the ORP quick-chat trigger in-game.
  3. Helios checks whether that player is allowed to create an ORP zone.
  4. If valid, the player gets a Yes/No confirmation prompt.
  5. Helios creates one ORP zone centered on that player's current base position.
  6. While tracked members are online, the zone stays Online.
  7. After the last tracked member goes offline, the zone moves to Pending.
  8. When the activation timer ends, the zone becomes Protected.
  9. When the protection timer expires, the zone is removed.
  10. If a tracked member comes back online before or during protection, the zone returns to Online.

Zone States

Helios uses three main ORP states:

  • Online: tracked members are online, so the zone is active but not protecting the base
  • Pending: nobody tracked is online and the activation countdown is running
  • Protected: ORP protection is live for that zone

When a zone is protected, Helios applies the protected color and disables building, building damage, and base damage inside that ORP zone.

Setup ⚙️

  1. Run /orp settings server:"<SERVER>".
  2. Review the current ORP panel values before changing anything.
  3. Turn Offline Protection on.
  4. Choose whether the server should use Team mode or Clan mode.
  5. Set the ORP zone Size.
  6. Set Minimum Distance so new ORP zones cannot be placed too close to each other.
  7. Set Minimum Team to control how many linked members are required before a zone can be created.
  8. Set Activation Time to control how long a base must stay offline before ORP activates.
  9. Set Expires In to control how long protection lasts before the zone is removed.
  10. Set Protected Color and Online Color if you want visible state differences.
  11. Set Radiation only if you want protected zones to apply radiation damage.
  12. Configure Feed if you want ORP activity sent to a Discord channel.
  13. Decide whether Show Chat msg should stay on or off for zones.
  14. Click Sync Monuments if you want Helios to reapply its built-in monument zone adjustments.

Orp settings

Commands or Controls 💬

/orp settings server:"<SERVER>"
/orp list server:"<SERVER>"
/orp wipe server:"<SERVER>"
/orp wipe server:"<SERVER>" user:"<DISCORD USER>"
/orp wipe server:"<SERVER>" gamertag:"<LEADER NAME>"

Settings Reference

Current defaults in code:

  • Size: 30
  • Minimum Distance: 10
  • Radiation: 0
  • Minimum Team: 1
  • Activation Time: 15
  • Expires In: 1440
  • Protected Color: 250,0,0
  • Online Color: 250,250,0
  • Mode: Team
  • Show Chat msg: On

Offline Protection

Turns the ORP system on or off for that server.

  • Enabled: players can create and use ORP zones
  • Disabled: Helios ignores the ORP player flow on that server

Team/Clan Mode

Controls who Helios tracks for ORP status.

  • Team: ORP follows in-game Rust team membership
  • Clan: ORP follows Helios clan membership instead

Use Clan mode only if your clan setup is already clean. In clan mode, every clan member must have a linked in-game account before that clan can create ORP.

Size

Controls the ORP zone radius used when Helios creates the zone.

  • Larger size = more base area covered
  • Smaller size = tighter protection area

This setting also updates existing ORP zones when changed.

Minimum Distance

Controls how close a newly placed ORP zone can be to another ORP zone.

  • Lower value = easier placement in crowded areas
  • Higher value = more spacing between ORP zones

If a player tries to create a zone too close to another one, Helios blocks it.

Radiation

Controls radiation damage applied while a zone is in the Protected state.

  • 0 = no radiation
  • Higher values = more radiation pressure inside the protected zone

Radiation is removed again when the zone returns to Online.

Minimum Team

Controls the minimum number of tracked members required before a zone can be created.

  • In Team mode, this means minimum team members
  • In Clan mode, this means minimum clan members

If the player group is below this value, Helios refuses the ORP request.

Activation Time

Controls how many minutes Helios waits after everyone goes offline before ORP activates.

  • 0 = protection can move from Online to Protected immediately through the pending check
  • Higher values = longer delay before protection starts

This does not move an existing zone. It changes when protection begins.

Expires In

Controls how many minutes a zone stays protected before Helios deletes it.

  • Shorter value = ORP ends sooner
  • Longer value = protection lasts longer

This is a hard expiration. Once the timer is reached, Helios removes the zone.

Protected Color

Controls the zone color used while the zone is Protected.

Format must be R,G,B using numbers from 0 to 255.

Example:

250,0,0

This setting updates existing ORP zones when changed.

Online Color

Controls the zone color used while the zone is Online.

Format must be R,G,B using numbers from 0 to 255.

Example:

250,250,0

This setting updates existing ORP zones when changed.

Feed

Sets the Discord channel that receives ORP feed messages for that server.

With a feed channel selected, Helios can post:

  • zone created messages
  • ORP status changes
  • ORP zone activity updates

Pressing Feed again when one is already set removes the channel.

Show Chat msg

Controls the zone chat-message flag Helios applies to ORP zones.

Simple rule:

  • On: zone chat messaging stays enabled
  • Off: zone chat messaging stays disabled

This setting updates existing ORP zones when changed.

Sync Monuments

This re-runs Helios' built-in monument zone adjustment pass for that server.

Inference from source: this is used to reapply known monument zone sizes after startup, plugin changes, or map-related changes. It is not a player ORP placement button.

Player Creation Flow

Players use ORP in-game, not through Discord slash commands.

Basic Flow

  1. The player uses the server's ORP quick-chat trigger.
  2. Helios checks whether the player is eligible to create a zone.
  3. Helios sends a Yes/No confirmation message.
  4. The player stands in the center of the base and confirms.
  5. Helios creates the zone at that location.

What Helios Checks First

Before creating a zone, Helios checks that:

  • ORP is enabled on that server
  • the player is the leader of the tracked team or clan
  • the team or clan meets Minimum Team
  • in Clan mode, all clan members are linked
  • the placement is not too close to another ORP zone
  • the player position can be read successfully

Replacing an Existing Zone

If the leader already has an ORP zone, Helios does not blindly create a second one.

Instead:

  1. Helios warns the player that a zone already exists.
  2. The player confirms whether they want to replace it.
  3. Helios deletes the old zone and creates a new one at the new position.

If your server setup maps different quick-chat slots for ORP, use your actual mapped trigger in player instructions.

Reviewing Zones

Use /orp list server:"<SERVER>" to review the current ORP zones on a server.

The zone list shows useful details such as:

  • zone name
  • leader
  • tracked team or clan ID
  • member count
  • current status
  • activation or expiration timing when applicable

This is the fastest way to verify whether ORP actually created a zone and what state it is currently in.

orp list

Wiping Zones

Use /orp wipe when you need to remove ORP zones.

You can wipe:

  • every ORP zone on a server, or
  • only the zone(s) for one specific leader

Full Wipe

/orp wipe server:"<SERVER>"

Wipe One Leader By Discord User

/orp wipe server:"<SERVER>" user:"<DISCORD USER>"

This uses the linked gamertag for that Discord user.

Wipe One Leader By Gamertag

/orp wipe server:"<SERVER>" gamertag:"<LEADER NAME>"

Wipe behavior:

  1. Helios shows a confirmation prompt.
  2. Staff confirm the wipe.
  3. Helios deletes the matching ORP zone records and live zones.
  4. Helios verifies the result with a follow-up zone check.

Common Issues 🧯

Problem

Player uses the ORP trigger and nothing happens.

Likely Cause

ORP is disabled, the server is not premium, or the wrong trigger is being used.

Fix

Check /orp settings, confirm ORP is enabled, and verify the player is using the correct ORP quick-chat trigger for that server.

Prevention

Test the full player flow after every wipe or trigger change.

Problem

Player gets blocked from creating a zone.

Likely Cause

They are not the tracked leader, they do not meet Minimum Team, or the zone is too close to another ORP.

Fix

Check the current ORP mode, confirm leadership and member count, then retest from the center of the base with enough spacing from nearby ORP zones.

Prevention

Document your live ORP rules for players so they know the leader and member requirements.

Problem

Clan ORP will not create.

Likely Cause

One or more clan members are not linked in Helios.

Fix

Link every clan member first, then try again.

Prevention

Require linking as part of clan setup before enabling clan-based ORP.

Problem

Protection never turns on.

Likely Cause

A tracked member is still considered online, or the activation timer has not finished yet.

Fix

Check /orp list and the ORP feed to confirm whether the zone is Online or Pending, then wait out the activation time.

Prevention

Use a realistic activation timer and test with a clean offline scenario.

Problem

Protection ends sooner than expected.

Likely Cause

Expires In is set lower than intended.

Fix

Increase Expires In in /orp settings.

Prevention

Set the expiration window intentionally and note it in your server rules.

Tips / Best Practices ⭐

  • Start in Team mode unless you already maintain clan links correctly.
  • Keep one staff-only ORP feed channel for setup testing and incident review.
  • Test one full create -> pending -> protected cycle before announcing ORP to players.
  • Use moderate zone sizes first, then expand only if real bases are clipping outside protection.
  • Keep Minimum Distance high enough to reduce base-overlap abuse.
  • Only add radiation if you deliberately want protected zones to be hostile to stand in.
  • Re-run Sync Monuments after map-related changes if ORP placement starts behaving oddly near monuments.