Confirmed cheat bans

#What counts as a ban

Only a confirmed ban is reported. A violation level is not a ban and a kick is not a ban, so neither is ever sent.

The connector decides by watching which punishment command actually ran. You control that list, so a network with its own punishment plugin can name its own ban command.

#Configuration

The anticheat block lives in the Paper connector config. The connector attaches to whichever supported anticheat it finds at startup.

anticheat:
  enabled: true

  # A punishment counts as a ban only when it runs one of these.
  ban-commands:
    - "ban"
    - "tempban"
    - "banip"
    - "litebans:ban"

  # Only needed when your build's class names differ from the known ones.
  grim:
    event-classes: []

  # Polar publishes no event class this connector can rely on, so nothing is
  # reported from Polar until you name its punishment event class here.
  polar:
    event-classes: []

#Why a ban can arrive early

Sessions are posted when a player leaves, so a ban usually reaches us before the record that would create the player. The API answers 425 in that case and the connector retries, rather than dropping the first offence of every cheater it catches.

A ban never creates a player, because inventing a first join time and an empty acquisition source would corrupt the numbers this product exists to report.