Best ORP and ZORP Settings for Rust Console: Zone Size, Activation Delay and Expiry

What ORP and ZORP actually do on Rust Console

ORP (offline raid protection) and ZORP (zone offline raid protection) both solve the same problem: stopping people from cracking your base while every defender is logged off. ZORP is the zone-based version. When your whole team goes offline, a protection zone seals the base so it cannot be damaged or its cupboard accessed. When someone logs back in, the zone opens and the base fights and builds like normal. That open state is the part people forget, and it is the part that keeps this from ruining live PvP.

Here is the console truth up front. There are no add-ons to install on Rust Console, so nothing you put into the game itself gives you ZORP. It runs through your server settings and a bot connected over WebRCON that creates and manages protection zones for you, watches who is online, and flips the seal on and off. That is how it works on PS4, PS5 and Xbox, and it is worth understanding the mechanics before you tune anything. Our full Rust Console offline raid protection pillar walks through the setup end to end.

Most systems show the zone state with colour. Green means a teammate is online and the base is open. Red means everyone is offline and the base is sealed. Some add a short transition state in between. If you ever see your base flash green while nobody is home, that is not a cosmetic bug, it is a real window where the base is raidable, and we will cover why it happens below.

Zone size: cover the whole base, not just the core

The single most common ZORP mistake is a zone that only covers the middle of the base. The seal protects everything inside the radius. Anything outside it (an external tool cupboard, a peek turret, a garage door, a wall you extended last wipe) is fair game. Raiders learn to look for the edge of a zone and attack the parts that stick out.

Set the radius to cover your entire footprint plus a small buffer, not the smallest circle that fits your loot room. Stand at the furthest corner of your base, then at the opposite corner, and size the zone so both sit comfortably inside with a few metres to spare. For a solo or small base that is often somewhere around a 25 to 35 metre radius. For a bigger clan compound with external gear it can be 45 to 60. There is no single magic number, because it depends on your build, which is the whole point: measure your base, do not guess.

Two guardrails. Do not make the zone so large it swallows a neighbour or the road, because overlapping seals get messy and you end up protecting things you did not mean to. And if your system has a minimum distance between zones, keep it larger than your radius so zones cannot stack on top of each other and so a raider cannot plant a decoy zone right against your wall. If you add onto your base mid-wipe, resize the zone the same day, or the new rooms are protected by nothing.

Activation delay: the gap that gets bases raided

Activation delay is the wait between your last teammate logging off and the seal actually arming. It exists for a good reason: you do not want the base flipping sealed the instant someone rubber-bands offline for ten seconds, and you do not want a player sealing themselves in to abuse it. But this delay is also the number one reason people ask why their ZORP base still got raided. Whatever that delay is, it is a window where you are offline and not yet protected. A raider who watches you log off can start in that window.

Keep the delay short. Aim for something around 5 minutes. That is long enough to ride out a quick disconnect or relog, and short enough that the open window is too small to run a real raid through. If your delay is set to 15, 30 or 60 minutes, you have handed watchers a large, predictable head start every single night. If it is set to zero, you can get flappy behaviour and the odd seal at a bad moment, so a few minutes is the balance.

There is a matching side on the way back. When a teammate logs in, the zone opens so they can play. A good setup keeps the seal up for a brief moment while they load in, so you are not exposed the very second your character appears and before you can grab a gun. Short arm delay, gentle open on return: that combination protects the offline hours without stealing your live fights.

Expiry: how long a sealed base stays protected

Expiry is how long a zone survives with the team continuously offline before it deletes itself and the base goes raidable again. It exists so a server is not clogged with dead zones from players who quit three weeks ago. The trade-off is obvious once you say it out loud: too short and your base opens up while you are simply asleep or at work, too long and abandoned bases stay invincible and choke the map.

