Warden ACDocs

Autobans & punishments

How to make Grim act on its own, running a command like a kick or ban when a player crosses a violation threshold. This is Grim's punishments.yml, separate from moderating by hand in Warden AC.

The easy way: the Config wizard
The fastest route is the Config wizard in your dashboard, under the Grim section. Pick your Grim version, your server type and how strict you want it, choose whether flags should alert, auto-kick or auto-ban, and it generates a ready-to-paste punishments.yml. There's also a Punishments tab to fine-tune each category. The rest of this page explains how that file works if you'd like to understand or edit it yourself.

How punishments.yml is organised

Grim groups checks into categories. A category collects one or more checks together and defines what should happen at given violation levels, for example, alert staff every few violations, and run a command once violations pass a higher number. Because checks share a category, you tune a whole group of related detections in one place instead of per check.

Punishments are just commands Grim runs from console when a threshold is reached. That's the key idea: Grim doesn't have its own ban database, it fires a command, so you decide whether that's a vanilla ban, or a command from a punishment plugin like LiteBans, AdvancedBan or your network's own system.

Default Grim under-punishes on purpose
Out of the box, several whole categories only alert and never auto-ban, flight, speed, knockback and more can flag endlessly without Grim taking action. If you want Grim to ban on its own, you have to set these thresholds up yourself. If you'd rather handle it by hand, skip all this and moderate from the Warden AC dashboard instead.

Set up an autoban

1
Open punishments.yml
Find it in plugins/Grim/punishments.yml. Back it up before editing.
2
Pick or create a category
Group the checks you want to punish together under a category. Blatant movement cheats (fly, speed, motion) are a common one to start with.
3
Add alert and command thresholds
Decide when staff get alerted and when a command runs. A common shape is: alert every few violations, then ban once violations pass a higher number.
4
Use a real ban command
Point the command at whatever your server uses to ban. Grim runs it from console, with the player's name substituted in.
5
Reload and test
Run /grim reload (or restart), then verify on a test account that the command fires at the threshold you set.

Illustrative example

The exact syntax depends on your Grim version, so treat this as the shape of the idea rather than copy-paste config. It groups movement checks, alerts staff, and runs a ban command once violations pass a threshold:

punishments.yml (illustrative, verify against the Grim wiki)
Movement:
  checks:
    - "Simulation"
    - "Speed"
    - "Fly"
  # run these commands at the given violation counts
  commands:
    5:
      - "[alert]"          # notify staff in-game
    40:
      - "[webhook]"        # optional: fire a Discord webhook
    200:
      - "ban %player% Unfair advantage (Grim)"

Here %player% is replaced with the player's name. Swap the ban line for your punishment plugin's command if you use one (for example a tempban with a duration). Higher thresholds mean more certainty before a ban, at the cost of letting a cheater play a little longer first.

Let Warden AC carry the grey area
A nice setup: keep Grim's autobans for the truly blatant, high-certainty cases, and use the Warden AC dashboard for everything borderline, where a human should look at the context before deciding. That way you avoid false-ban complaints while still catching obvious cheaters automatically.

Discord alerts

Many setups also fire a Discord webhook on a punishment or alert threshold, so staff see activity in a channel. That's configured on Grim's side too. Remember it's independent of Warden AC, your dashboard already gives you the full live feed and history without needing webhooks.

Always confirm with the Grim wiki
Punishment syntax, placeholders and category behaviour differ between Grim versions. Before rolling autobans out on a live server, check the official Grim wiki for your version and test on a throwaway account first.
PreviousConfiguring GrimNextDashboard overview