Skip to main content

Pin one PlaceholderAPI expansion update for a staging test

Applies to: PlaceholderAPI; match the linked maintainer documentation to your installed platform and release.
Documentation checked .

An expansion update can change an expression’s output while the menu or scoreboard stays the same. Test one expansion release against recorded values before replacing several integrations during the same maintenance window.

Prepare the test

Keep the original placeholder text beside the result during diagnosis. The expansion supplies the data; the scoreboard, menu or chat plugin decides where and how to display that result.

Make the change

  1. List the target expansion’s information and note its current version. Save its original jar and any related settings, then make a staging copy with separate credentials for external integrations.
  2. Use papi ecloud info with the expansion name and requested version to check the release details. The documented download command accepts a version argument; confirm that release exists before selecting it.
  3. Download only the selected release on the test server and follow PlaceholderAPI’s documented registration or reload procedure. Do not use a general server reload to substitute for a plugin’s supported update path.
  4. Parse a small recorded set of expressions: a populated value, an empty value and a player with different permissions. Compare formatting, number types and error messages before testing the consuming display.

Check the result

Approve the update when the expressions retain the meaning your displays expect and the log shows no repeated registration failures. Record the tested expansion version beside the server and provider versions for the next update.

If the test fails

If output changes break a display, restore the previous expansion jar and matching settings using a controlled stop and start where appropriate. Keep the new file separately for investigation rather than repeatedly swapping versions during live play.

Treat an expansion and its data provider as a pair. A newer expansion cannot make an unsupported provider version compatible, and a successful download does not prove that the integration works.

References and related help

Check the official PlaceholderAPI documentation against your installed release before using a command or setting from another version.

No comments to display