PvP Protections
ConsentPVP enforces mutual consent: a harmful interaction between players only succeeds when both the attacker and the defender have PvP consent enabled. If either player has PvP disabled, the attack or harmful interaction is blocked.
Crucially, ConsentPVP doesn't just stop melee swings — it blocks a wide range of direct and indirect PvP so players can't route around consent with projectiles, explosives, or environmental tricks.
Protected Interactions
| Interaction | Blocked when consent isn't mutual |
|---|---|
| Melee attacks | Direct player melee attacks. |
| Projectiles | Projectile attacks fired by players. |
| TNT | TNT damage where the source is a player. |
| End crystals | End crystal damage when the crystal's owner is tracked. |
| Splash potions | Harmful splash potion effects. |
| Lingering potions | Lingering potion / area effect cloud effects. |
| Explosions | Explosion damage to players who have PvP disabled. |
| Player-placed lava | Lava damage caused by player-placed lava. |
| Player-placed fire | Fire damage from player-placed fire, or spread fire linked to player-placed fire. |
| Respawn anchors | Interactions where a player tries to charge/use an anchor placed by someone else. |
| Knockback / push | Knockback or push effects from direct attacks and player-fired projectiles, including wind-charge–style push events. |
| Sweep / mace AoE | Sweep attacks and mace-style area-of-effect sweep damage. |
| Explosive minecarts | Anonymous or unknown explosive minecart damage is blocked if the defender has PvP disabled. |
Anonymous & Unknown Sources
Some damage sources can't be attributed to a specific tracked player (for example, certain explosive minecart damage). When the source is anonymous or unknown, ConsentPVP still protects a defender who has PvP disabled, and uses the *_anonymous message variants so feedback stays clear.
Vanished Attackers
Attacks from vanished players are silently blocked. ConsentPVP checks Bukkit's hidePlayer state along with common "vanished" metadata, so a hidden staff member can't accidentally (or intentionally) damage players who haven't consented — and the target isn't tipped off by a denial message.
Because protection is mutual, the most common reason a hit is blocked is simply that one of the two players hasn't run /pvp enable. See Troubleshooting.