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

# AtomCombat

AtomCombat is a modular, packet-based combat plugin for Paper survival, survival-op and prison servers. It brings back a 1.8-style PvP feel on modern Minecraft versions, adds serious combat rules, a player-funded bounty system, rank-gated abilities, per-player stats and leaderboards, and first-class integration with PulsePrison — while staying fully usable standalone.

## What AtomCombat is

* A combat rules and mechanics plugin for the "normal" world of your server: survival, survival-op, prison.
* Modular: every feature is its own module that can be enabled or disabled independently in `config.yml` without breaking the rest.
* Packet-based at its core (via PacketEvents), giving real control over knockback and attack timing instead of patching vanilla behaviour after the fact.
* Standalone: every feature works with no other plugin installed.
* Deeply compatible with PulsePrison when it is installed, through AtomCombat's own internal event bus.

## What AtomCombat is not

* Not a practice/duels core: no queues, no ELO, no 1v1 arenas.
* Not a minigame plugin: no FFA, no dedicated kitmap.
* Not a replacement for PulsePrison — it complements it.

## Supported versions

* Paper 1.20.4 through 1.21.11.
* Java 17 or newer.

## Where to start

* [Installation](/atomcombat/getting-started/installation.md) to get the plugin running.
* [First setup](/atomcombat/getting-started/first-setup.md) to activate your license and pick a language.
* [Modules](/atomcombat/getting-started/modules.md) for a map of every feature and its toggle.


---

# 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/readme.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.