# Should your PvE Rust server add a dueling area or a combat weekend?

[Rust server guides](https://rustsc.com/learn/index.html.md) / [Players and community](https://rustsc.com/learn/community/index.html.md)

Choose the smallest area where the fight belongs. Use a dueling area when some players want a fight and others want to keep building. Consider a combat weekend when players actually want combat to change the whole world's routine.

## Decide what the player who sits out can do

Ask a builder, a fighter and a newcomer to describe their Saturday. A rule works when all three can say where they can play, what they risk and how to get back to ordinary PvE.

| Format | Player's way to opt out | What you must prove |
| --- | --- | --- |
| Keep PvE everywhere | Carry on with normal routes and play. | There is no temporary player combat exception. |
| Offer a dueling area | Stay outside the marked arena and keep ordinary access to roads, shops and home. | The entry, exit and both directions across the boundary behave as described. |
| Hold a combat weekend | Avoid the server or use any explicitly tested peaceful option. | The announced protections for homes, sleepers and loot hold during combat, and normal play returns at the end. |

## Try the arena against an ordinary route

Imagine Reedbank, whose players want fair duels beside the town in G8. The first proposed ring sits across the bridge that builders use to reach the recycler. Move the ring off the bridge or keep the event private. Putting a warning on the bridge still makes the arena a condition of the usual trip.

Put one ordinary account in the ring and another outside. Try an agreed test hit each way. Swap accounts and repeat after the fighter walks out and after a reconnect. If you use TruePVE with Zone Manager, check the mappings and any separate zone flags. A person standing inside a marked zone cannot establish how attacks crossing its edge behave. Record both directions separately. If only one direction protects the player outside, move the ring or keep it closed until both sides match the published rule.

## Put losses on the invitation

Describe gear and loot before choosing a format. For Reedbank's first event, use loose practice gear and leave ordinary inventories and homes out of it. Check what happens when someone drops a bag or disconnects. TruePVE deals with damage. Where you promise restrictions on looting, prove those separately.

A world-wide event needs a public start, a tested end and a way to close early. A post saying ‘PvE returns Sunday’ should also tell players whether event losses stay lost. If staff cannot describe that evening to a newcomer in one message, run the smaller event first.

## Make the opening decision

Read the proposed announcement to someone outside the crew and ask them to name the safe route, the loss they can take and the time when peace returns. If they can explain it and the corresponding ordinary-player tests pass, publish. Otherwise move the boundary, narrow the rules or keep the server PvE for this round.

## Sources

- [TruePVE: damage rules and zone integration](https://umod.org/plugins/true-pve)
- [Zone Manager: flags and zone settings](https://umod.org/plugins/zone-manager)

## Related resources

- [Run a PvP weekend on your PvE Rust server](https://rustsc.com/learn/community/weekend-pvp-on-a-pve-rust-server/index.html.md)
- [What should you check before advertising a Rust server as PvE?](https://rustsc.com/learn/configuration/check-what-pve-means-on-your-rust-server/index.html.md)

---

HTML version: https://rustsc.com/learn/community/choose-a-combat-format-for-a-pve-rust-server/
