> For the complete documentation index, see [llms.txt](https://docs.xandtech.fr/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xandtech.fr/home/xplayercurrencies/integrations/vault.md).

# Vault

Lets one currency also act as the server's Vault economy (`net.milkbowl.vault.economy.Economy`), so shop/jobs/every other Vault-aware plugin reads and writes that currency's balances too - on top of XPlayerCurrencies' own commands/GUI/PAPI, which keep working normally on the exact same underlying balance.

## Setup

1. Install [Vault](https://www.spigotmc.org/resources/vault.34315/) (it's a soft dependency, nothing breaks without it - this integration is simply unavailable).
2. In the currency's `currencies/<id>.yml`:

   ```yaml
   plugin-integration: VAULT
   ```
3. `/currencies admin reload`.

{% hint style="warning" %}
Only **one** enabled currency can back Vault at a time. If several currency files request `VAULT`, the first (by `priority` then id) wins and the rest are skipped with a console warning.
{% endhint %}

XPlayerCurrencies has no concept of per-world balances or banks in the Vault sense, so every `worldName` parameter Vault passes is ignored (the balance is the same everywhere), and Vault's own "bank" methods report `NOT_IMPLEMENTED` (use [XPlayerCurrencies' own bank](/home/xplayercurrencies/features/bank.md) instead, which is unrelated to Vault's bank API).

## Migrating existing balances into Vault-backed currency

If another plugin was already Vault's economy provider before you switch to XPlayerCurrencies:

```
/currencies admin migrate vault <currency> [confirm]
```

Without `confirm`, shows a preview of how many players would be imported. Run again with `confirm` to actually apply it - this **overwrites** the target currency's current balance for every imported player.

Next: [WorldGuard](/home/xplayercurrencies/integrations/worldguard.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.xandtech.fr/home/xplayercurrencies/integrations/vault.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.