> For the complete documentation index, see [llms.txt](https://wiki.helpch.at/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.helpch.at/helpchat-plugins/chatchat/placeholders.md). # Placeholders ChatChat PlaceholderAPI placeholders, internal tags, and configurable MiniPlaceholders. ChatChat provides a PlaceholderAPI expansion and internal MiniMessage tags for use in formats and configured placeholders. ## PlaceholderAPI placeholders ChatChat registers its own `chatchat` expansion. No separate eCloud download is needed. | Placeholder | Return value | Description | | --------------------------------------- | ------------ | -------------------------------------------------------------------------------------------- | | `%chatchat_channel_name%` | Text | The player's current channel name. | | `%chatchat_channel_prefix%` | Text | The display prefix of the player's current channel. | | `%chatchat_channel_message_prefix%` | Text | The quick-send prefix of the player's current channel. | | `%chatchat_social_spy_enabled%` | Boolean | Whether social spy is enabled for the player. | | `%chatchat_private_messages_enabled%` | Boolean | Whether the player accepts private messages. | | `%chatchat_private_messages_recipient%` | Text | Name of the last private-message conversation target, or an empty string when there is none. | | `%chatchat_ranged_chat_enabled%` | Boolean | Whether the player has ranged-chat filtering enabled. | The last-message target expires after `last-messaged-cache-duration` seconds by default. A negative value disables expiration. ## Tags for formats These tags are available in ChatChat formats. MiniMessage tag names are case-insensitive. | Tag | Example | Result | | ---------------------- | -------------------------------------- | ------------------------------------------------------------------------------------------------------------------------- | | `` | `` | Parses a PlaceholderAPI placeholder for the sender. | | `` | `` | Parses a sender placeholder without allowing legacy color formatting to continue past the inserted value. | | `` | `` | Parses a sender placeholder and lets its formatting continue after the inserted value. | | `` | `` | Parses a relational PlaceholderAPI placeholder for the sender and recipient. The placeholder name must begin with `rel_`. | | `` | `` | Parses a PlaceholderAPI placeholder for the message recipient. | | `` | `` | Inserts the processed chat or private message into a format. | Use the PAPI placeholder name without `%` inside these tags. The regular `%placeholder%` syntax is also available in configured formats. Recipient and relational tags need a recipient context, such as a private-message format or a per-recipient public format. Cross-server private-message formats support `` for the remote recipient. ## Configured MiniPlaceholders Define custom tags in `placeholders.yml`. A configured tag named `greeting` is used as ``. The tag name must match `[!?#]?[a-z0-9_-]*`. Players need `chatchat.tag.placeholder.greeting` to use it in their own messages; configured formats can use the tag without that player-message permission. | Option | Purpose | | -------------------- | ------------------------------------------------------------------------------------------------------------------------------------- | | `name` | Tag name used between angle brackets. | | `message` | Text inserted by the tag. | | `requires-recipient` | When `parse-mini` and `parse-papi` are enabled, allows recipient and relational placeholders and requires a player recipient context. | | `parse-mini` | Parses MiniMessage tags inside the configured message. | | `parse-papi` | Parses supported PlaceholderAPI tags when `parse-mini` is enabled. | | `closing` | When true, closes formatting from the inserted content. When false, inserted formatting can continue into the surrounding format. | See [MiniMessage tags in chat](/helpchat-plugins/chatchat/tags.md) for the tags players can use in public messages. --- # 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://wiki.helpch.at/helpchat-plugins/chatchat/placeholders.md?ask=&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.