> 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/getting-started/modules.md).

# Modules

AtomCombat is split into independent modules. Each one is toggled in `config.yml` under `modules:`, and each owns one file under `plugins/AtomCombat/modules/`.

```yaml
modules:
  combat-core:
    enabled: true
  combat-rules:
    enabled: true
  bounties:
    enabled: true
  stats:
    enabled: true
  rank-abilities:
    enabled: true
  effects:
    enabled: true
  announcements:
    enabled: false
```

| Module                                                  | Config file                  | Purpose                                                                                                            |
| ------------------------------------------------------- | ---------------------------- | ------------------------------------------------------------------------------------------------------------------ |
| [Combat Core](/atomcombat/modules/combat-core.md)       | `modules/combat-core.yml`    | Packet-based knockback, shield blocking, sweep attack, attack timing. The foundation every other module relies on. |
| [Combat Rules](/atomcombat/modules/combat-rules.md)     | `modules/combat-rules.yml`   | Combat tag, grace periods, PvP/keep-inventory/keep-experience rules.                                               |
| [Bounties](/atomcombat/modules/bounties.md)             | `modules/bounties.yml`       | Player-funded bounties, kill recaps, killstreaks.                                                                  |
| [Stats & Leaderboards](/atomcombat/modules/stats.md)    | `modules/stats.yml`          | Per-player kills/deaths/KDR/streak tracking, leaderboards, lifetime kill milestones.                               |
| [Rank Abilities](/atomcombat/modules/rank-abilities.md) | `modules/rank-abilities.yml` | Permission and rank-gated combat abilities: dash, charged strike, ground slam.                                     |
| [Effects](/atomcombat/modules/effects.md)               | `modules/effects.yml`        | Particles, sounds, fireworks and action bar feedback tied to combat events.                                        |
| [Announcements](/atomcombat/modules/announcements.md)   | `modules/announcements.yml`  | Recurring broadcast messages.                                                                                      |

Disabling a module fully unregisters its commands and listeners; nothing from a disabled module runs. Re-enabling it (or running `/atomcombat reload` after flipping the toggle) restarts it cleanly.

You can also toggle every module live from the [Admin GUI](/atomcombat/admin/admin-gui.md) without editing YAML.


---

# 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/getting-started/modules.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.