checks.yml reference
Every key in checks.yml, its type and its shipped default. For what the keys do, start at the
checks overview.
The file has three top-level sections: autototem, crystalaura and anchormacro.
Shared keys
autototem, crystalaura and anchormacro share this structure.
| Key | Type | Meaning |
|---|---|---|
enabled |
boolean | Master switch. The checks GUI toggle writes exactly this key |
precision |
STRICT | FINE | STANDARD |
How much evidence is required before a flag |
mitigation |
boolean | Actively cancel the cheat's packets instead of only flagging. On/off only; when and how it steps in is managed by Ecstacy, not customer-tunable. Present but not yet active on autototem (beta) |
fail.max |
integer | Violation level at which punish runs |
fail.alert.enable |
boolean | Alert staff on a flag |
fail.alert.viewer |
STAFF | ALL |
Who sees the alert |
fail.alert.mode |
INHERIT | CHAT_AND_WEB | WEB_ONLY |
Per-check override of alerts.mode in settings.yml. INHERIT follows the global setting |
fail.alert.console |
boolean | Print this check's flags to the server console |
fail.alert.every |
integer | Alert on every nth flag |
fail.commands |
list of strings | Console commands run on every flag |
punish.enable |
boolean | Whether the threshold acts |
punish.effect |
string | Effect applied on punishment. Custom values can be registered through the API |
punish.alert.enable |
boolean | Alert staff on punishment |
punish.alert.viewer |
STAFF | ALL |
Who sees it |
punish.commands |
list of strings | Console commands run once, at the threshold |
Placeholders in both command lists: %player%, %check%, %vl%, %maxVl%.
Defaults by family
| Key | crystalaura |
anchormacro |
autototem |
|---|---|---|---|
enabled |
true |
true |
true |
precision |
FINE |
STANDARD |
STANDARD |
fail.max |
20 |
20 |
40 |
fail.alert.every |
1 |
1 |
5 |
fail.alert.mode |
INHERIT |
INHERIT |
INHERIT |
fail.alert.console |
true |
true |
true |
fail.commands |
one example | one example | empty |
punish.enable |
true |
true |
true |
punish.commands |
one example ban |
one example ban |
empty |
mitigation |
false |
false |
false (beta) |
heuristic block |
enabled, mode, shadow |
enabled only |
n/a |
Heuristic keys
Present on crystalaura and anchormacro only.
| Key | Type | Default | Meaning |
|---|---|---|---|
heuristic.enabled |
boolean | false |
Master switch for the heuristic layer |
heuristic.mode |
VANILLA_IMPOSSIBLE | DETERMINISTIC | BOTH |
VANILLA_IMPOSSIBLE |
Which tier of hard-flags runs. crystalaura only |
heuristic.shadow |
boolean | true |
Record violations but never punish. crystalaura only |
Note
This page tracks the cloud-side authoritative defaults, which are what the dashboard serves to new installs. The copy shipped inside the plugin jar can lag behind by a release. When they disagree, the cloud one wins.