Skip to main content

What should you check before advertising a Rust server as PvE?

Test the protection you want to advertise with two ordinary players and disposable gear. A PvE browser tag tells people what to expect. Your checks tell you what you can promise them.

Match your label to the running game

Facepunch documents that server.pve applies a PvE browser tag. Check how the server actually shows up in the browser. If you use a plugin to control damage instead, read its setup instructions before changing the built-in setting. TruePVE documents damage rules separately from looting, so a blocked shot or raid does not tell you who can open a box.

Write the promise before building the test. A small server might promise ‘No player combat, base raiding or theft in the open world. Scientists and upkeep still matter.’ Each word must survive a realistic interaction. Build a disposable base on a matching test world, stock the cupboard and set up one locked door, an ordinary storage box and a sleeping spot.

Check the things players expect to keep

Keep test staff powers out of both accounts. Let one person act as the base owner and the other as an unrelated visitor.

Check the things players expect to keep
What you intend to promiseOrdinary-player test and pass condition
No player combat in normal play.Try a direct hit in an open area and check both health bars. When the server promises teammates the same thing, repeat after the accounts join a team.
Strangers cannot raid a maintained home.Have the visitor try the test base wall and locked door. Confirm the pieces take no damage from the agreed raid methods.
A player's sleeper is protected.Have the owner log out with disposable gear. Have a stranger try the agreed damage and access checks, then have the owner reconnect to confirm their state.
A stranger cannot take private gear.Try to open the owner's test box and take spare items from an agreed corpse or dropped bag. Check the visitor and owner separately against the advertised loot rule.
Monuments still give people a combat challenge.Ask a player to visit a familiar monument and check that its NPCs can still damage them. Record any places where you advertise a different rule.

Turn a failed result into a smaller promise or a repair

Imagine Seabank's shot, door and monument checks pass, but the visitor can take cloth from the owner's dropped bag. Hold back the theft claim. Decide whether dropped items are public by design or whether a separate rule needs fixing. If you change loot protection, rerun the box, corpse and bag cases as both an unrelated visitor and an authorized teammate if their access differs.

Record the game build, relevant plugin versions and places tried with the result. Put a failed case on the next change checklist. Recheck affected protections after an update or a change to a zone or plugin.

Publish the same promise in the browser and welcome post

For Seabank's example result, the listing could say ‘PvE with protected maintained bases. Dropped bags are public. Scientists and ordinary PvE hazards remain.’ Add the fuller local rules where new players start. If you announce a special combat area, mark its boundary and test entry, exit and actions crossing the edge before making a separate promise.

Sources

Analytics settings

Analytics are off.

Help improve RustSC with page counts and performance measurements. Privacy details