The strongest starting point for a Rust PvE server is a documented uMod/Oxide or Carbon plugin loader with TruePVE as the damage-control layer. Configure TruePVE before adding convenience or economy features, then add only the plugins your players will use: progression and economy tools, clans, backpacks, teleportation, events and carefully chosen quality-of-life systems. This approach prevents accidental player damage while keeping maintenance and server overhead under control.
For the hosting layer, Godlike.Host provides Rust game-server hosting through its own game panel, with SFTP/FTP access and up to three free backups a day with restore.
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
Rust Key Cards, Rust Red Key Card, Cobalt Restricted Access Cards, Rust Gift For Gamers, Blue Key... | $25.00 | Buy on Amazon |
| 2 |
|
Rust Video Game Notebook | $15.00 | Buy on Amazon |
| 3 |
|
Rust Game Props Large Furnace (S) | $14.99 | Buy on Amazon |
As an Amazon Associate I earn from qualifying purchases.
What a good Rust PvE mod stack must do
A PvE server is not simply a normal Rust server with player-versus-player damage switched off. Players can still damage allies, deployables, vehicles, NPCs, bases or loot if protection rules are incomplete. A useful stack therefore has to solve four separate problems:
- Protection: define who or what can damage players, buildings, deployables, NPCs, vehicles and containers.
- Progression: give players meaningful goals and ways to obtain or manage resources without turning the server into an unstructured sandbox.
- Administration: provide predictable permissions, understandable commands, logs and a recovery path when a rule or plugin behaves unexpectedly.
- Operations: remain compatible with the current Rust build and your selected loader while keeping configuration and update work manageable.
The best stack is consequently the smallest one that delivers the experience you want. Every additional plugin introduces configuration, permissions, possible conflicts and another component to test after a Rust update.
#1 Best Overall
- Inspired by the Rust Video Game – These cards replicate the iconic keycards found in Rust (Red, Blue, Green).
- High Quality PVC Plastic – Printed on both sides, durable and water-resistant. Not a sticker.
- Great Rust Gift Idea – Perfect for fans of Rust, whether for cosplay, loot-themed gifts, or collection.
- Wallet-Size Replica – Standard 3.375x2.125 inches, 30 mil thick—fits in any wallet.
- NOT a sticker*
Core choice: uMod/Oxide or Carbon
Rust server plugins run through a server-side loader. uMod/Oxide is the established workflow described by uMod and Oxide documentation: plugins are self-contained code packages that alter server behavior, usually create JSON configuration or data files, expose permissions and offer console or chat commands. Carbon is an alternative loader used for Rust plugin hosting. Choose one loader for a server and install plugins built and maintained for that loader; do not assume a package made for one environment will work unchanged in the other.
| Decision | What to verify before installation |
|---|---|
| Loader | Whether the plugin explicitly supports your current uMod/Oxide or Carbon installation and Rust build. |
| Configuration | Where the plugin writes JSON, data and localization files, and which settings require a reload or restart. |
| Permissions | The plugin’s permission strings, default groups and whether permissions can be inherited safely. |
| Commands | The documented console and chat commands, required access level and expected output. |
| Updates | How the author announces compatibility changes and what happens to existing configuration during an update. |
Keep a copy of the loader version, Rust build and every plugin version in your change log. When a server update causes a problem, that record lets you identify the last changed component instead of guessing.
TruePVE: the protection layer to install first
TruePVE is the clearest documented candidate for controlling damage on a PvE Rust server. It is designed as a Rust damage-control plugin and supports rulesets, schedules, entity groups, permissions and zone integration. Those controls matter because a single global “no PvP” switch cannot express every legitimate PvE rule.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesBuild a protection policy before touching settings
Write down the behavior you want in plain language. For example:
- Players cannot damage other players anywhere on the main map.
- Players can damage hostile NPCs and event enemies.
- Players cannot damage allied bases, doors, deployables, vehicles or stored loot.
- Administrators may test damage in a private maintenance area.
- A scheduled event zone can use different rules from the rest of the map.
Turn that policy into TruePVE rulesets rather than adding unrelated protection plugins. Test each category separately with two ordinary player accounts and, where relevant, an administrator account. A rule that protects players but not their deployables is not a complete PvE policy.
Use rulesets for different activities
Rulesets let a server distinguish normal survival from special activities. A main-world ruleset can block player damage while allowing damage to NPCs. An event ruleset can permit a defined encounter without opening the entire map to player attacks. A maintenance ruleset can be limited to an administrator-only zone and schedule.
Schedules are useful when the rule changes at a known time, such as a limited event window. Zone integration is useful when the rule changes by location. Entity groups are important when you need separate decisions for players, NPCs, vehicles, structures, deployables or loot. Permissions can restrict who is allowed to use an exception.
Free tools Windows power users keep installed
One-click scans. No signup required.
Test the edge cases players actually encounter
- Direct weapons and melee attacks between two non-admin players.
- Damage to doors, boxes, tool cupboards, turrets and other deployables owned by another player.
- Explosives, fire and other area effects near allied structures.
- Vehicles and mounted objects that can be damaged by players or environmental events.
- NPCs, event enemies and loot containers that should remain interactable.
- Teleporting into or out of a protected zone while an event or schedule is active.
Record the expected result and the observed result for every test. If a change produces an unexpected result, revert the last configuration edit before changing several settings at once.
A balanced plugin stack by player need
Install features in the order your players experience them. The following stack is a framework, not a requirement to install every category.
| Player need | Useful plugin category | Why it helps | Operational questions |
|---|---|---|---|
| Safe foundation | TruePVE | Controls damage through rulesets, schedules, entity groups, permissions and zones. | Are every protected entity and exception tested? |
| Early progression | Kits | Provides a controlled starting package or milestone rewards. | Are kit contents balanced and limited by permission or cooldown? |
| Trading and rewards | Economics | Creates a currency layer for shops, rewards or services. | How are balances stored, audited and recovered? |
| Social play | Clans | Groups players for cooperation and shared identity. | Do clan permissions overlap with TruePVE ownership rules? |
| Inventory management | Backpacks | Gives players extra storage without requiring more physical boxes. | What happens to backpack contents during wipes, deaths or plugin removal? |
| Travel | Teleportation and homes | Reduces long travel for cooperative building and events. | Are cooldowns, costs, combat restrictions and zone restrictions clear? |
| Replayable activity | Events | Adds scheduled or triggered objectives beyond ordinary farming. | Does each event have a protected area and an explicit cleanup plan? |
| Reduced friction | Quality-of-life tools | Improves routine inventory, building or information tasks. | Does the convenience remove a survival decision or create UI clutter? |
Progression and economy plugins
Kits
Kits are most useful when they solve a specific progression problem: a modest starter package, a milestone reward or an administrator-approved recovery kit. Keep contents consistent with the server’s intended difficulty. A starter kit that includes advanced weapons or excessive building materials can erase the early-game loop that makes a wipe interesting.
Use permissions and cooldowns so ordinary players receive only the intended kits. Document whether a kit is one-time, wipe-limited or repeatedly claimable. Test what happens when a player has a full inventory, disconnects during the claim, or loses the plugin’s data file.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallEconomics
An economics plugin is a shared currency service for shops, rewards and paid conveniences. Decide what creates currency and what removes it before opening a store. If rewards create money but nothing consumes it, prices quickly stop carrying meaning. Suitable sinks can include travel fees, event entry, cosmetic services or carefully priced supplies, provided those choices fit your server’s rules.
Rank #2
Protect the economy with least-privilege permissions. Separate the ability to view a balance from the ability to grant currency or alter prices. Keep periodic backups of currency data and define a response for duplicated, lost or corrupted balances.
Social, travel and inventory convenience
Clans
Clans make cooperative PvE easier to organize, but they do not automatically define ownership. Decide whether a clan member may access another member’s doors, containers or vehicles, and make that behavior consistent with your TruePVE rules. A clan system should not silently override the protection policy.
Set limits that match the server’s scale. Very large groups can make a cooperative server feel inaccessible to solo players, while tiny limits can fragment a group that the server is designed to support. Explain how membership changes affect shared access before players commit resources to a base.
Backpacks
Backpacks reduce the number of storage boxes players need and make exploration more practical. They also change the value of death, travel and base security. Decide whether backpacks drop on death, remain with the owner, or follow a separate recovery rule. Players need to know the answer before carrying irreplaceable items into an event.
Check persistence across restarts, wipes and plugin updates. A backpack plugin that does not clearly document its data handling deserves a test server and a verified backup before production use.
Teleportation and homes
Teleportation and home systems are strong quality-of-life additions for PvE communities that spend time building or running events. Balance them with cooldowns, travel costs, combat restrictions and zone restrictions. Blocking teleport requests while a player is taking damage prevents many escape exploits; restricting use in event areas preserves the event’s intended risk.
Define whether homes survive a wipe, whether players can set homes inside protected event zones and what happens when a building is removed. Test teleports across the map, into blocked areas and during a server restart.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Events and quality-of-life features
Events
Events provide goals after players have established a base. Start with one event type and a clear reward loop rather than enabling several systems at once. For each event, specify its trigger, location, participants, enemies, reward, duration and cleanup behavior.
Connect event areas to an explicit TruePVE zone or ruleset. Verify that event enemies can be damaged while players remain protected from one another, and verify that event loot cannot be taken or destroyed by an unintended damage rule. Run an event with ordinary player permissions before announcing it publicly.
Quality-of-life systems
Quality-of-life plugins should remove repetitive friction without turning every survival choice into an automated action. Evaluate them against three questions:
- Does the feature save time players currently spend on an uninteresting task?
- Does it change resource scarcity, travel risk or building progression?
- Can a player understand, disable or recover from it without administrator help?
Add one convenience feature at a time. Players can then tell you whether it solves a real problem, and you can identify a conflict if an update breaks behavior.
Permissions: design groups before granting commands
Oxide’s permission system assigns plugin-specific permission strings to users or groups. Groups can inherit from parent groups, so a deliberate hierarchy is safer than granting administrator access whenever a plugin needs testing.
Rank #3
- Acrylic Painting Pla Plastic
| Group | Typical purpose | Access principle |
|---|---|---|
| Player | Normal survival and publicly available features. | Only the permissions required for ordinary play. |
| VIP | Optional donor or supporter conveniences, if your server uses them. | Feature-specific additions; never inherit moderation or data powers. |
| Moderator | Player support, investigation and limited event assistance. | Can inspect or resolve incidents without unrestricted configuration access. |
| Administrator | Configuration, maintenance and emergency recovery. | Restricted to trusted operators and protected by a documented change process. |
Review every plugin’s permission list before assigning it. A permission that sounds like a convenience command may also grant inventory, economy or configuration control. Test each group with a real account, not only with an administrator account, because administrators can hide missing permissions and protection mistakes.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Installation workflow for a new server
- Choose the loader. Select uMod/Oxide or Carbon based on the plugins you intend to run and confirm compatibility with the current Rust build.
- Prepare a test instance. Copy the server configuration and world or use a separate test server. Keep production players off the instance while rules are being validated.
- Install the loader and verify it starts. Confirm that the loader creates its expected directories and that the server reaches a normal ready state before adding gameplay plugins.
- Install TruePVE first. Restart or reload as required by its documentation, then inspect its generated configuration and data files before changing values.
- Configure the baseline ruleset. Implement the written policy for player, structure, deployable, NPC, vehicle and loot interactions. Add schedules or zones only after the global behavior is correct.
- Create permission groups. Establish player, VIP, moderator and administrator groups, then assign only the plugin-specific permissions each group needs.
- Test protection. Use at least two ordinary accounts to test direct damage, splash damage, structures, deployables, vehicles, NPCs, loot and event areas.
- Add one feature category. Install kits, economics, clans, backpacks, teleportation, events or a quality-of-life plugin individually. Read its configuration and permission documentation before enabling it.
- Test persistence. Restart the server, reconnect players and verify that inventories, balances, homes, clan membership and event state remain correct.
- Back up configuration and data. Store loader settings, plugin JSON, data files and permission information before opening the server to players.
- Document player-facing behavior. Publish available commands, cooldowns, restrictions, wipe behavior and support contacts in one accessible location.
- Repeat after every update. Update the loader and plugins in a controlled order, review errors, run the protection checklist and keep a rollback copy.
Performance, compatibility and maintenance
No independent benchmark establishes a universal player-count or performance limit for these plugins. The practical cost depends on the Rust build, map activity, event frequency, configuration and the number of systems running at once. Treat plugin count as an operational risk, not a performance score.
- Prefer maintained plugins with clear compatibility notes.
- Remove unused features instead of leaving them disabled but installed indefinitely.
- Watch server logs after installation and after Rust updates.
- Measure symptoms such as delayed commands, failed saves, entity buildup or unusually long restarts before blaming a single plugin.
- Keep event schedules, teleport restrictions and economy changes documented so another administrator can reproduce the setup.
When two plugins appear to affect the same action, isolate the conflict on the test instance. Disable one plugin, reproduce the symptom, then compare logs and configuration. Changing several plugins simultaneously destroys the evidence needed to find the cause.
Common failure modes and fixes
Players can still hurt one another
Check whether the attack occurred in a different zone or during a scheduled ruleset, whether the attacker has an exception permission, and whether the damage type is covered by the active entity rules. Reproduce the incident with two ordinary player accounts and record the exact location and weapon type.
Players are protected, but bases or deployables are not
Review structure and deployable entities separately from player entities. Area damage, fire and vehicles may follow different rules from direct attacks. Add a targeted test for each entity category instead of assuming a player-protection setting covers the entire base.
A plugin command reports missing permission
Confirm the exact plugin-specific permission string, the account’s group membership and any parent-group inheritance. Test with a normal account after assigning the permission; do not use an administrator account as proof that the permission model is correct.
Data disappears after a restart or update
Stop making configuration changes, preserve the affected files and compare them with the last backup. Check whether the plugin expects a reload, a full restart or a migration step. Restore only the affected data after confirming that the installed plugin version matches the backup format.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Players report lag after adding several plugins
Review the installation timeline and server logs, then disable the newest plugin on the test instance. Check event frequency, repeated timers, excessive entity creation and failed save operations. If the symptom disappears, reintroduce features one at a time and keep the feature that delivers the most player value for the least maintenance burden.
Server listing and policy requirements
Facepunch Studios’ current guidance states: “When using plugins with your Rust server you should be listed under the Modded section.” The same guidance says gameplay-modifying plugins and custom UI are not allowed in the Community section. A server using TruePVE, kits, economy, clans, teleportation, events or other gameplay-changing plugins should therefore use the Modded listing treatment and describe its rules honestly.
Make the listing match the live configuration. Tell players whether PvE protection applies globally, how event zones differ, which convenience systems are enabled and whether wipes affect kits, homes, balances or backpacks. Clear disclosure prevents players from joining with expectations based on an unmodified server.
A lean starting configuration
For a first wipe, start with TruePVE, one progression feature and one travel or inventory feature. A practical sequence is:
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →- TruePVE with a globally protected main map.
- A modest starter or milestone kit with a documented cooldown or claim limit.
- Either homes/teleportation or backpacks, depending on whether travel or storage is the larger complaint.
- Clans after you have confirmed how group membership interacts with base access.
- Economics and events once you have a tested reward, currency and cleanup plan.
This order gives players immediate safety and useful progression while leaving room to observe how the community actually plays. Add another system only when you can state its player benefit, permission model, backup plan and rollback procedure.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
