Stats & Leaderboards

Config file: modules/stats.yml Command: /combatstats (alias: /cstats)

Checking stats

Command	Permission	Description
`/combatstats [player]`	`atomcombat.stats.use`	Shows kills, deaths, KDR, current streak and best streak. Defaults to yourself.
`/combatstats top [kills\|deaths\|kdr\|streak] [limit]`	`atomcombat.stats.use`	Leaderboard for the given metric. Defaults to `kills` and `leaderboard.default-limit`.

Admin commands

Command	Permission	Description
`/combatstats reset <player>`	`atomcombat.stats.admin`	Zeroes out a player's kills, deaths and streaks.
`/combatstats set <player> <kills\|deaths\|streak\|best-streak> <value>`	`atomcombat.stats.admin`	Overwrites a single metric, e.g. for correcting a mistake.

Storage

yaml

storage:
  file: data/stats.yml
  autosave-interval-seconds: 300

Stats are cached in memory and flushed to disk (or to SQL — see Storage) every autosave-interval-seconds, and once more on shutdown/reload.

Leaderboard defaults

yaml

leaderboard:
  default-limit: 10

Milestones

yaml

milestones:
  enabled: true
  broadcast: true
  thresholds:
    50: { commands: [] }
    100: { commands: [] }
    500: { commands: [] }
    1000: { commands: [] }

Unlike killstreaks (which reset on death), milestones fire once when a player's lifetime kill count crosses a threshold, and never again. Each threshold can run console commands (%player%, %uuid%, %threshold% tokens available) and optionally broadcast to the server. Fires AtomCombatMilestoneEvent — see Internal Events.

PulsePrison skill experience

yaml

pulseprison:
  skill-track: combat
  experience-per-kill: 0.0

When experience-per-kill is greater than 0, every confirmed kill grants that much experience on the given PulsePrison skill track. See PulsePrison integration.

PlaceholderAPI

If integrations.placeholderapi.enabled is true in config.yml and PlaceholderAPI is installed, AtomCombat registers the atomcombat expansion automatically — see Placeholders.