For a normal weekly or biweekly wipe, an expiry in the range of 24 to 36 hours is a sensible default. It comfortably covers a work day plus a sleep, and it clears out genuinely abandoned bases within a day or so. If your community plays hard the first 48 hours and then thins out, you can lean shorter. If you run a slower, more casual server where people vanish for a couple of days and come back, lean longer, and tell them the limit so nobody is surprised.

Two things to set alongside expiry. Zones should clear at wipe so a fresh map does not inherit last week's seals sitting over empty ground. And communicate the expiry number to your players, because "I was offline for three days and got raided" is almost always expiry doing exactly what it was told. Bake it into your wipe day checklist so it is handled every cycle instead of remembered by luck.

Team vs clan tracking: why the seal opened while you were offline

This is the setting nobody talks about, and it causes the raids that feel impossible. The seal should arm only when every registered teammate is offline, and it should open only when at least one is genuinely back online. If the system misreads who is present, one of two bad things happens. Either it seals while a defender is still home (annoying, breaks their session), or, far worse, it thinks someone is online when they are not and leaves your base wide open all night.

On console this is harder than it sounds, because presence is read off the WebRCON console stream, which is a noisy, shared feed. A player's kill line, a laggy read or a dropped message can all be misinterpreted. A classic failure: a sleeping teammate gets killed, that kill line reads as "activity," the system decides they are online, and it quietly unseals the base in the middle of a raid. You were offline the whole time. The seal just believed a bad signal.

So when you compare setups, care about how presence is decided, not just that ZORP exists. The right approach reads your online roster from an authoritative record of who is actually connected, not from a single log line, and it requires confirmation before opening a base that is currently sealed. Make sure your team, not just the flag owner, is all registered, so protection actually waits for the last person and lifts for the first.

Why is my ZORP base still getting raided? The checklist

Run through these in order. Nine times out of ten, one of them is the culprit, and every one is fixable in a couple of minutes.

The zone was too small, so a turret, an external cupboard or an extended wall sat outside the seal. The activation delay was long, so a watcher hit the base in the gap between your logout and the seal arming. Expiry fired, because the team was offline longer than the limit and the zone deleted itself on schedule. Presence was misread, so the system thought a teammate was online and never sealed, or unsealed mid-raid off a bad signal. Not everyone was registered on the team, so protection kept waiting for a member who was never really tracked. Or the base was extended after the zone was set, and the new rooms were never inside it.

There is one more, and it is the quiet one: the bot dropped its connection. When a Facepunch patch lands, G-Portal auto-updates and reboots your server, which knocks the bot offline until it reconnects. If the zone engine does not re-assert your seals the moment it is back, a base can sit unprotected or flash raidable during the gap. That is a reliability problem, not a settings problem, and it is why a system that survives restarts matters as much as the numbers. If your current tool keeps dropping the connection, no ZORP value will save you.

A settings starter that protects offline without breaking PvP

Put it together and here is a starter you can adjust to your server. Zone radius: measured to cover your whole base plus a few metres, roughly 25 to 35 for small builds and 45 to 60 for compounds. Activation delay: around 5 minutes. Return buffer: a short grace so you are protected while you load in. Expiry: 24 to 36 hours for weekly and biweekly wipes. Minimum distance between zones: larger than your typical radius so zones never overlap. Team tracking: whole team registered, presence read from an authoritative online roster, and confirmation required before a sealed base ever opens.

Pair this with alerts so you are never guessing. Knowing the moment a sealed base is even tested lets you decide whether to log in and defend, and it turns a silent overnight loss into something you can react to. Our raid and admin alerts guide covers how to wire that up on console.

This is exactly the behaviour Vantic is built for: it reads presence from your real online roster instead of a single noisy log line, creates zones already sealed so a reconnect never flashes your base green, and re-asserts the seal automatically after a G-Portal patch reboot. Whatever you run, hold it to that same bar. Offline bases stay sealed, live PvP stays honest, and "why did my base get raided" stops being a mystery.

Frequently asked questions

Keep reading

Rust Console offline raid protection · raid and admin alerts · keep the bot connected · wipe day checklist · best Rust Console bot