Choose MiniPlaceholders or percent-style placeholders for one field
A plugin can support MiniMessage formatting without automatically supporting every placeholder system. Check the exact field’s integration documentation before converting all of its text to another syntax.
Prepare the test
Choose the correct execution platform before testing a tag. A proxy and a backend can have different expansions, audiences and permissions even when the same player appears on both.
Make the change
- Copy the original field into a local note. Separate formatting tags, MiniPlaceholders tags and percent-style expressions so you can identify which parser should handle each part.
- Check the destination plugin’s documented support and required integrations. Verify its own version and the platform where it runs before interpreting a raw tag as a missing expansion.
- Test one supported value with minimal formatting in a private copy of that field. Compare a direct MiniPlaceholders parse with the destination output, keeping the same test player context.
- Add formatting back in small steps after the value resolves. If the plugin offers different configuration paths for different parsers, select one documented route instead of nesting syntax by guesswork.
Check the result
The destination should show the intended value and formatting without literal tags or percent tokens. Test both a populated result and an empty result because an empty string can conceal a parsing failure.
If the test fails
Restore the original field when the destination does not support the chosen system. Use its supported integration or ask the maintainer about that exact field rather than replacing the whole text stack.
Keep player-entered text outside any path that treats it as trusted formatting or command content.
References and related help
Check the official MiniPlaceholders documentation against your installed release before using a command or setting from another version.