> 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/rank-abilities.md).

# Rank Abilities

Config file: `modules/rank-abilities.yml` Command: `/ability`

Rank Abilities are AtomCombat's answer to donor/prestige progression: short, punchy combat abilities that only players with the right permission (and optionally the right PulsePrison prestige/rebirth) can use.

## Using abilities

| Command         | Description                                                                  |
| --------------- | ---------------------------------------------------------------------------- |
| `/ability <id>` | Activates the named ability if you're unlocked and off cooldown.             |
| `/ability list` | Shows every ability with its status (ready / locked / on cooldown).          |
| `/ability gui`  | Same information as an inventory menu; click a ready ability to activate it. |

Pressing the swap-hands key (F by default) also activates the first ability you have unlocked and ready, in the order abilities are declared in the config, if `swap-hand-trigger: true`.

## Admin

| Command                                     | Permission                 | Description                                                           |
| ------------------------------------------- | -------------------------- | --------------------------------------------------------------------- |
| `/ability resetcooldown <player> [ability]` | `atomcombat.ability.admin` | Clears one ability's cooldown, or all of them if no ability is given. |

## Rank gating

Each ability is gated by a Bukkit permission (which works naturally with LuckPerms — grant `atomcombat.ability.<id>` to a rank group) and, optionally, a minimum PulsePrison prestige or rebirth:

```yaml
abilities:
  dash:
    enabled: true
    permission: atomcombat.ability.dash
    cooldown-seconds: 12
    pulseprison:
      min-prestige: 0
      min-rebirth: 0
```

If PulsePrison isn't installed, or `min-prestige`/`min-rebirth` are `0`, the PulsePrison check is skipped and only the permission matters.

## Built-in abilities

### Dash

```yaml
dash:
  horizontal-force: 1.8
  vertical-boost: 0.35
```

A short forward dash in the direction you're facing, with a small upward boost to clear ledges.

### Charged Strike

```yaml
charged-strike:
  duration-seconds: 4
  strength-amplifier: 1
```

Grants a temporary Strength buff (amplifier configurable — `1` is Strength II) for `duration-seconds`.

### Ground Slam

```yaml
ground-slam:
  radius: 4.0
  knockback-force: 1.4
  damage: 4.0
```

Slams the ground, damaging and knocking back every entity within `radius` blocks.

## Adding permissions to ranks

Each ability's permission node defaults to `false` in `plugin.yml`:

* `atomcombat.ability.dash`
* `atomcombat.ability.charged-strike`
* `atomcombat.ability.ground-slam`

Grant them per rank with your permissions plugin, e.g. with LuckPerms:

```
/lp group vip permission set atomcombat.ability.dash true
```

Every ability activation fires `AtomCombatAbilityUsedEvent` — see [Internal Events](/atomcombat/reference/events.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/rank-abilities.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.