Cloud API overview

The cloud is a remote machine-learning engine that classifies behaviour over longer windows than a local check can see: rotation analysis, combat heuristics, backtrack detection and clicking heuristics. It runs alongside the local checks — never instead of them — and the whole integration is optional.

The loop

1. Each tracked player's telemetry is submitted every submit-interval-ticks (1 by default — the ML windows want per-tick signal).
2. The cloud classifies and answers with flags, mitigations or punishment triggers, which flow back into the normal pipeline: violations are counted, alerts are sent, mitigation profiles are applied.
3. Native checks feed the same escalation engine — failing local combat checks escalates combat mitigations too, so the two halves stay consistent.

What is enabled by default

The cloud integration ships enabled with the default endpoint configured, and your licence and server identity are validated automatically against the backend — there is nothing to type in. Telemetry is submitted every server tick for the best signal, and mitigation is on. Every knob is documented in the comments of the shipped cloud configuration file.

Observing it from a plugin

The runtime state is on CloudService — connection status, the server name, per-user mitigation state. The two events that carry cloud decisions are CloudDetectionEvent and MitigationEvent, both cancellable, so an integration can suppress or annotate anything the cloud decides.

api.events().repository().register(CloudDetectionEvent.class, event -> {
    if (event.confidence() < 0.6) {
        event.setCancelled(true);       // ignore low-confidence classifications
    }
});

What is not sent

Cloud features exchange the signals needed to classify behaviour — rotations, clicks, movement and combat telemetry — not chat logs and not inventory contents. With the cloud disabled, nothing leaves the server and local checks, alerts, history and punishments keep working unchanged.

Setup: domain verification and onboarding procedure. Runtime controls: CloudService.