How to Set Up a Rust PvE Server in 2026
Set up Rust PvE damage rules with TruePVE, test players and sleepers, and choose optional zones, gather rates, decay and recoverable hosting.
On this page
Decide what “PvE” allows before installing a plugin. Can players hurt each other, damage a sleeper or raid an unattended base? Are there places where those rules change? Your answers become the tests to run before inviting the community.
Rust has a native server.pve setting. This guide uses TruePVE for configurable damage rules, with the native setting left as the plugin author requires. Keep the environmental threats you want and test them alongside player damage.
Start with one damage-control system
TruePVE’s author documentation requires:
server.pve falseThat leaves native PvP mode enabled while TruePVE handles damage through its configured rules. Follow the installed version’s release notes and test the entities and damage paths your community uses.
Choose an Oxide or Carbon build supported by the required plugins. Back up before installation or a framework change. If you prefer another system, such as NextGenPVE, check its current author documentation and compatibility. Combine damage systems only where their authors document an integration.
Configure and test TruePVE rules
TruePVE uses RuleSets and Mappings. Its handleDamage option enables damage handling, while useZones enables zone-specific behavior with ZoneManager. Each mapping must refer to a RuleSet you have configured.
Read authorization flags one by one against the generated configuration. Do not treat an ownership-related flag as a blanket promise that players can damage only their own structures.
Run the tests on a recoverable instance with two non-admin accounts. Admin privileges can hide permission faults.
| Test | Result to record |
|---|---|
| Player attacks another player | Friendly-fire behavior |
| Player attacks a sleeper | Offline-player protection |
| Damage to another player’s building | Raiding behavior |
| Fire, explosives and vehicle contact | Outcome for each enabled damage path |
| NPC, animal and environmental damage | Threats that should remain active |
| Restart after a configuration change | Rules and player data still match the intended state |
Add traps, turrets and installed content plugins to the checklist where used. Record the observed result, including failures, rather than ticking a box because the plugin loaded. Stop admitting players if a protection rule fails, and preserve the error.
Add PvP areas only when the rules are clear
TruePVE can apply zone-specific RuleSets through ZoneManager. Add an arena or PvP monument only if the group wants one.
Mark the boundary and tell players what changes when they cross it. Test attacks in both directions, projectiles, overlapping zones and sleeping players. Repeat after a restart. Review exclusion mappings with care: they can restore default Rust damage behavior.
A raid-content plugin may maintain its own zones. Check its rules rather than assuming it uses ZoneManager or the same priority order.
Tune gather rates and decay
Choose progression settings with the group, then change one at a time. Gathering and decay also affect the amount of persistent world data you will maintain.
Gather Manager distinguishes dispensers, pickups and quarries. Carbon has an optional Gather Manager module too. Choose the system you intend to use and follow its current commands.
Try 2x or 3x against your current rates if gathering consumes more of a session than players want. Keep those as experiments, not assumed population preferences.
Facepunch lists decay.scale as a multiplier with a default of 1. Read the live value first. Lower decay can leave more structures in the save, so monitor world growth and publish a cleanup policy. Console command reference
State the map and blueprint wipe policy with room to follow mandatory updates. Players need to know what you intend to retain and what the publisher may require you to reset.
Add content and convenience plugins by need
Start with a task the group wants to do:
| Task | Example to assess |
|---|---|
| Configured raid encounters | Raidable Bases |
| Extra inventory or starter equipment | Backpacks or Kits |
| Travel between agreed locations | NTeleportation |
| Removing allowed structures | Remover Tool |
| Currency or rewards | Economics or ServerRewards |
Check the release, licence, dependencies and framework support for each candidate. You do not need the whole list to open a PvE server.
Raidable Bases needs CopyPaste and prepared base files; it does not generate those files for you. Check your edition’s features before planning events around them. Installing raid content cannot promise that players will return.
Test persistence after restart and include plugin-managed state in the backup. Before starting an isolated test copy, replace or disable its connections to live databases and webhooks.
Size hosting from the actual world
A long-lived building world and a short-wipe PvP server can produce different workloads at the same player count. Measure the world you intend to keep.
Use the Rust requirements worksheet for the save, population, plugin versions, server FPS and process memory. Check those measurements during the activities players care about. Investigate a stall with the lag runbook before assuming the allocation is too small.
Finding a PvE server to play on
Search the Rust browser’s pve tag or the server name, then read its damage and wipe rules. The label cannot tell you which plugin is installed or which damage paths are blocked. Facepunch browser tags
Look for a reporting channel and a schedule that fits your play time. Third-party lists can help you discover servers; verify the rules with the operator and through play.
Hosting on VYKIX
We provide file access, Oxide/Carbon workflows, scheduled maintenance and VxShield on VYKIX managed Rust hosting. Keep the compatibility and recovery tests when using a panel framework selector. The three same-server backup slots supplement your external backups.
The Rust trial lasts 48 hours and requires a valid card for fraud verification, with no trial charge or automatic paid subscription. Service is suspended at expiry, and active trial data is deleted seven calendar days after suspension. Export needed files before expiry. Continuing requires a separate paid order; trial hardware can differ from the paid configuration.
For a move, ask us to confirm eligibility, technical scope and terms before best-effort migration. Review Rust hosting or ask VYKIX about your plugin set with the versions and rules you need to preserve.
Game-aware DDoS protection for your server.
Run your game server with VxShield included. Ask about free migration and seven days free for eligible customers switching hosts. VYKIX confirms the scope, timing, and terms before the move.
Continue with
