Skip to main content

Run a PvP weekend on your PvE Rust server

A PvP weekend needs a working finish as much as a working start. Rehearse both on a separate server before inviting your PvE community to fight, and decide whether homes, sleepers and loot will stay protected.

Give the weekend one clear set of rules

Imagine Meadow, an established PvE community using TruePVE. Its first combat weekend runs from Friday at 18:00 to Sunday at 20:00. The server's clock is UTC. Players may fight across the world, but raiding homes and stealing remain against the rules. Existing damage and looting protections must support that promise. There is no new protected-town exception to explain at the boundary.

Write that short description before changing the server. If your players want an arena while peaceful building continues elsewhere, use an arena setup instead: the global schedule below changes the whole world's rules. Agree what happens to event loot and destroyed items too. In this example, normal progress carries on after the event; putting protections back does not rebuild anything lost during combat.

Prepare Meadow's rehearsal copy

Use a separate Rust server with its own ports, identity and compatible framework. Copy the community's relevant plugin settings and keep live Discord announcements and other live integrations off. Save the normal TruePVE configuration, its data and any zone or looting-plugin settings before making an event copy. Give the test players disposable gear and build a small test home.

This example assumes TruePVE already provides your normal protection with server.pve false, as its documentation requires. Keep damage handling on. Clone the working normal ruleset into a ruleset named weekend. If its player rule is players cannot hurt players, replace that rule with players can hurt players in the event copy. Retain its building and locked-door protection, and keep defaultAllowDamage false. Flags can override ordinary rules, so verify the result rather than treating that one edit as a complete configuration. TruePVE does not manage looting; retain and test your existing looting plugin's protection.

Set a start and a return to normal

In TruePVE's Schedule, set enabled, useRealtime and broadcast to true. Replace the entries in the event copy with the two lines below. Meadow runs on UTC. Friday is day 5 and Sunday is day 0. Replace default if your normal ruleset has a different name.

For the first rehearsal, move the two entries to upcoming times a few minutes apart on the test server. Reload the plugin using your framework's plugin controls and watch the console for successful loading. Check the current rules before the start, during the event and after the end. Schedule selection can take a short time to appear; use the observed change and the player checks before announcing that combat is open or closed.

Let TruePVE own these two transitions in this example. If another tool already swaps the same configuration or schedules combat, turn off its competing event changes for the rehearsal and planned event. Keep the saved normal configuration ready for an early finish.

Set a start and a return to normal
Meadow timeSchedule entry
Friday at 18:00 UTC5.18:00 weekend Weekend rules switched. Wait for staff to open combat.
Sunday at 20:00 UTC0.20:00 default Combat is closed. Staff are checking the return to PvE.

Try to break the promise before players do

Have two ordinary player accounts run the following checks before, during and after the short event. Use accounts without administrator powers or protection bypasses. Record the actual result beside the expected one. Test an unrelated player against the small home so ownership or team membership cannot make the check look safer than it is.

Existing zone mappings need particular attention. In our separate TruePVE rehearsal, two synthetic locations inside the same mapped town selected the town's normal rules during the event. With only one side inside, the resolver selected the global event rules. That was a rule-selection test, not a shot fired across a real boundary. Test both directions with your actual zones before promising a sanctuary; keep combat closed if the promise fails.

Try to break the promise before players do
CheckExpected outcome
Two unrelated players exchange a shot in the openPlayer damage is blocked before the event, allowed during it and blocked after it.
A visitor attacks the test home's wall and locked doorThe home stays protected before, during and after combat.
A player disconnects; the other attacks their sleeperNormal protection before and after; the exact announced sleeper rule during combat.
A visitor tries a test box and another player's dropped bagThe looting plugin enforces the promised no-stealing protection, including during combat.
Players stand together in each existing mapped zone, then shoot across its edge in both directionsEach direction matches the published boundary during combat, with normal protection restored afterward.

Announce the rules you just proved

Replace the dates in this example before posting it: ‘Meadow combat weekend runs Friday [date], 18:00 UTC to Sunday [date], 20:00 UTC. PvP is allowed across the world once we confirm it is open. Homes and loot stay protected. No raiding or stealing. Event losses stay lost; there is no world rollback at the end. We will confirm the return to PvE here and in game.’ Add the sleeper rule you actually tested and a place to report a problem.

Post the same boundaries in Discord and in the game's event messages. Before the start, remind players what they should carry and where to read the full rules. Have a helper watch for protection problems during the opening. If the rehearsal exposed an exception you cannot explain and support, change the event's scope before publishing the invitation.

Restore peace and close the event

At the end, watch the normal rules return and have the same two players repeat the open-world shot and home-protection checks. Verify the looting and sleeper protections you promised too. Publish ‘PvE is back’ after those checks agree. If a protection fails during the event, end combat early: restore the saved normal plugin settings, reload the affected plugins and repeat the checks before reopening peaceful play.

For a one-off weekend, put the saved normal configuration back after the scheduled finish and reload it. Check that it contains no enabled event schedule, then verify normal protection once more. The example entries repeat weekly if left enabled. Leave a short staff note with the closing result and any player issue still needing a reply; returning to PvE does not restore lost gear or undo damage.

What our rehearsal can establish

Our disposable Debian test with TruePVE 2.4.8 selected normal, event and normal rules again on a shortened schedule. The event copy kept the same damage rules, so that run verifies switching only. Two players still need to test damage, sleepers, looting and real zone boundaries on your own rehearsal server.

Sources

Analytics settings

Analytics are off.

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