Minecraft anticheat guide
Cheating Rules Page Wording for Minecraft Servers
Cheating rules page wording for Minecraft servers: define banned client mods, macros, and exploits, state enforcement, and avoid promising detection coverage.
What should a cheating rule say?
A cheating rule should name the behaviors you prohibit, define each one in plain words, describe the range of penalties, and link the appeal process. Keep detection claims out of the rule. A line that says 'we detect every cheat' is a promise you cannot keep, and players will test it.
Which behaviors need their own definition?
Group behaviors by what the player gains, not by the tool used. That keeps the rule useful when a new tool appears. The starting wording below is a draft for you to edit.
| Behavior | Starting rule wording | Note for staff |
|---|---|---|
| Client modifications | Using a client change that shows information or performs actions the normal game would not | List any allowed clients or mods by name, or say that none are allowed |
| Macros and automated clicking | Using scripts, macros, or devices that send clicks or key presses for you | Say which click-rate limits are rules and which are only enforced by a plugin |
| Visibility cheats | Using visibility of blocks, players, or entities the normal client would not show | Describe the behavior, not a specific cheat name |
| Exploits and duping | Using a bug to gain items, currency, or position in a way the server did not intend | State whether reported exploits are reset or rolled back |
How do you write the enforcement clause?
Describe the range of responses and the basis for choosing one. Players accept a clear range more readily than a fixed sentence that does not match what staff actually do.
3.2 Cheating
Using third-party software to gain an advantage in gameplay is not allowed. This includes <CATEGORY LIST>.
Penalties range from <WARNING> to <PERMANENT BAN> depending on the case.
Automated systems may flag activity. Staff review flagged activity before a final decision, except <EXCEPTION OR "NONE">.
Appeals: <APPEAL URL>, within <TIME LIMIT>.What should the rule leave out?
Some lines look helpful and cause problems later. Remove them before you publish the page.
How should the rule handle Bedrock players?
Write the rule around the behavior, not the input device. Bedrock players may use different controls, so a rule that refers to clicks or aim should not assume Java-only input. If your server accepts Bedrock players, add a line that says staff will review a case with the player's input method in mind.
How do you change the rule without confusing players?
Edit the rule text and the penalty ranges together. If a penalty changes, the rule should say so and give a date. Post a short note in the rules channel that names the section that changed, and keep the old version linked for players who were punished under it.
Avoid silent edits. A player who reads the rule last month and sees different wording today has no way to know which version applied to their case unless you say so.
Should the rules page link to examples?
Examples help players understand a category, but each example can become a loophole. Use one or two clear examples per category, mark them as examples rather than a full list, and say that staff decide each case on its facts. Do not publish screenshots of real cases, because they reveal player names and the evidence you used.
If a category is hard to explain in words, a short video or a staff-written walkthrough can help. Keep it on your own channel and date it, so it stays accurate after an update.
What have we not verified?
This wording is a starting point, and it has not been tested against your rule history or your staff process. Ask someone who did not write it to read it cold, check each penalty against your actual practice, and print a version date in the page footer.
FAQ
Should the rules list specific anticheat checks?
No. Name categories, not checks. Specific checks change with plugin updates, and a public list shows cheat authors which behaviors to adjust.
Can we ban all client mods?
Only if you can define the set. A blanket ban with no list is hard to enforce and hard to appeal. Name the allowed clients or mods, say that anything else is not allowed, and explain how a player can ask about a specific mod.
Does the rules page change how the anticheat behaves?
No. The page sets expectations and the basis for a punishment. Plugin settings control detection and actions. When you change one, check the other, so the rule and the behavior do not drift apart.
Do we need to mention macros if we already limit clicks?
Yes. A click limit is a technical setting, and a macro rule is a conduct rule. Players may break the conduct rule without triggering any limit, and staff need the written rule to act on that case.