Configuration

Venus ships with sensible defaults; most servers never need to touch anything except checks.yml. The reference values for each option are documented in the comments of the shipped files themselves.

The files

• checks.yml — which checks are active and what happens as violations accumulate. This is the file server owners live in: it groups checks and assigns thresholds and actions to each group.
• config.yml — general behaviour: network handling, timeouts, alert presentation and per-check tuning.
• messages.yml — every line the plugin and its commands print. See localisation.
• discord.yml — webhook settings and message templates.
• cloud.yml — cloud connection and mitigation behaviour. See the Cloud API.
• database.yml and the databases/ folder — storage backend selection and connection details.

checks.yml

Checks are organised into named groups. A group decides how long a violation counts, which checks belong to it, and what happens when a player crosses a threshold — an alert, a log line, a broadcast, a ban or a cloud ban wave. A check that appears in no group is switched off, so an empty file never punishes anyone.

Thresholds reference the violation level the check has built up; the details of how violation levels rise and decay are explained on detections and mitigations.

If you are migrating from another anticheat, start from the shipped groups file rather than writing one from scratch — the group names and check groupings match the categories used throughout the docs.

Changing things safely

• Change one group at a time and watch the alerts for a while before the next change.
• Prefer raising a threshold over disabling a check — a noisy check with a high threshold still catches the heavy cases.
• Configuration changes can be applied without a restart, but a change to the storage backend needs one.