Grim Anticheat Plugin FAQ

Check the console or your configured alert channel after players join and move around; Grim logs violations and flags as they happen. If you see nothing at all, confirm the plugin loaded without errors and that your alert permissions are set for your account.

Alerts are permission-gated, so your account likely lacks the alert permission node or the alert output is disabled in config. Also check that you're not filtering out the specific check or threshold that's triggering.

A violation is a recorded detection of suspicious behavior tied to a specific check; a punishment is an action you configure to fire once violations cross a threshold. Grim detects and reports, but you decide whether and how it punishes.

No, by default Grim focuses on detection and alerting rather than issuing punishments on its own. Automatic kicks or bans only happen if you explicitly configure punishment thresholds and commands.

Lag and packet loss can look like cheating, so tune your thresholds and use the setback/lenience options rather than disabling checks outright. Review the violation reports to see which checks are firing falsely before adjusting.

Grim is generally designed to coexist with most server plugins, but running two anticheats that both modify movement or combat can cause conflicts. If you see doubled flags or odd behavior, test with the other anticheat disabled first.

Grim is built to be lightweight and does most of its work per-player as packets arrive, so impact is usually minimal on typical servers. If you notice lag, check your alert verbosity and logging settings, which can add overhead.

Use a test account or a controlled client to perform the behavior and watch the console and alert channel for the corresponding check. This lets you confirm detection and tune thresholds before relying on it in production.

Cross-reference the reported check and timestamp with your server logs and the player's ping at that moment. If it's a false positive, adjust that check's threshold or lenience rather than removing the check entirely.

Grim works out of the box for detection, but alerts, punishments, and false-positive tuning all require configuration to match your server. Start by setting up alerts so you can see what's being flagged, then tune from there.