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

# Effects

Config file: `modules/effects.yml`

The Effects module adds no commands or gameplay rules of its own — it purely listens to AtomCombat's internal events (see [Internal Events](/atomcombat/reference/events.md)) and layers particles, sounds, fireworks and action bar feedback on top of them. Disabling this module removes all of the below without affecting the underlying mechanics.

## Kill feedback

```yaml
kill:
  enabled: true
  particle: FLAME
  particle-count: 30
  sound: ENTITY_WITHER_DEATH
  sound-volume: 0.6
  sound-pitch: 1.4
```

Plays at the victim's location on every confirmed PvP kill. `particle` and `sound` accept any Bukkit `Particle`/`Sound` enum name.

## Killstreak firework

```yaml
killstreak:
  firework-enabled: true
  firework-power: 1
```

Launches a firework on the player when they reach a killstreak threshold (see [Bounties](/atomcombat/modules/bounties.md#killstreaks)). `firework-power` is the flight height (`0`-`3`); `0` detonates immediately at the player's feet.

## Bounty claimed firework

```yaml
bounty-claimed:
  firework-enabled: true
```

Launches a firework on the killer when a bounty is paid out.

## Bounty placed alert

```yaml
bounty-alert:
  enabled: true
  sound: ENTITY_ENDER_DRAGON_GROWL
```

Plays a sound and shows a title/subtitle to a player the moment someone places a bounty on them (if they're online). The text is localized — see the `effects` section of your [language file](/atomcombat/getting-started/language.md).

## Combat tag action bar

```yaml
combat-tag:
  action-bar: true
```

Shows a live countdown ("In combat: 12s") in the action bar to both players involved in a combat tag, for the duration configured in [Combat Rules](/atomcombat/modules/combat-rules.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/effects.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.