> For the complete documentation index, see [llms.txt](https://mode-development.gitbook.io/atomcombat/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mode-development.gitbook.io/atomcombat/modules/stats.md).

# 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](/atomcombat/getting-started/storage.md)) 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](/atomcombat/reference/events.md).

## 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](/atomcombat/integrations/pulseprison.md).

## PlaceholderAPI

If `integrations.placeholderapi.enabled` is `true` in `config.yml` and PlaceholderAPI is installed, AtomCombat registers the `atomcombat` expansion automatically — see [Placeholders](/atomcombat/reference/placeholders.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://mode-development.gitbook.io/atomcombat/modules/stats.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.