Grim & Warden AC

Grim is the anticheat that does the detecting; Warden AC is the dashboard on top. This page explains what works out of the box, what you can change, and where the line between the two sits.

It works out of the box

Once Grim is installed, it starts working immediately, you don't have to configure anything to get detections. Grim runs a physics simulation of every player and raises a flag whenever someone does something the game shouldn't allow. Those flags show up in your server console and, with Warden AC installed alongside it, live in your dashboard.

So the honest short answer to "do my server owners need to customise Grim?" is: no, not to get started. The default jar detects and alerts on its own. Customising is optional, and it's about tuning sensitivity and deciding what happens when someone is caught.

What Warden AC does, and doesn't

Warden AC reads Grim's flags and gives you a place to see and act on them: a live feed, player history, a map, and one-click warns, kicks and bans across your network. It never changes Grim's detection and it doesn't touch Grim's own punishment settings. Grim keeps making the calls; Warden AC is the layer that makes those calls usable for your staff.

Two different kinds of punishment
There are two separate things that can ban a player. Grim's own autobans, configured in Grim's punishments.yml, happen automatically when someone trips a threshold. Warden AC's moderation is when you or your staff click warn/kick/ban in the dashboard. They can happily coexist, many networks lean on Warden AC for hands-on moderation and keep Grim's autobans light.

The thing most owners miss

Out of the box, Grim sees almost everything but doesn't automatically punisheverything. Several whole categories of cheats have no autoban set up by default, a player can flag over and over on things like flight, speed or knockback and simply sit in the alert feed forever without ever being banned by Grim itself.

That's not a bug; it's a deliberate, cautious default. But it means if an owner expects Grim to auto-ban blatant cheaters and it doesn't, this is usually why. You have two ways to handle it: moderate those players by hand from the Warden AC dashboard, or set up Grim's autobans so it acts on its own. The next two pages cover both.

Where to go next

Configuring Grim walks through Grim's config files and how to tune checks. Autobans & punishments shows how to make Grim ban on its own when a player crosses a threshold. Grim's own documentation is the source of truth for exact settings , it lives on the Grim GitHub and wiki.

Grim is separate software
Grim is free, open-source and maintained by its own team, not by Warden AC. We're not affiliated with it. These pages are a friendly starting point; for anything version-specific, always check the official Grim wiki.