Minecraft anticheat guide
Custom Enchantments and Anticheat Alerts on Minecraft Servers
Map each custom enchantment effect to the anticheat checks it can trigger, then test every enchant on staging before you change exemptions or thresholds.
Short answer
Custom enchantments can add knockback, movement speed, extra damage, or faster block breaking, effects that vanilla enchantments never produce. An anticheat tuned for vanilla behavior may alert on them. Copy each enchantment's effects from its plugin configuration, match every effect to the check it could trigger, and test each effect on staging before you adjust anything.
Why custom enchants look like cheats
A vanilla enchantment has known, fixed effects. A custom enchantment can change any number the plugin exposes, including how far a target is pushed, how fast a player moves, or how quickly a block breaks. Each change is a legitimate server rule, but a check built around vanilla values reads the result as something a player should not be able to do.
The risk grows with the number of enchants. Two enchants that are each harmless alone can combine on one item, for example extra knockback on a weapon that also carries a speed effect. Test combinations that players can actually obtain, not only each enchant in isolation.
Map each enchant effect to a check
The table groups common effect types with the check family that may react. Fill it in from your own plugin's configuration. The test column describes what to repeat on staging. It is not a measured result from any enchant plugin.
| Enchant effect | Check that may react | Staging test |
|---|---|---|
| Extra knockback on hit | Knockback or velocity checks | Hit a target with and without the enchant and compare its response |
| Movement speed boost | Speed or movement checks | Walk a fixed straight line with and without the enchant and compare timing |
| Extra damage on hit | Damage or hit-validation checks | Hit a dummy target ten times and compare the damage each hit deals |
| Faster or area block breaking | Fast-break or nuker checks | Break a fixed block set with and without the enchant and log alerts |
| Reduced fall damage or extra jump height | Fly or no-fall checks | Jump and fall from a marked height and log every alert |
Run the enchant audit
Keep the mapping in a shared document, so the next staff member can see which test produced which result. Update the document whenever you add or change an enchant. Record the plugin version next to each row as well. Plugins sometimes change effect values between releases, so an alert that starts after an update may come from a changed number rather than new player behavior.
Explain results to staff
When you hand the mapping to staff, include one example alert for each effect and the expected result from the staging test. Staff can then tell an expected alert from an unexpected one without rerunning the test. Keep each example short and tie it to the log entry it describes.
Avoid exemptions that trust an enchant name
An exemption keyed to an enchant name trusts whatever item carries that name. Players can receive enchanted items through drops, trades, shops, or staff commands, so the exemption applies to anyone who gets the item. A narrower change, such as tuning the single check that alerted, keeps the rest of the detection in place.
If the alerts point to a single enchant, review that plugin's effect values before changing the anticheat. A value set higher than you intended may be the real cause, and a fix there can be simpler than an exemption.
What we have not verified
We have not tested any custom enchantment plugin against any anticheat. Effects vary between plugins and versions, so use the plugin's configuration as the source of truth and your staging run as the evidence for your server.
FAQ
Does a knockback enchant always cause an alert?
No. It depends on whether your knockback checks compare against vanilla values and how wide their tolerance is. Run the staging hit test to see what your setup does.
Which enchants need the movement test?
Test every enchant that changes movement, damage, knockback, or block breaking. An enchant that only changes item text or sound does not need the movement test, though one logged run costs little.
Can alert history point to an enchant problem?
Yes, if your logs record the item the player held. A cluster of alerts around one enchant suggests a configuration issue rather than a single player. If the logs do not record the item, add that detail before drawing conclusions.
Do new enchanted items need a new test?
Yes. A new item that carries a custom enchant brings the same effects with it. Add its effects to the mapping and run the staging test before you release the item to players.