Configuration Explanation
Detailed breakdown of every parameter in your config.yml.
Settings moved to the site
WorldGuard regions, models, alerts, violation buffers, penalties and responses are no longer edited in config.yml. Open Configs in the dashboard, create a preset and point the plugin at it:
remote-config: preset: "main" # имя пресета с сайта refresh-minutes: 5 # как часто проверять изменения
Until a preset is set and reachable the plugin runs on its built-in defaults. The blocks below explain what each group of settings controls.
Configs on the site
A preset is a named set of detection, alert, buffer and penalty settings stored in your account. One account can hold several; the preset field decides which one a given server loads. Presets are private — the plugin only reads those belonging to its API key owner and never writes anything back.
Changes are picked up automatically, without a restart. If the preset is missing, deleted, or the site is unreachable, the plugin keeps running on built-in values, so a bad edit cannot take your server down.
Player reports
Players complain with /report nick reason. The report lands in a queue staff open through /mlsac suspects on the Reports tab. Recent anticheat checks are attached to every report, so the decision is not made blind.
A claimed report is locked to one moderator: nobody else can enter until it is closed or left idle for 30 minutes. From the menu you can teleport to the player in spectator mode, disable their damage, or close the report with a reason that goes to staff chat.
Cross-server reports
With several servers on one account the queue can be shared. A report from one mode becomes visible to staff on all the others, so an offender does not have to be caught on the server they already left.
server-identity:
name: "survival" # имя сервера в уведомлениях
family: "MyNetwork" # общая семья: делятся только внутри неё
interserver:
enabled: true # добавлять имя сервера в сообщения
cross-reports: true # общая очередь репортовReports are shared only between servers with the same family, which keeps separate projects on one key from mixing. Foreign reports are tagged with their origin server and teleport is disabled for them — the player is simply not there.
1. API key
The key is on the server card in your dashboard. One key belongs to one server: sharing it between servers mixes up statistics and daily request limits.
detection: enabled: true endpoint: https://api.mlsac.net api-key: APIKEY
2. Models
Open Configs →Which models you get is decided by your plan, not by preference. Mini is the free-plan model and is not available on paid plans; paid plans run Pro and Pulse instead. Pulse is the strongest of the three — granted after verification, it catches what the others miss. Pro is worth leaving enabled alongside it if your server sees very little PvP, where Pulse has less to work with. Mini and Pro always punish: neither can be set to alerts-only, because silencing them would disable punishments for the whole server. Display names are fixed by the service so alert templates stay consistent.
The strongest model. Granted after verification.
Free plan only — not available on paid plans.
Paid plans. Worth keeping on beside Pulse if your server has little PvP.
This is how the setting looks in the dashboard — it is not edited as YAML any more.
3. Penalties
Open Configs →Penalties are a ladder by violation level: a repeated detection raises the level and moves the player to the next action. You can stop at a kick, go straight to a ban, or skip bans entirely and only cut damage. Actions run as console commands, so anything your server supports works.
kick {PLAYER} MLSAC Detectionban {PLAYER} MLSAC DetectionThis is how the setting looks in the dashboard — it is not edited as YAML any more.
4. Damage reduction
Open Configs →Instead of banning outright, the plugin can gradually cut a suspect damage. Stages fire on a rolling window: more detections inside the window mean a stronger and longer reduction. Useful when you would rather frustrate a cheater than announce that they were caught.
This is how the setting looks in the dashboard — it is not edited as YAML any more.