Rust is built around PvP, but not every server needs to revolve around raiding other players. PvE servers can put the focus on building, progression, monuments, NPCs, events, and playing alongside a community without constantly worrying about another player destroying your base.

There are two main ways to turn a Rust server into a PvE server. You can use Rust's built-in PvE setting for a quick setup or install TruePVE for much more control over who and what can deal damage. This guide covers both options and explains how to configure TruePVE whether you are self-hosting or using a game server host.

What Is A Rust PvE Server?

A Rust PvE server disables or restricts combat between players while keeping most of the rest of Rust's survival gameplay intact. Players can build bases, explore monuments, gather resources, fight animals and NPCs, and take part in server events without normal open-world PvP.

PvE does not necessarily mean removing all danger. Scientists, animals, the Patrol Helicopter, Bradley APC, traps, and other parts of the environment can still be threats depending on how your server is configured.

Server owners can also take the idea much further by protecting bases, changing turret behavior, creating PvP zones, or scheduling certain periods where PvP is enabled.

Vanilla PvE Vs TruePVE

Rust includes a built-in PvE setting using the server.pve server variable. Enabling it is the quickest way to disable normal PvP and will also automatically give the server the PvE tag in Rust's server browser.

The downside is that vanilla PvE gives server owners very little control over how damage is handled. It can also create some unusual damage interactions. For example, Rust's default PvE behavior can cause damage to be reflected back onto players in certain situations.

For a simple private server, vanilla PvE may be enough. For a public community, TruePVE is generally much more useful because it allows you to control damage using specific rules and RuleSets.

TruePVE can determine whether players can damage other players, buildings, NPCs, vehicles, traps, turrets, and many other entities independently.

How To Enable Vanilla PvE On A Rust Server

If you only want basic PvE, you do not need any plugins.

On a self-hosted server, open your server.cfg file and add:

server.pve true

Save the file and restart the server. You can also change the value through your server console, although adding it to server.cfg ensures that the setting is applied whenever the server starts.

If your server is hosted with Pine Hosting, you can enable the same setting without manually editing the configuration file. Open the Easy Config tab, enable Server PVE, save the changes, and restart your server.

If you later decide to use TruePVE, disable this setting again. TruePVE is designed to handle PvE damage rules itself and should be used with:

server.pve false

Running TruePVE while Rust's vanilla PvE system is also enabled can lead to unintended damage behavior.

How To Install TruePVE On A Rust Server (Self-Hosting & Pine Hosting)

Before installing TruePVE, your server needs a plugin framework such as Oxide/uMod.

If you are self-hosting, install Oxide for your Rust server and then download the current TruePVE plugin. Place the TruePVE.cs file inside your server's oxide/plugins directory. Once the plugin loads, it will automatically create the files needed for configuration.

The process is easier if you are using Pine Hosting. Select Oxide as your framework from the Startup tab, restart the server, and then open the Plugins page. Search for TruePVE and install it directly onto your server. You do not need to manually download or upload the plugin file.

Once TruePVE is installed, the rest of the configuration process is essentially the same regardless of where the Rust server is hosted.

How To Configure TruePVE

TruePVE creates its main configuration file at:

oxide/config/TruePVE.json

Before making large changes, creating a backup of this file is a good idea.

TruePVE works using RuleSets. A RuleSet determines which types of entities are allowed to damage one another. The default RuleSet generated by TruePVE is already designed around PvE, so most server owners do not need to create an entirely new configuration from scratch.

One of the most important settings is:

defaultAllowDamage

For a PvE RuleSet, this should be set to false. This means damage is blocked unless another rule specifically allows it.

Rules then create exceptions. For example, a PvE configuration can allow the environment and NPCs to damage players while specifically preventing players from damaging each other.

A core PvE rule is:

players cannot hurt players

Other rules can allow damage to NPCs, resources, helicopters, traps, and other parts of the game. TruePVE processes more specific rules before broader ones, allowing you to build surprisingly detailed damage systems.

After editing the configuration, save the file and reload TruePVE from your server console by typing:

oxide.reload TruePVE

Restarting the server will also load your changes.

For a standard PvE community, the goal is usually to prevent player-versus-player damage and unauthorized base destruction while allowing normal Rust progression to continue.

Your default RuleSet should therefore keep defaultAllowDamage set to false and retain the rule preventing players from damaging other players. From there, you can allow damage involving NPCs, animals, resources, helicopters, barricades, and other entities that are part of regular PvE gameplay.

TruePVE also includes flags for more specific behavior. For example, you can decide whether players can damage themselves, whether certain turrets target players, whether sleepers receive additional protection, or how ownership affects damage to structures.

It is better to modify the configuration generated by your current version of TruePVE instead of copying an entire configuration from an old guide. The plugin receives updates as Rust changes, so older configurations may contain outdated entities, flags, or rules.

TruePVE also does not control every part of Rust. For example, decay and looting are separate from its standard damage rules. If you want a PvE server where players also cannot access other players' containers or bodies, additional configuration or plugins may be required.

How To Allow PvP In Specific Areas

A PvE server does not have to be completely free of PvP.

TruePVE can work with ZoneManager to apply different RuleSets to specific areas of your map. This makes it possible to run a mostly PvE server while allowing PvP at selected monuments, arenas, events, or other custom zones.

To do this, enable zone support in TruePVE and create a separate PvP RuleSet. The ZoneManager zone ID can then be mapped to that RuleSet inside the TruePVE configuration.

You can also map a zone to exclude, which tells TruePVE not to process damage there and lets Rust use its normal damage behavior instead.

Be careful with exclusion zones around player structures. Returning completely to default Rust damage can also allow building damage. If you want players to fight each other while keeping nearby bases protected, creating a dedicated PvP RuleSet is usually safer than simply excluding the area.

Testing Your Rust PvE Server

Always test your PvE configuration before opening the server to a larger community.

Try damaging another player, a player-owned structure, an NPC, an animal, and several common vehicles or deployables. You should also test turrets, traps, sleeping players, and any custom PvP zones you have created.

If damage is not behaving as expected, TruePVE includes the tpve.trace command. Tracing records how TruePVE evaluated a damage event, including which entity groups and RuleSet were used. The trace automatically disables after a short period to prevent unnecessary log growth.

Testing is especially important after installing additional plugins, as another plugin may also modify damage and override the behavior you expected from TruePVE.

Run Your Rust PvE Community With Pine Hosting

Building the rules is only part of running a successful PvE Rust server. As your community grows, you also need to manage plugins, configuration files, updates, restarts, and server performance.

With our Rust hosting, you can install plugins such as TruePVE directly from the control panel, manage server settings through Easy Config, edit files, and access your console without having to manage the underlying server manually.

That gives you more time to focus on the parts that actually make a PvE community enjoyable: creating events, improving your rules, adding new content, and giving players a server they want to return to.