Onboarding procedure

1. Register the server

Create the server entry in the panel and note the exact name you give it. That name is what history, the webhook and the cloud detections will be attributed to, and it is what domain verification binds the licence to.

2. Install

1. Stop the server.
2. Put the Venus jar in plugins/.
3. Remove any other anticheat and any standalone PacketEvents jar.
4. Start the server.

3. Confirm both halves are up

• Local checks: staff holding the alerts permission should see detections arriving as players move around. Silence for hours, on a server where you expect some noise, means something is off.
• Cloud: /venus version reports the connection state. If it says offline, the local anticheat still works; only cloud detections and ban waves are affected.

4. Watch before you tune

Give the default configuration a day of real traffic with alerts enabled for staff and punishments left where the shipped checks.yml puts them. Tuning thresholds before you have data is how servers end up with a configuration nobody can explain later.

5. Then tune deliberately

1. Start with configuration — the network and timeout options matter more than the check thresholds for most servers.
2. Move to checks.yml: decide which groups should punish at all, and leave the rest at alert and log.

6. Give your staff the right nodes

Alerts and mitigations are separate permissions for a reason: alerts are what most staff want, while mitigation notices are noisy. The list is on commands and permissions.

7. If you are writing an add-on

Continue with the API overview. It covers the dependency, how to obtain the API safely while the server is still starting, and the services you will use most.