| Name | Modified | Size | Downloads / Week |
|---|---|---|---|
| Parent folder | |||
| GriefPrevention3D.jar | 2026-07-02 | 933.2 kB | |
| README.md | 2026-07-02 | 3.1 kB | |
| v18.2.2_ add configurable per-claim PvP toggles source code.tar.gz | 2026-07-02 | 645.4 kB | |
| v18.2.2_ add configurable per-claim PvP toggles source code.zip | 2026-07-02 | 829.7 kB | |
| Totals: 4 Items | 2.4 MB | 1 | |
GriefPrevention3D v18.2.2
Wiki: https://github.com/castledking/GriefPrevention3D/wiki
Features
PvP can now be toggled per claim and subdivision
Added a new /claim pvp command that allows claim owners to enable or disable PvP inside their claims. The command works in both top-level claims and subdivisions, allowing different PvP rules for individual subdivisions if desired.
:::text
/claim pvp <true|false> confirm
A standalone alias is also available:
:::text
/claimpvp <true|false> confirm
Like /abandonclaim, the command requires a confirm suffix before making any changes.
Configurable claim and subdivision support
PvP toggling is disabled by default and can be enabled independently for main claims and subdivisions.
:::yaml
Claims:
PvPToggle:
Claim:
Enabled: true
Price: 0.0
Subdivision:
Enabled: true
Price: 0.0
DefaultState: INHERIT
Each scope has its own configurable economy cost, allowing servers to charge different prices (or no price at all) for claim and subdivision PvP changes.
Subdivision inheritance
New subdivisions can either inherit their parent claim's current PvP state or always use a configured default.
INHERIT (default)
- New subdivisions copy the parent claim's current PvP state.
- Existing subdivisions are unaffected if the parent is changed later.
DEFAULT
- Every new subdivision starts with the configured default PvP state regardless of its parent.
Economy integration
If a toggle price greater than 0 is configured:
- Requires Vault and a supported economy plugin.
- Players must have enough money before confirming.
- Payment is only taken after confirmation.
- Clear error messages are shown if payment fails.
Persistence
The PvP state is persisted across server restarts in both flatfile and database storage.
Alias system support
The /claim pvp subcommand is fully integrated with the alias system:
- Available as
/claim pvpthrough the unified command handler - Standalone
/claimpvpcommand can be disabled viastandalone: falsein alias.yml - Tab completion support for
true/falsearguments
Technical changes
- Added
Claim.pvpEnabledfield to store per-claim PvP state (default:true) - Added configurable PvP toggle settings under
Claims.PvPTogglein config.yml - Added
handlePvpCommand()for unified command handling - Registered
/claim pvpsubcommand in the unified command handler - Added standalone
/claimpvpcommand in plugin.yml - Added Vault economy integration with balance checks and withdrawals
- Added
pvpenabledcolumn to database schema (schema version 10) - Added
PvP Enabledkey to flatfile YAML serialization - Added pvpEnabled loading in both flatfile and database storage
- Updated alias.yml with
/claim pvpsubcommand and/claimpvpstandalone - Added "merge" option to
/claim modein alias.yml documentation - Updated wiki documentation (Commands.md, Key-Features.md, Configuration.md)