Skip to main content

Share a useful PlaceholderAPI support report without player data

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

A useful report shows which expression failed, which player context you supplied and whether the provider started. A large unreviewed log can disclose player names, network addresses or integration details that support does not need.

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. Record the server build, PlaceholderAPI version, provider version and affected display plugin. Keep the exact expression in a private note and reproduce the failure with a disposable test identity where the provider permits it.
  2. Capture a direct parse result and the corresponding startup registration messages. Include the first relevant error and its surrounding cause chain, rather than sending hundreds of repeated follow-up exceptions.
  3. If you use papi dump, understand that it uploads environment information to a paste service. Review what the report contains and use a private support route when it includes information you do not want public.
  4. Attach a short reproduction sequence and the expected result. State whether the failure affects one account, all accounts, console-only output or only a particular display; those distinctions narrow the integration path.

Check the result

A reviewer should be able to identify the failing layer from your report without receiving passwords, account balances or a full unredacted player list. Confirm the shared link is the intended report before submitting the ticket.

If the test fails

If a report exposed a secret, restrict or remove access where the service allows it and rotate that secret through its owner. Do not regenerate repeated public dumps as a substitute for collecting a smaller redacted example.

CloudExa support can inspect your hosting service, but the plugin maintainer may need the same version and parse evidence for an upstream bug. Keep that evidence independent of customer credentials.

CloudExa game panel console and logs view for collecting startup and diagnostic evidence
Collect the relevant timestamped log text in the panel, then remove private data before sharing it with support.

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