What is offline raid protection in Rust Console?

Offline raid protection (ORP) stops a base being raided while everyone who lives in it is logged off. In Helios, a team leader creates a protected zone around their base in game. While anyone on the team is online the zone does nothing; once the last member logs off and your activation delay passes, building and base damage inside the zone are switched off until the protection expires or someone logs back in.

Yes. Offline raid protection is a premium module - if premium lapses the panel opens but protection can't be enabled.

When does protection turn on?

After the whole team logs off and the activation delay you configured passes. It ends when the expiration window runs out or a team member logs back in.

Can players make their own ORP zones?

Yes. Team leaders create their zone in game, within the size and team-count rules you set in /orp settings. Staff do not have to place anything by hand.

Does ORP stop online raiding too?

No. While any tracked member is online the zone stays in the Online state and the base can be raided normally. Protection only applies once the whole team is offline.

Can I limit raiding to certain hours instead?

Yes. Scheduled Raid Protection with /settings srp sets weekly raiding hours server-wide - outside that window building damage is off for everyone. It is premium and can run alongside ORP.

How long does protection last?

As long as the Expires In value you set. The default is 1440 minutes, which is 24 hours, after which the zone is removed.

How do I reset ORP zones at wipe?

Run /orp wipe server:"..." - you can clear everything or target one player's zones.

Does ORP work on both PlayStation and Xbox?

Yes. Helios connects to Rust Console Edition servers over WebRCON, so ORP works the same on PlayStation and Xbox. There is nothing to install on the server.

Home / Rust Console Offline Raid Protection

Rust Console ORP Bot

Offline Raid Protection for Rust Console

Last updated 21 August 2026 · Verified against Helios 2026.8

Offline raid protection stops a base being raided while everyone who lives in it is logged off. You set the rules once — how long a base has to be empty, how long protection lasts, how big the zone is — and after that players protect their own bases without asking staff for anything.

Open Full ORP Docs Create ORP Zones

Important: Staff configure ORP with /orp settings. Players use the server's ORP quick-chat trigger in game, normally Can I Build Here. ORP is a premium feature.

Quick answer

To set up Rust Console offline raid protection, run /orp settings server:"<SERVER>", turn Offline Protection on, choose Team or Clan tracking, then set the zone Size, the Activation Time (how long a base must be empty before protection starts, default 15 minutes) and Expires In (how long protection lasts, default 24 hours). Team leaders then create their own ORP zone in game with the quick-chat trigger. ORP requires premium.

Why owners turn ORP on

Offline raiding is the single most common reason console players quit a server. ORP is how you take that off the table without turning the server PvE.

Players stop losing everything overnight

A solo who logs off at midnight and comes back to a stripped base usually does not come back again. Protection while offline means progress survives the night, and players keep playing.

Raiding stays real

The moment anyone on the team is online, the zone goes back to Online and the base can be raided normally. ORP removes offline raiding, not raiding.

Staff do not place anything

You configure the rules once. Players create their own zones in game with a quick chat, inside the size and team limits you set, so nobody has to open a ticket to get protected.

Requirements

Server and permissions

A Rust Console server connected to Helios
Premium enabled for the target server
Manage Server permission for staff setup
Server-side custom zone commands available

Team or Clan tracking

Team mode: follows in-game Rust team membership
Clan mode: follows Helios clan membership
Clan mode requires every clan member to have a linked account

How Helios ORP works

Staff configure the system with /orp settings.
A player uses the ORP quick-chat trigger at the center of the base.
Helios checks leadership, group size, account links, distance, and position.
The player receives a Yes/No confirmation prompt.
Helios creates one ORP zone at that base position.
While a tracked member is online, the zone remains Online.
After the last member disconnects, the zone becomes Pending.
When the activation timer ends, the zone becomes Protected.
If a tracked member reconnects, the zone returns to Online.
When the protection timer expires, Helios removes the zone.

ORP zone states

Online

At least one tracked team or clan member is online. The zone exists but does not protect the base.

Pending

No tracked members are online and the configured activation countdown is running.

Protected

Protection is active. Helios applies the protected color and disables building, building damage, and base damage inside the zone.

Set up Offline Raid Protection

Run /orp settings server:"<SERVER>".
Review the current values, then turn Offline Protection on.
Choose Team or Clan mode.
Set Size, Minimum Distance, and Minimum Team.
Set Activation Time and Expires In.
Choose protected and online colors, then decide whether to use radiation.
Configure the Discord ORP feed and zone chat-message option.
Use Sync Monuments when monument adjustments need to be reapplied.
Test a full Online → Pending → Protected cycle before launch.

The Helios offline raid protection settings panel in Discord, showing the ORP toggle, Team or Clan mode, zone size, minimum distance, minimum team, activation time, expiry and colour options — The `/orp settings` panel. Every rule on one screen — set it once and players take it from there.

Raiding hours and ORP schedules

ORP protects individual bases. If you would rather control raiding for the whole server, Helios can put raiding on a weekly timetable instead — or alongside.

Scheduled Raid Protection

