> For the complete documentation index, see [llms.txt](https://docs.xandtech.fr/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xandtech.fr/home/xplayerexp/features/integrations.md).

# Integrations (PlaceholderAPI, bStats, Hex Colors)

## PlaceholderAPI

If [PlaceholderAPI](https://www.spigotmc.org/resources/placeholderapi.6245/) is installed, the `xplayerexp` expansion registers itself automatically at startup — no separate download, no `/papi ecloud` install step. See the full placeholder list in [PlaceholderAPI](/home/xplayerexp/reference/placeholderapi.md).

## bStats

XPlayerEXP reports anonymous, aggregate usage statistics via [bStats](https://bstats.org/) (plugin ID `33623`) — the same opt-out mechanism every bStats-integrated plugin shares, controlled server-wide from `plugins/bStats/config.yml`, not from anything in XPlayerEXP itself. No per-player data is ever collected; it's server counts only (how many servers run the plugin, which Minecraft/plugin versions, etc.).

## Hex colors everywhere

Every piece of configurable text — messages, the bottle's display name and lore, the Double XP boss bar title, the help menu — goes through the same formatter, which understands both:

* **Legacy codes**: `&a`, `&c`, `&l`, ...
* **Hex codes**: `&#RRGGBB`, e.g. `&#ff8800` for orange.

```yaml
bottle-settings:
  item:
    display-name: "&#4C93FF&lExperience Bottle &7(Right-Click)"
```

Mix both freely in the same string — hex codes are converted first, then legacy codes are applied on top, so `&#ff0000&lBOLD RED` works exactly as you'd expect.

{% hint style="info" %}
A missing translation key never crashes a message — it prints `[Missing lang key: <path>]` in-game and logs a warning to console, so a partially-translated custom language file degrades visibly instead of throwing an error.
{% endhint %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.xandtech.fr/home/xplayerexp/features/integrations.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.