DGuard — AI-powered Anticheat

DGuard is an anticheat for Minecraft servers of any genre: PvP and anarchy, survival, minigames. It learns from real cheaters — its combat model is trained on a live server with 500+ players online. Any new bypass gets closed within a couple of days, and support answers you directly.


50 cheat types. A check for every one


We checked every cheat type against the source code and documentation of five popular anticheats under the same rules: “partial” doesn't count. They cover 19 to 28 of these 50; DGuard covers all 50. The table with primary sources: dguard.site/en/compare.



Why DGuard

• Evidence from every front. Combat, movement, building and the world, inventory, packets: 11 checks and 80+ rules watch every player at once — hiding one cheat won't save them.
• Stealth mode. Hits land and small movement slips aren't set back, so the cheater has no idea they've been caught. Only the blatant is blocked: flying, teleports, hits far beyond reach.
• No snap bans. Every flag is evidence with a weight. By default a ban comes only once a player reaches 400 points across three separate episodes, and every ban gets a report: checks, evidence, ping, TPS and client version.
• You set the bar. Ban, kick, “only with a combat cheat” or “don't punish” — for each cheat feature. Test mode tells staff “would be banned” and bans no one.
• Packet order. We took Minecraft clients apart down to the packet: a legit client sends them in a strict order, a cheat breaks it — and gets caught, however human it pretends to be.
• No bans for useful mods. Hotbar binds, swapping in a weapon for the hit and hotbar refill mods produce no evidence. Gray-area features — AutoArmor, InvMove, AutoTool and others — aren't punished by default.
• Light. Checks run on network threads, and the heavy part — Golem and the deciding part of the rules — runs on DGuard's server. On a live server with 125 players that's about 1.5% of the main thread's work, with TPS at 20.

Golem — a combat neural network for PvP


Golem is DGuard's own AI combat model. It was trained on billions of gameplay data points collected through collaboration and testing with the most popular PvP servers, and today it's the strongest AI model in the anticheat space. A rule catches one impossible hit; Golem reads the whole fight, tick by tick — so neither smoothed aim nor “human-like” delays can fool it.

Golem keeps learning on fresh fights, and a new version ships only after passing an exam on fights it has never seen. It's part of DGuard on every plan, the free one included. How Golem works


Made for staff

• The /dg menu in game: checks, the punishment for each feature, strictness, test mode and every setting with its description. Ready profiles — PvP, survival, minigames — are one command away.
• Alerts with a click to teleport to the player, an evidence dossier and a report for every ban. /dg watch shows a live line about a suspect above the hotbar: ping, clicks, hit reach, misses and evidence.
• Web panel: the punishment log with reports and CSV export, access for moderators by email, Telegram alerts when a server goes silent.
• DGuard network: if DGuard has already banned a player on other servers, staff see it when they join. A hint, not evidence.
• Alts and bot farms: /dg alts finds accounts that share a client fingerprint. Bans and suspicions can go to Discord through a webhook.
• Server networks: one key per project, shared dossiers through MySQL, and DGuard-Velocity brings the alerts of every server into one chat.
• Two languages: menu, messages and config in English or Russian.

Compatibility

• Players: any client from 1.21–26.3 — all checked the same way.
• Server: Paper or Leaf 1.21.4–26.3, plus Folia. Every build is tested with cheating bots on 1.21.4, 1.21.8, 1.21.11, 26.2 and 26.3 and with a real Minecraft client running Meteor Client.
• Requirements: Java 21+ for 1.21.x and 25+ for 26.x, the latest PacketEvents release and HTTPS access to DGuard's site. Offline, the checks keep running for up to 72 hours; the cloud check and bans wait for the connection.
• Bedrock players (Geyser, Floodgate) aren't checked: Java rules would flag them falsely.

Setup in 2 minutes

1. Sign up and create a project in the panel — a name and an IP. You get a dg_… key, one for all the project's servers.
2. Put the latest PacketEvents release into plugins/ — the panel links to it.
3. Download DGuard.jar in the panel, put it there too and paste the key into plugins/DGuard/license.yml.
4. Restart the server: it shows up as “Online” in the panel. Check from the console with /dguard license. DGuard installs new versions itself on restart.

Pricing


Full protection on every plan — you only pay for player count. A week, a month or 3 months at 20% off, no auto-renewal.

• Starter — free, up to 30 online, 1 server, no time limit
• Mini — up to 60 online, 1 server — €9 a month
• Basic — up to 100 online, 2 servers — €19 a month (best choice)
• Pro — up to 200 online, 3 servers — €39 a month
• Business — up to 400 online, 5 servers — €79 a month
• Network — up to 800 online, 10 servers — €159 a month
• Enterprise — 800+ online, on request

FAQ

I already have an anticheat. Why switch?
Don't switch blind: run DGuard for free alongside your current anticheat in test mode and compare the logs after a week.

Does DGuard catch paid and private cheats?
DGuard doesn't look for client names — it looks for things vanilla Minecraft never does: impossible physics, out-of-order packets, hits outside the hitbox. So a new or private client gets caught by the same rules.

Where does player data go?
Nicknames, IPs, chat and dossiers stay on your server. The cloud check gets only gameplay measurements under random IDs — no nicknames, IPs or world coordinates.

What if a ban turns out to be wrong?
Send the ban report to support: we'll go through the fight tick by tick and fix the rule — for every server at once.



Questions and help with setup — on Telegram and through support on the site, even without an account.