Use MiniPlaceholders with a compatible Minecraft text plugin

MiniPlaceholders lets compatible Minecraft plugins resolve placeholders into Adventure text components. Installing it does not make every chat, scoreboard or MOTD plugin understand its syntax. Start by checking that the plugin displaying the text explicitly supports MiniPlaceholders.

Confirm the producer and consumer

Identify the plugin that supplies the value, such as a permissions expansion, and the plugin that displays it. Both sides must support the relevant integration. PlaceholderAPI percentage-style placeholders and MiniPlaceholders angle-bracket tags are different systems; changing punctuation does not convert one into the other.

Check the current platform and Java requirements on the official download and user guide. These requirements vary between project generations and platforms. Choose the build matching your actual Paper, proxy or supported mod installation instead of assuming one JAR works everywhere.

Use plugin installation for a Paper server. Keep the current text configuration, plugin versions and expansion files before changing an existing setup. A backup helps you return to the matched configuration if an integration update changes output.

Install one required expansion

1. Download MiniPlaceholders through the official project links and install the platform-appropriate artifact.
2. Read the placeholder catalogue for the value you need. Some integrations are built in; others require a separate expansion download or provider plugin.
3. Install only the documented expansion and its requirements. Do not add unrelated expansion collections to solve one missing value.
4. Start normally and read Console for dependency or API-version errors. Confirm the provider and text-consuming plugin also enabled.
5. Copy one documented placeholder into a test field that the consuming plugin says it processes through MiniPlaceholders. Keep the rest of that field plain text.

Preserve YAML or other configuration syntax around the text. An angle bracket inside a value is not itself an XML file, and a valid MiniMessage formatting tag does not prove the requested expansion is installed. Use the exact identifier and arguments from the catalogue.

Test the right player context

Some values are global, while others need a player or a pair of players. A server-list response may not have the same player context as an in-game chat message. On Paper, use /miniplaceholders expansions to list loaded expansions, then use the documented /miniplaceholders parse command with the intended player context. Velocity uses /vminiplaceholders. Check the consuming plugin's guidance as well; a Console-only test cannot represent every viewer.

Compare an administrator and an ordinary test player. Permission-based prefixes, groups or visibility can legitimately differ. If a relational value works for one viewer but not another, check whether the consuming plugin supports relational placeholders before changing group permissions.

Resolve literal tags and unexpected formatting

If the raw tag remains visible, check integration support, the expansion's loaded state and the exact configuration field. If the tag disappears but the value is empty, inspect its arguments and player context. If the text looks different, check how the consuming plugin serialises components and applies surrounding formatting.

Do not install a PlaceholderAPI bridge or proxy bridge unless the documented deployment needs it. Network bridging adds another component and is not an automatic fix for an incorrect tag. See PlaceholderAPI expansions for that separate system. Further reading: getting started, placeholder catalogue and diagnostic commands.

Looking for another plugin? Browse the Minecraft plugin guide directory.