PvP and raid protection
Hit registration
On a modern server a swing counts only when the client says it hit something. On 1.8 servers built for PvP, the server checked the swing itself, and hits at the edge of reach landed. That is the difference players describe as "hits not registering".
raid.rogue-hit.enabled- When the client swings without reporting a hit, the server traces the swing and applies the hit if a target was there. A block in the way cancels it, and spectators are ignored. This changes how PvP feels, so try it on a test world first.
raid.rogue-hit.max-distance- Reach of that check in blocks, measured from the attacker's eyes to the point of impact.
2.6matches 1.8 reach, which is 2.90 blocks between the two players. raid.rogue-hit.hitbox-leeway- How much the target's hitbox is grown for the check.
0.01matches 1.8.
Combat that survives a TPS dip
raid.pvp.time-based-hit-cooldown- The short invulnerability after a player is hit is counted in real time instead of ticks. When the server drops to 15 TPS during a raid, fights keep their rhythm.
Anti-freecam
Freecam clients let a player move the camera through walls and click what they see. Each of these settings refuses the action when a block sits between the player's eyes and the face they clicked.
| Setting | Refuses |
|---|---|
raid.anti-freecam.chests |
Opening a chest |
raid.anti-freecam.dispensers |
Opening a dispenser |
raid.anti-freecam.signs |
Using a sign |
raid.anti-freecam.spawn-eggs |
Placing a spawn egg |
They are separate switches because a server with shop signs behind glass may want three of the four.