Minecraft anticheat guide
Combat Anticheat for Crystal PvP Servers
What Crystal PvP owners should watch around AutoTotem, inventory speed, hitbox, reach, and elytra combat.
Crystal PvP compresses every abuse channel at once
Crystal combat stacks totem saves, rapid inventory swaps, precise aim under explosion knockback, reach disputes in close quarters, and Elytra repositioning between exchanges. Unlike steady SMP skirmishes, the entire abuse surface fires within seconds and repeats every round.
Review must therefore be multi-channel from the start: totem sequences, inventory chains, hitbox geometry, and movement context read as one fight rather than as isolated flags.
Totem, inventory, and combat read as one sequence
The decisive evidence is the combined timeline: totem-pop moments against refill packet order, swap chains against interaction plausibility, and hit plausibility against eye-to-hitbox distance with occlusion in crystal-damaged terrain. Terrain that changes mid-fight makes occlusion context especially important.
FairPlay includes checks for AutoTotem sequences, inventory interactions, hitbox and reach, and Elytra combat. Test crystal PvP scenarios with your server settings before enabling enforcement.
Staging crystal review without copying SMP playbooks
SMP baselines built on slow skirmishes mislead here. Collect samples from genuine crystal regulars at the server's latency spread, label their refill and swap speed floor explicitly, and keep checks alert-only until that floor is stable.
Escalate on corroborated multi-channel patterns across rounds, preserve the combined timeline for appeals, and re-baseline whenever crystal mechanics or related plugins change.
FAQ
How is this different from general SMP protection?
Crystal fights compress totem, inventory, aim, and geometry abuse into seconds-long rounds, so review must be multi-channel and staged on crystal scenarios specifically.
What evidence matters most in a crystal appeal?
The combined timeline: pop moments, refill packet order, swap plausibility, hit geometry with occlusion, and latency context.