> For the complete documentation index, see [llms.txt](https://lethium.gitbook.io/lethium-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://lethium.gitbook.io/lethium-docs/placeholders/combat.md).

# Combat placeholders

Fury, auto-attack, targeted mob, killstreak and ability placeholders.

These are the fast-refreshing placeholders (every 0.1 second) and need `mob-rewards`, `killstreaks` or `ability` enabled.

### Fury and auto-attack

| Placeholder                           | Returns                                       |
| ------------------------------------- | --------------------------------------------- |
| `%clickem_combat_charge_percent%`     | The Fury meter, `0` to `100`                  |
| `%clickem_combat_autoattack_targets%` | Mobs the player's auto-attack is fighting now |
| `%clickem_combat_autoattack_limit%`   | The player's cap. `-1` means unlimited        |

### The mob being hit

The **target** is whichever ClickEm mob is in the player's crosshair, or the last one they hit if they are not looking at one. Empty if neither.

| Placeholder                                                          | Returns                                               |
| -------------------------------------------------------------------- | ----------------------------------------------------- |
| `%clickem_combat_target_name%`                                       | Internal MythicMobs id (`W1Z1f1`). Not for display.   |
| `%clickem_combat_target_display_name%`                               | Player-facing name (`Oak Whelp`)                      |
| `%clickem_combat_target_element%`                                    | Lower-case element id (`fire`, `neutral` if unmapped) |
| `%clickem_combat_target_element_color%`                              | That element's colour tag                             |
| `%clickem_combat_target_health%`, `_max_health%`                     | Health as full digits                                 |
| `%clickem_combat_target_health_formatted%`, `_max_health_formatted%` | Compact (`1.1M`)                                      |
| `%clickem_combat_target_health_percent%`                             | `0` to `100`                                          |

Health is refreshed about every 2 ticks. The values read a captured snapshot, never a live entity, so they are safe for BetterHud.

#### Recently hit mobs

For HUD popups above several mobs at once:

`%clickem_combat_target_<n>_<field>%`

`n` is **0-based**, oldest hit first, among the mobs the player hit in the last few seconds. It matches BetterHud's `popup_index`, so each stacked popup reads its own mob. `<field>` is one of `name`, `display_name`, `element`, `element_color`, `health`, `max_health`, `health_formatted`, `max_health_formatted`, `health_percent`.

Example: `%clickem_combat_target_0_element%`.

How long a hit mob keeps its slot is `combat.hud-slot-memory-ms` in `mob-rewards.yml` (2000). Match it to how long your popup stays visible.

### Killstreak

| Placeholder                                  | Returns                                                          |
| -------------------------------------------- | ---------------------------------------------------------------- |
| `%clickem_killstreak_count%`                 | Current streak (0 when timed out)                                |
| `%clickem_killstreak_decay_percent%`         | `100` the instant a kill lands, draining to `0` over the timeout |
| `%clickem_killstreak_seconds_left%`          | Seconds until the streak times out                               |
| `%clickem_killstreak_tier%`                  | Kills threshold of the current tier                              |
| `%clickem_killstreak_next_tier%`             | Threshold of the next tier. `-1` at the top                      |
| `%clickem_killstreak_tier_progress_percent%` | `0` to `100` toward the next tier                                |
| `%clickem_killstreak_timeout_seconds%`       | The configured timeout                                           |
| `%clickem_killstreak_limit_remaining%`       | Rewarded tiers left in the reward window                         |
| `%clickem_killstreak_window_seconds%`        | Seconds until the reward window resets                           |

### Abilities

| Placeholder                         | Returns                                                                                        |
| ----------------------------------- | ---------------------------------------------------------------------------------------------- |
| `%clickem_ability_fury%`            | Fury as `0` to `100`                                                                           |
| `%clickem_ability_<slot>_id%`       | Ability id in that slot                                                                        |
| `%clickem_ability_<slot>_name%`     | Plain name (for example `Cleave`)                                                              |
| `%clickem_ability_<slot>_ready%`    | `true` or `false`                                                                              |
| `%clickem_ability_<slot>_cooldown%` | Whole seconds left, `0` when ready                                                             |
| `%clickem_ability_<slot>_state%`    | Empty if nothing equipped, else `ready`, `noready` (on cooldown) or `nofury` (not enough Fury) |

`<slot>` is `active_1`, `active_2`, `ultimate`, `passive_1` or `passive_2`.

The `_state` value matches the BetterHud icon files `a1_ability_ready.png`, `a1_ability_noready.png`, `a1_ability_nofury.png` (and `a2`, `u`, `p1`, `p2`).


---

# 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://lethium.gitbook.io/lethium-docs/placeholders/combat.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.