FAQ and troubleshooting
Short answers to the most common questions: no flags or no suppression, the preset didn’t load, no holograms, out of requests, a false positive.
The plugin does nothing: no flags or no suppression on a player
Nine times out of ten it’s a bypass permission. mlsac.bypass takes the player out of every check. mlsac.suppression.bypass keeps the checks but turns off in-game suppression, and it’s also inside mlsac.admin, which operators get by default. A * wildcard in LuckPerms hands out all of them at once.
# what does the player actually have?lp user <nick> permission check mlsac.bypasslp user <nick> permission check mlsac.suppression.bypasslp user <nick> permission check mlsac.admin# take it away (false overrides groups and *)lp user <nick> permission set mlsac.bypass falselp user <nick> permission set mlsac.suppression.bypass false# or remove a node you set on the player by handlp user <nick> permission unset mlsac.suppression.bypass
Test on a normal account with no op and no *. If permissions look fine, go down this list:
- The API key is missing or wrong. Check
/mlsac statusand this case. - The preset hasn’t applied yet. After
/mlsac reloadit arrives about two seconds later; otherwise the server checks once a minute. - You’re out of requests for today, see the limit.
- The player is in a region or world with detection turned off. See Regions/Worlds.
- The player isn’t fighting another player. The model doesn’t judge hits on mobs, bots or thin air.
- It’s a fake player or an NPC. The anticheat doesn’t check those at all, so test with a second real account.
- It was loaded with Plugman or
/reload. That isn’t supported; do a full server restart.
I saved the preset but nothing changed on the server
The server checks the site once a minute, so give it a moment. Need it right now? /mlsac reload, and the preset arrives about two seconds later with Applying preset in the console. No such line? Check /mlsac status: the preset should say “active”.
I don’t see holograms over players
- You need
mlsac.notify.alerts,mlsac.alertsormlsac.admin. - A tag only appears after the player’s first checks. To see it straight away, turn on “Show with no checks”.
- Bots and fake players get no tags because the anticheat doesn’t check them. Test with a real second account.
- Players in spectator have none, and holograms don’t run on Folia.
Checks stopped and the status says “request limit”
Your plan’s daily requests ran out, so checks pause until the next day (midnight, server time). To avoid that, turn on “Return to free” in the preset: requests then come from a free Beginner licence if your account has one. If you run out every day, you need a bigger plan.
I’m testing suppression on myself and nothing happens
You’re probably op. Operators have mlsac.admin, which includes mlsac.suppression.bypass, so damage, lag and tricks skip them. Use a normal account; more above. And if you’re testing thresholds, make sure “Buffer suppression” is on in the preset.
MLSAC punished an honest player
- 1Save the data
While they’re online:
/mlsac falsepositive restore <name>. The plugin saves their recent checks for us. - 2Open the dossier
See how many detections there were and on which model. One spike and dozens of checks over days look very different.
- 3Write to us
A support ticket with the name, time and server.
The dashboard says “never connected”
The key isn’t in, has a typo, or there was no /mlsac reload after adding it. Look in the console for Detection: off (API key …) or The backend refused the API key. If it says Cannot reach, your host is blocking outgoing HTTPS.
Does it load the server much?
No. The neural networks run in our cloud; the plugin just collects combat data and sends it. If the cloud is unreachable, the plugin moves to the backup address on its own and comes back later.
Does MLSAC catch fly, speed, scaffold?
No, MLSAC is about combat. For movement, run Grim alongside; they don’t clash. More in Compatibility.
