How to Set Up a Rust PvE Server in 2026
Agree on the damage rules before installing a PvE plugin. Decide whether players can hurt each other, attack sleepers or raid an empty base. If you want an arena or PvP monument, define where those rules change. You can then test those decisions before players risk their progress.
Rust provides native PvE behavior through server.pve. The setup below uses TruePVE to configure damage rules, leaving the native setting as its author requires. Include the environmental threats you want to keep in the tests as well as the player damage you want to block.
Start with one damage-control system
Section titled “Start with one damage-control system”Set the following value as required by TruePVE’s author documentation:
server.pve falseRust remains in native PvP mode while TruePVE handles damage using your rules. Read the release notes for the installed version and try the entities and damage types your group uses.
Install an Oxide or Carbon build supported by your plugins, taking a backup before installation or a framework change. For an alternative such as NextGenPVE, follow that author’s current documentation and framework requirements. Use multiple damage systems together only when their authors document the integration.
Configure and test TruePVE rules
Section titled “Configure and test TruePVE rules”Configure TruePVE’s RuleSets and point its Mappings at those RuleSets. Turn on damage handling with handleDamage. To apply rules by zone through ZoneManager, use useZones and check that each mapping points to a RuleSet you have defined.
Read authorization flags against the configuration your version generates. For an ownership-related flag, test whose structures it permits a player to damage before relying on it.
Use two non-admin accounts on an instance you can restore. Owner privileges can make a broken permission look as though it works.
| Test | Result to record |
|---|---|
| Player attacks another player | Check whether friendly fire matches your policy |
| Player attacks a sleeper | Confirm how offline players are protected |
| Damage to another player’s building | Check which raiding actions are allowed |
| Fire, explosives and vehicle contact | Test each damage path enabled on your server |
| NPC, animal and environmental damage | Confirm that the threats you want remain active |
| Restart after a configuration change | Verify the rules and player data after the restart |
If you use traps, turrets or content plugins, add their damage paths to the checks. Write down what happened, including any failure. If a protection rule fails, stop admitting players while you investigate and save the error details.
Add PvP areas only when the rules are clear
Section titled “Add PvP areas only when the rules are clear”You can apply different TruePVE RuleSets by area with ZoneManager. Agree with the group before adding a PvP arena or monument.
Make the boundary visible and explain which rules change there. Attack across it in both directions, checking projectiles, overlapping zones and sleepers. Repeat after restarting the server. Pay attention to exclusion mappings, which can restore Rust’s default damage behavior.
Check raid-content plugins for their own zone systems. They may use different rules or priorities from your ZoneManager configuration.
Tune gather rates and decay
Section titled “Tune gather rates and decay”Discuss progression with your players, then adjust one setting at a time. Keep an eye on world growth as you change gathering and decay; both influence the persistent data your server carries.
The Gather Manager plugin has separate controls for dispensers, pickups and quarries. Carbon offers an optional Gather Manager module. Select the system you will use and follow the commands for its current version.
If players spend too much of a session gathering, test 2x or 3x and compare it with your current rates. Ask the group how the changed progression feels before keeping the setting.
Check the live decay.scale value before editing it. Facepunch lists a default multiplier of 1. Reducing decay can leave more structures standing, so watch the save grow and tell players how you will handle cleanup. Console command reference
Publish the map and blueprint wipe policy alongside those settings. Explain what you plan to keep and that mandatory updates may require a reset.
Add content and convenience plugins by need
Section titled “Add content and convenience plugins by need”Pick additions around an activity your group wants:
| Task | Example to assess |
|---|---|
| Raid bases prepared for encounters | Raidable Bases |
| Give players extra inventory or starter equipment | Backpacks or Kits |
| Allow travel between agreed locations | NTeleportation |
| Let players remove permitted structures | Remover Tool |
| Add currency or rewards | Economics or ServerRewards |
Before installing a candidate, check its release, licence, dependencies and framework support. You can open the server with the plugins you need and add others as the group asks for them.
Raidable Bases requires CopyPaste and prepared base files. Supply those files yourself; the plugin does not generate them. Check the features in your edition before planning a raid event.
Restart after setup and check that plugin-managed data survives. Include that data in your backup. When you launch an isolated test copy, replace or disable its copied connections to live databases and webhooks first.
Size hosting from the actual world
Section titled “Size hosting from the actual world”A PvE world full of long-lived buildings can demand different resources from a PvP world that wipes after a short cycle, even with the same player count. Test the save you intend to keep.
Record the save, population, plugin versions, server FPS and process memory with the Rust requirements worksheet. Capture those readings while players use the features that matter to your group. If a session stalls, work through the lag runbook before buying a larger allocation.
Finding a PvE server to play on
Section titled “Finding a PvE server to play on”Search the browser for the pve tag or a server name. Read the operator’s damage and wipe rules to find out what the server permits; the tag does not identify its plugin or damage configuration. Facepunch browser tags
Check where you can report a problem and whether the schedule fits your play time. Use third-party lists to find candidates, then confirm their rules with the operator and during play.
Hosting on VYKIX
Section titled “Hosting on VYKIX”VYKIX managed Rust hosting provides game-file access, Oxide/Carbon workflows, maintenance schedules and VxShield. After installing a framework through the panel, test plugin compatibility and try your recovery procedure. Keep an external backup as well as the three same-server slots.
The Rust trial gives you 48 hours and requires a valid card for fraud verification. There is no trial charge or automatic paid subscription. Service is suspended at expiry, and active trial data is deleted seven calendar days after suspension. Export your needed files before expiry. Continuing requires a separate paid order, which can use a different hardware configuration from the trial.
For a move, confirm eligibility, technical scope and terms with us before best-effort migration. Review Rust hosting or ask VYKIX about your plugin set, including the versions and damage rules you need to retain.