Skip to main content

Identify a built-in PlaceholderAPI expansion before downloading another

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

Some plugins register their own expressions with PlaceholderAPI. Downloading a similarly named expansion can add confusion without repairing the original integration. Identify who owns the expression and what is already registered.

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. Find the affected expression in its author’s documentation. Note whether the author describes an eCloud download or a built-in integration, and record the exact identifier before changing the server.
  2. Compare papi list with the installed list shown by papi ecloud list installed. The registered list can include integrations supplied by another plugin, so a difference between these lists is not itself an error.
  3. Check the startup log for the owning plugin and its integration registration. A plugin that failed earlier may leave its expressions unavailable even though PlaceholderAPI itself started without a warning.
  4. Follow the owner’s documented dependency route on a staging copy. Add an eCloud expansion only when the documentation calls for it; otherwise repair the owning plugin’s actual startup failure.

Check the result

The intended identifier should register once and produce a value in a direct parse for a connected test account. Check the consuming display afterwards, since its configuration can still contain a misspelled expression.

If the test fails

If an added expansion did not help, remove only that test addition through the supported management method after recording its filename. Preserve the owning plugin’s data and previous expansion set while you investigate the first startup error.

A download catalogue and an active registry answer different questions. Use both as evidence, and avoid treating an absent eCloud entry as proof that a built-in integration is missing.

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