Skip to main content

Prepare a useful report for a Vault integration error

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

A maintainer can investigate an integration error faster when you identify both sides of the bridge. A screenshot saying that a plugin is red omits the dependency that failed first.

Before you start

Vault connects consumer plugins to an economy provider; it does not replace that provider or store your player balances. Identify the component holding the money before changing integrations, and check the provider name in startup logs.

Work through the check

  1. Copy the server software, Java version, Vault build, provider build and affected consumer build from the running service.
  2. Capture the first startup exception and its surrounding hook messages, then note the exact action and timestamp that trigger the later error.
  3. Reproduce with a low-value test account and record the before-and-after balance, including whether an item or reward arrived.
  4. Compare the reproduction on a backed-up test copy with optional consumers removed one at a time, keeping required dependencies intact.

What to compare

Include the first relevant exception and its surrounding startup lines in the report. A final message saying a consumer disabled itself usually explains less than the earlier dependency error that caused it.

Confirm the result

Your report should name the active provider and show a repeatable action, a complete exception chain and the observed transaction outcome.

If the result differs

Redact database passwords, tokens and player addresses before sharing logs. Do not upload an entire server directory or use a public diagnostic upload without reviewing its contents.

Recover safely

Keep production transactions paused if outcomes are inconsistent. Restore any temporarily removed test plugins and their matching configuration before using that test copy for another comparison.

CloudExa game console with the log controls visible.
The CloudExa console provides the log view used in this check. This is a general panel screenshot, not plugin-specific output.

Documentation and related help

Check the Vault maintainer documentation and Vault maintainer reference against your installed release before applying changes.

No comments to display