> 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/admin/commands-and-permissions.md).

# Commands & Permissions

## `/atomcombat`

Permission: `atomcombat.admin` (default: op)

| Subcommand                                        | Description                                                                                                                                               |
| ------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `/atomcombat reload`                              | Reloads `config.yml`, the active language file, and every module, without restarting the server.                                                          |
| `/atomcombat debug`                               | Reports license status and which soft-dependencies (Vault, LuckPerms, WorldGuard, PlaceholderAPI, PulsePrison, Discord webhook) are detected.             |
| `/atomcombat gui` (aliases: `menu`, `admin`)      | Opens the [Admin GUI](/atomcombat/admin/admin-gui.md).                                                                                                    |
| `/atomcombat settings`                            | Opens the [Live Settings](/atomcombat/admin/live-settings.md) editor.                                                                                     |
| `/atomcombat set <module\|config> <path> <value>` | Changes any setting in any module's YAML file (or the root `config.yml`) in place, then reloads. See [Live Settings](/atomcombat/admin/live-settings.md). |
| `/atomcombat get <module\|config> <path>`         | Prints the current value of any setting.                                                                                                                  |
| `/atomcombat announce <message>`                  | Broadcasts a one-off message immediately, with legacy colour codes.                                                                                       |

## `/bounty` (aliases: `/bounties`, `/recompensa`)

Permission: `atomcombat.bounties.use` (default: everyone)

See [Bounties](/atomcombat/modules/bounties.md#placing-listing-and-cancelling) for the full subcommand table. Admin-only subcommands (`admingui`, `recover`, and cancelling someone else's bounty) require `atomcombat.bounties.admin` (default: op).

## `/combatstats` (alias: `/cstats`)

Permission: `atomcombat.stats.use` (default: everyone)

See [Stats & Leaderboards](/atomcombat/modules/stats.md). `reset` and `set` require `atomcombat.stats.admin` (default: op).

## `/ability`

Permission: `atomcombat.ability.use` (default: everyone)

See [Rank Abilities](/atomcombat/modules/rank-abilities.md). `resetcooldown` requires `atomcombat.ability.admin` (default: op). Using a specific ability additionally requires that ability's own permission (`atomcombat.ability.dash`, `atomcombat.ability.charged-strike`, `atomcombat.ability.ground-slam` — all default to `false`).

## Full permission list

| Permission                          | Default | Grants                                                           |
| ----------------------------------- | ------- | ---------------------------------------------------------------- |
| `atomcombat.bounties.use`           | true    | `/bounty` base usage                                             |
| `atomcombat.bounties.admin`         | op      | Cancel any bounty, `/bounty admingui`, `/bounty recover`         |
| `atomcombat.stats.use`              | true    | `/combatstats` base usage                                        |
| `atomcombat.stats.admin`            | op      | `/combatstats reset`, `/combatstats set`                         |
| `atomcombat.ability.use`            | true    | `/ability` base usage                                            |
| `atomcombat.ability.dash`           | false   | Unlocks the Dash ability                                         |
| `atomcombat.ability.charged-strike` | false   | Unlocks the Charged Strike ability                               |
| `atomcombat.ability.ground-slam`    | false   | Unlocks the Ground Slam ability                                  |
| `atomcombat.ability.admin`          | op      | `/ability resetcooldown`                                         |
| `atomcombat.admin`                  | op      | `/atomcombat` (reload, debug, gui, settings, set, get, announce) |


---

# 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/admin/commands-and-permissions.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.