# GriefPrevention3D v18.3.8
**Wiki:** https://github.com/castledking/GriefPrevention3D/wiki
## Overview
Fix for the per-claim PvP toggle: turning PvP **on** via `/claim pvp on confirm` (or the
equivalent) did not actually enable combat — players in the claim remained protected.
## Root cause
`claimIsPvPSafeZone` only honored the per-claim setting in one direction. When a claim's PvP
toggle was turned **off**, the method correctly returned a safe zone. But when it was turned
**on**, the method fell through to the global config fallback
(`PvP.ProtectPlayersInLandClaims`, etc.). On servers whose global config protected players in
claims (the common default), that fallback still reported the claim as a PvP safe zone —
so enabling PvP on an individual claim had no effect.
The fix also scopes the toggle by claim type. Previously the check keyed off an aggregate "is
either toggle enabled" flag, so enabling only the main-claim toggle would also make
subdivisions defer to their per-claim value, bypassing the global subdivision config.
## Fix
`claimIsPvPSafeZone` now:
- checks the per-claim toggle only for the claim type the server enabled it for (main claim vs
subdivision, mirroring `getPvpToggleContext` in the command handler);
- treats the claim's own `pvpEnabled` setting as authoritative in **both** directions when that
toggle is active — off protects, and on overrides the global "no combat in claims" fallback;
- otherwise falls back to the global config, preserving existing behavior on servers that never
opted into the per-claim toggle.
## Upgrade notes
No configuration, storage, or migration changes. Drop-in replacement for v18.3.7.
Optional dependencies
QuickShop-Hikari
Any compatible version
VaultUnlocked
Any compatible version
PlaceholderAPI
Any compatible version
Developer information
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle.
maven { name = "Modrinth"; url = "https://api.modrinth.com/maven" }
