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

# Combat Core

Config file: `modules/combat-core.yml`

Combat Core is the foundation every other combat module builds on. It intercepts network packets (via PacketEvents) rather than reacting to already-processed Bukkit damage events, which lets it replace knockback and time attacks precisely.

## Knockback profiles

```yaml
knockback:
  profile: vanilla
  worlds: {}
  regions: {}
  profiles:
    vanilla: { horizontal: 0.4, vertical: 0.4, air-horizontal: 0.4, air-horizontal-limit: 0.4, vertical-limit: 0.4, preserve-vertical: true }
    one-eight: { horizontal: 0.4, vertical: 0.42, ... }
    custom: { ... }
```

* `knockback.profile` is the server-wide default: `vanilla`, `1.8` (maps to the `one-eight` profile) or `custom`.
* `knockback.worlds` and `knockback.regions` override the profile per world or per WorldGuard region (requires WorldGuard — see [WorldGuard integration](/atomcombat/integrations/worldguard.md)).
* Each profile's numeric fields mirror Minecraft's own knockback math: horizontal/vertical push, the airborne push and its cap, and whether the victim's existing vertical speed is preserved before the push is applied.

Use this to give your server the classic 1.8 knockback feel, vanilla behaviour, or fully custom values tuned to your PvP style.

## Shield blocking

```yaml
blocking:
  shield:
    enabled: true
```

Set to `false` to disable 1.9+ shield blocking entirely, for a purer 1.8 combat feel where shields can't stop melee hits.

## Sweep attack

```yaml
sweep-attack:
  enabled: true
```

Set to `false` to cancel the area-of-effect sweep attack that was added after 1.8.

## Attack timing

```yaml
timing:
  enabled: true
  max-pending-attacks: 32
  pending-window-milliseconds: 2000
```

Tracks precise attack intervals per player. This powers `AtomCombatHitEvent` (see [Internal Events](/atomcombat/reference/events.md)), which other modules (and PulsePrison, or your own addon) can listen to for combos, anti-abuse checks, or custom rewards.


---

# 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/combat-core.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.