/settings srp sets weekly raiding hours in your chosen timezone. Outside the window, building damage is off server-wide, so bases can only be raided during the hours you announced. The schedule repeats every week and is reapplied automatically, including after the server reconnects.

Set up raiding hours →

ORP creation windows and pauses

/orp timers — block new ORP zones during a weekly window. Existing zones keep working.
/orp scheduled-zorp — schedule a recurring ORP pause, optionally wiping zones.
/orp scheduled-raids-remove — drop a saved schedule and go back to normal raiding.

Confirmation in Discord that weekly raiding hours have been saved for a Rust Console server with Helios Scheduled Raid Protection — Weekly raiding hours saved with `/settings srp`. Premium, like ORP itself.

ORP settings and defaults

Setting	Default	What it controls
Offline Protection	Off until enabled	Whether players can create and use ORP zones.
Mode	Team	Tracks in-game Rust teams or Helios clans.
Size	30	ORP zone radius. Changes also update existing zones.
Minimum Distance	10	Required spacing between ORP zones.
Minimum Team	1	Minimum team or clan members required to create a zone.
Activation Time	15 minutes	Offline delay before protection activates.
Expires In	1440 minutes	Protection duration before the zone is removed.
Radiation	0	Radiation applied only while the zone is Protected.
Protected Color	250,0,0	RGB color used during protection.
Online Color	250,250,0	RGB color used while members are online.
Show Chat msg	On	Whether the zone chat-message flag is enabled.
Feed	Not set	Discord channel for ORP creation, status, and activity messages.

Admin commands

Configure and review

/orp settings server:"<SERVER>"
/orp list server:"<SERVER>"

The list shows the leader, tracked group, member count, current state, and timing.

Remove zones

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

Helios confirms the wipe, removes records and live zones, then verifies the result.

Player ORP zone creation

Eligibility checks

ORP is enabled and Premium is active
The player is the team or clan leader
The group meets Minimum Team
Every clan member is linked in Clan mode
The location is far enough from another ORP zone
Helios can read the player's current position

Replacing an existing zone

If a leader already has a zone, Helios warns them first. After confirmation, it deletes the old zone and creates the replacement at the new position instead of creating a duplicate.

Publish your server's actual ORP quick-chat mapping in the player rules.

Helios ORP zone list in Discord showing the zone leader, tracked group, member count and current protection state — `/orp list` — who has a zone, who is tracked, and which state each zone is in right now.

Common ORP problems

Problem	Likely cause	Fix
The quick-chat trigger does nothing	ORP is disabled, Premium is inactive, or the wrong trigger is used.	Check `/orp settings`, Premium, and the configured trigger.
A player cannot create a zone	They are not leader, do not meet Minimum Team, or are too close to another zone.	Confirm mode, leadership, group size, position, and spacing.
Clan ORP will not create	One or more clan members are not linked.	Link every clan member before trying again.
Protection never turns on	A member is still online or Activation Time has not finished.	Check `/orp list` and the ORP feed for Online or Pending status.
Protection ends too soon	Expires In is lower than intended.	Increase Expires In and publish the duration in server rules.

Best practices

Start in Team mode unless clan membership and links are already reliable.
Use a staff-only ORP feed channel for testing and incident review.
Test one complete create → Pending → Protected cycle after every wipe.
Start with moderate zone sizes and expand only when real bases need it.
Keep Minimum Distance high enough to reduce overlapping-zone abuse.
Use radiation only when protected zones are intentionally hostile.
Run Sync Monuments after map or plugin changes if monument placement acts incorrectly.

Frequently asked questions

What is offline raid protection in Rust Console?: It stops a base being raided while everyone who lives in it is logged off. A team leader creates a protected zone around their base in game. While anyone on the team is online the zone does nothing; once the last member logs off and your activation delay passes, building and base damage inside the zone are switched off until protection expires or someone logs back in.
Is ORP premium?: Yes. Offline raid protection is a premium module — if premium lapses the panel opens but protection can’t be enabled.
When does protection turn on?: After the whole team logs off and the activation delay you configured passes. It ends when the expiration window runs out or a team member logs back in.
Does ORP stop online raiding too?: No. While any tracked member is online the zone stays Online and the base can be raided normally. ORP removes offline raiding, not raiding.
Can players make their own ORP zones?: Yes. Team leaders create their zone in game, within the size and team-count rules you set in /orp settings. Staff never have to place one by hand.
How long does protection last?: As long as your Expires In value. The default is 1440 minutes — 24 hours — after which the zone is removed.
Can I limit raiding to certain hours instead?: Yes. Scheduled Raid Protection (/settings srp) sets weekly raiding hours server-wide; outside that window building damage is off for everyone. It is premium and can run alongside ORP.
Does ORP work on PlayStation and Xbox?: Both. Helios connects over WebRCON, so ORP behaves the same on either platform and nothing is installed on the server itself.
How do I reset ORP zones at wipe?: Run /orp wipe server:"..." — you can clear everything or target one player’s zones.

Related ORP guides

Ready to set up Offline Raid Protection?

Configure the server settings first, then test the full player creation and protection cycle before announcing ORP.

Open ORP Setup Player Creation Flow