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

# Optional Integrations

CommandPrompter has no required plugin dependencies. When a supported plugin is present, its hook is loaded automatically.

| Plugin         | Integration                                                                                                                                                  |
| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| CarbonChat     | Captures active Chat prompt answers through CarbonChat's event bus instead of the Bukkit chat listener.                                                      |
| Geyser-Spigot  | Offers an optional [anvil patch](/commandprompter/features/geyser-anvil-patch.md) for Bedrock input and cancel materials. Disabled by default.               |
| PlaceholderAPI | Expands placeholders in inline prompt display text, localized messages, JavaScript validators, and preset post-commands where a player context is available. |
| LuckPerms      | Adds `lpo` and `lpg<group>;` Player UI filters.                                                                                                              |
| Towny          | Adds `tt` and `tn` Player UI filters.                                                                                                                        |
| HuskTowns      | Adds the `ht` Player UI filter.                                                                                                                              |
| WorldGuard     | Adds `wgr`, `wgrm<region>;`, and `wgro<region>;` Player UI filters.                                                                                          |
| SuperVanish    | Excludes vanished players from the normal Player UI head cache and updates the cache when visibility changes.                                                |
| PremiumVanish  | Uses the SuperVanish-compatible integration.                                                                                                                 |
| VanishNoPacket | Excludes vanished players from the normal Player UI head cache and tracks status changes.                                                                    |

Filter syntax is documented on [Player UI Prompt](/commandprompter/prompts/player-ui-prompt.md). Multiple filters compose (intersect) using an anchored longest-match parser (e.g. `r10s` selects players within 10 blocks AND excludes self), so short keys like `w` never shadow longer keys like `wgr`. If an optional filter plugin is absent, its filter is not registered and unrecognized filter tokens are skipped.

Supported vanish integrations (SuperVanish, PremiumVanish, VanishNoPacket) enforce vanish checks at the head-cache boundary: vanished players are never added to the cache and are filtered out across all views.

## PlaceholderAPI

When PlaceholderAPI is installed, placeholders expand in all player-visible presentation fields across every prompt type:

* **Chat**: Prompt text, cancel message, and hover message.
* **Anvil**: Window title, prompt text, and button text / hover lore.
* **Sign**: Prompt text and all default lines.
* **Player UI**: Prompt text and button text / hover lore.
* **Dialog**: Dialog title, body contents, row labels, and button labels / tooltips.
* **Title Displays**: Main and subtitle text from `-t` flags and preset `title_display`.
* **Compound Dialogs**: Display text of every sub-tag recursively.

Semantic fields (such as preset IDs, tag keys, validator aliases, numeric constraints, action return values, and player-submitted answers) are never expanded.


---

# 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://cyr1en.gitbook.io/commandprompter/features/integrations.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.