Find a missing MiniPlaceholders expansion on the correct server
A backend can show the right expansion while the proxy still lacks it. Identify where the message renders before reinstalling files or comparing expansion lists from unrelated server consoles.
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
- Find the plugin that owns the affected message and establish whether it runs on Paper, another supported backend platform, or Velocity. Record that instance beside the exact tag.
- Run the documented expansions subcommand on that instance. Compare the listed identifiers with the expansion documentation, including spelling and any dependencies required by its current release.
- Check startup messages for the expansion and its data provider on the same instance. An expansion jar on a different server does not make the integration available here.
- Add or repair only the required integration on a test copy, using its supported platform artifact. Start the test instance cleanly, list expansions again, and parse a small example before restoring the full message.
Check the result
The relevant registry should contain the intended expansion, and a direct parse should produce the expected value on the renderer’s own instance. Check the visible message afterwards with an ordinary account.
If the test fails
If the integration will not register, restore the previous artifact set and investigate its first startup error. Keep proxy and backend files separate; copying every jar to both instances can introduce unsupported deployments.
Use the expansion author’s compatibility guidance rather than treating similarly named PlaceholderAPI and MiniPlaceholders downloads as interchangeable.
References and related help
Check the official MiniPlaceholders documentation against your installed release before using a command or setting from another version.