MonumentChoice

MonumentChoice is for PvE servers that allows eligible players to temporarily choose whether a monument should operate as a PvE or PvP area while they are inside it.

The plugin is designed for PvE servers that want dynamic, player-driven PvP areas at monuments without permanently configured PvP zones.

Description

When a player with permission enters an unclaimed monument, a UI window appears. The player can choose whether the monument should be set to PvE or PvP for the current occupation.

The selected mode stays active as long as the claiming player remains inside the monument. Once that player leaves, the monument is reset and becomes available again after the configured cooldown logic.

Other players inside the same monument are notified about the currently active mode.

Features

• Dynamic PvE/PvP selection per monument
• UI selection when entering an unclaimed monument
• Runtime PvE and PvP mode per monument
• Automatic reset when the claiming player leaves the monument
• Cooldown system to prevent immediate re-claiming
• Traveler option for players who do not want to claim a monument
• Separate traveler cooldown
• Configurable monument blacklist
• Automatic monument detection using Rust monument data
• Support for duplicate monuments on the same map
• PvP damage only between players inside the same PvP monument
• Teleport blocking inside active PvP monuments
• Bypass permission for admins or special roles
• English and German language messages
• Optional MyNotify support

Permissions

The plugin registers the following permissions:

monumentchoice.use

Allows players to use the MonumentChoice system. Only players with this permission receive the selection UI when entering an unclaimed monument.

monumentchoice.bypass

Bypass permission. Players with this permission are ignored by the MonumentChoice system. They do not receive the selection UI and are not restricted by the plugin's PvE/PvP checks.

Configuration

The configuration file is generated automatically at:

oxide/config/MonumentChoice.json

Dependencies

Optional

MyNotify

MyNotify is only required if this configuration option is enabled:

"UseMyNotify": true

If UseMyNotify is set to false, the plugin works without MyNotify.

Public API

Other plugins can call the following methods:

IsPlayerInPvPZone(BasePlayer player)

Returns true if the player is currently inside a monument that is set to PvP.

GetPlayerMonumentMode(BasePlayer player)

Returns the current mode of the player's monument:

Unclaimed
PvE
PvP

How It Works

1. A player enters a registered monument.
2. If the monument is unclaimed, the selection UI appears.
3. The player chooses one of the following options:
   • PvE
   • PvP
   • Traveler
4. If PvE or PvP is selected, the player becomes the owner of the monument state.
5. Players inside the monument are notified.
6. When the owner leaves the monument, the monument is reset.
7. The owner receives a cooldown for that monument.

PvP Logic

PvP damage is only allowed when all of the following conditions are true:

• the attacker and victim are inside the same monument
• that monument is currently set to PvP
• neither player has the bypass permission

Outside an active PvP monument, MonumentChoice does not actively allow PvP damage.

Teleport Blocking

When a player is inside an active PvP monument, the plugin blocks teleport attempts through the following hook:

CanTeleport(BasePlayer player)

This prevents players from escaping an active PvP monument by teleporting away.

Notes

• MonumentChoice stores monument states only at runtime.
• After a server restart or plugin reload, all monuments are unclaimed again.
• A selected mode remains active only while the claiming player stays inside the monument.
• Blacklisted monuments are ignored during server initialization.
• The plugin uses a 1-second position timer to detect monument entry and exit.

Known Limitations

• Monument states are not persistent.
• There are currently no admin commands to manually reset specific monuments.
• UI text is currently hardcoded in the plugin.
• PvP/PvE behavior may depend on how other damage or PvE plugins handle CanEntityTakeDamage.