Helios Rust Console Bot Documentation

Create Your ORP Zone

Request Offline Protection for your own base through Discord or in-game quick chat.

Last reviewed
Maintained by
Helios RCE

Stand at the centre of the base you want to protect. You must be online on the chosen Rust server, lead its tracked team or Helios clan, and meet the server's ORP rules. Staff configure those rules in Offline Protection.

1. Open your private player menu

In Discord, run /actions server:"<SERVER>", choose the correct server, and select ORP. You need a linked account and Premium on that game server; ordinary players do not need Manage Server permission.

Private Player Actions menu on Helios Bot Testing, with its ORP button and an Active feature label

Active means the ORP feature is enabled. Check the zone status inside ORP to see whether your base has a saved zone.

2. Check the zone before requesting one

ORP player view showing no saved zone, Set ORP enabled, and Remove ORP unavailable

The test account has no saved zone. Only the menu was opened; Set ORP was not pressed.

When ready, choose Set ORP. This starts a real placement request at your current in-game position, including replacement of an existing matching zone when eligible. The Discord route does not add a separate in-game Yes/No step. Check the resulting saved zone; a request-sent message alone is not proof that placement succeeded.

Prefer in-game quick chat?

  1. Stand in the centre of your base and use Can I Build Around Here?.
  2. Read Helios's eligibility and Yes/No prompt.
  3. Choose Yes to continue or No to cancel. Read any additional replacement prompt before agreeing to replace an existing zone.
  4. Check the saved zone and the server's ORP feed.

Use your community's configured instructions if the trigger differs. In-game placement does not require a Discord admin role; a required Discord role or Clan mode can still require linked accounts.

Why a request can be refused

Actual ORP Tracking and Timing controls in Team mode, with Minimum Team 1, no required role, and activation and expiry in minutes

Existing testing-server settings, inspected without saving. Your server may use different rules.

CheckWhat must be true
ServerConnected, Premium, and ORP enabled
LeadershipYou lead the tracked in-game team or Helios clan
Minimum TeamYour tracked group meets the configured member count
Clan modeEvery clan member has the required Helios account link
Required RoleThe placing leader is linked and holds it; Team Needs Role extends that check to all tracked members
PlacementHelios can read your position and the base meets spacing and location rules
RestrictionsNo applicable temporary ORP ban, Combat Lock, or scheduled creation block

Read the state correctly

ORP lifecycle diagram: Online, Pending after everyone leaves, Protected after the activation delay, and removal at expiry; any tracked member returning restores Online

A newly saved zone around an online team is Online, with ordinary raiding still possible. Pending is the activation wait. Protected is the protection state. See ORP states and settings, or Remove your zone when you intend to give up protection.