Player XP as your Vault currency: payments, XP cheques, requests, bill splitting, online bonus, leaderboard.
New: XP banks (
/economy bank, German aliaskasse). Players create named, shared XP pots (3–16 letters, digits,_or-), add members, and deposit or withdraw. XP in a bank is not on anyone's XP bar, so it is safe when you die and does not count for/baltop./economy bankopens a dialog with your banks. Each bank shows its balance, owner, members and its latest bookings, and has an amount field with deposit and withdraw buttons. Owners also get add or remove member and close bank. Closing pays the remaining XP to the owner. Every bank change is written todata/banks.json(atomically) before the XP moves the other way, and it is reverted if the second step fails, so XP is never doubled or lost. Player bookings appear in/economy historyas "XP bank". Admins (xpeconomy.admin) can see, withdraw from and close every bank, and/economy admin infoshows the number of banks and their total. Permissionxpeconomy.bank(default: everyone). Config:banks.enabled,banks.max-per-player(3) andbanks.max-members(10). The optionalbanks.vault-api(default off) offers the banks to other plugins through the Vault bank API. Non-empty banks are never deleted through that API.New: Standing orders (
/economy standing, German aliasdauerauftrag). A player pays another player a fixed amount every interval (12h,1d,1w, at leaststanding-orders.minimum-interval-minutes, default 60). Runs are either unlimited or a set count. The first payment runs right after confirmation, and later ones also run while the payer is offline. Each run is a normal player payment: it respects personal/economy limits, refunds the payer when the recipient's balance is full, and is recorded on both sides as "Standing order". An order's next date is saved before the XP moves, so a crash can skip one payment but never pay twice. Dates missed during downtime are not paid afterwards. Failed runs (for example not enough XP) are reported. Afterstanding-orders.pause-after-failuresfailures in a row (default 3), the order pauses, and the payer is told on their next join. Orders can be listed, paused, resumed and cancelled with clickable chat buttons or in a dialog. Recipients see the orders that pay them. Permissionxpeconomy.standing(default: everyone). Config:standing-orders.enabledandstanding-orders.max-per-player(10). Data:data/standing-orders.json.The account dialog (
/economy) has the buttons "XP banks" and "Standing orders". The player menu (Core 0.43.0, sneak + right-click a player) adds "Standing order to " (with the recipient filled in) and, for bank owners, "Add to your XP bank". Tab completion covers both commands, including your bank names and order numbers. All new settings are in/vadmin config XPVaultEconomy.Fixed (before release):
- A bank could no longer be withdrawn from once
economy.maximum-balancewas lowered below its balance (every withdrawal failed with "bank full"); only deposits are capped now. - The first standing-order payment, made right after confirmation, now queues an account save at once instead of waiting for the next save interval.
- A crash between a bank booking or standing-order payment and the next account save (a few seconds later) could create or lose the XP of that booking.
banks.jsonandstanding-orders.jsonnow record the player balances of each booking in the same atomic write (pending) until an account save contains them; on start, unsaved ones are put back (logged as a warning). Bank withdrawals and closing a bank now credit the player first and take it back if the bank file cannot be written.
- A bank could no longer be withdrawn from once
Requires Vystorm Core 0.44.0 (update Core first).