Commands
The player command /pv and the staff command /pvadmin, with their aliases, permissions and what each argument accepts.
Two commands. /pv is everything a player does with their own vaults; /pvadmin is everything staff do
with somebody else's. A player argument accepts anybody this server has seen, online, offline or on
another server, and suggests their names as you type.
/pv
/pv has the aliases /playervault, /playervaults, /vault and /vaults, and needs
exyliaplayervaults.use. It is for players only.
| Command | Permission | What it does |
|---|---|---|
/pv | exyliaplayervaults.use | Opens the vault list. |
/pv <number> | exyliaplayervaults.use | Opens that vault, after the restrictions. |
/pv search <item> | + exyliaplayervaults.search | Which of your vaults hold an item, by material or name. |
/pv <number> past the vaults a player has answers "You do not have vault <number>.". Renaming,
changing icons and buying are done from the list, not by command.
/pvadmin
/pvadmin has the alias /playervaultsadmin. On its own it prints the usage, with
exyliaplayervaults.admin.view.
| Command | Permission | What it does |
|---|---|---|
/pvadmin list <player> | exyliaplayervaults.admin.view | Their vault list; each vault opens to edit or read only, as the sender may. |
/pvadmin view <player> <number> | exyliaplayervaults.admin.view | A vault as stored, read only, without closing it for whoever has it open. |
/pvadmin edit <player> <number> | exyliaplayervaults.admin.edit | A vault, to change it; a window open elsewhere is written and closed first. |
/pvadmin history <player> <number> | exyliaplayervaults.admin.history | Its earlier copies, to look at, or put back with admin.edit too. |
/pvadmin clear <player> <number> | exyliaplayervaults.admin.clear | Empties it after a confirmation; the contents go to its history first. |
/pvadmin reload | exyliaplayervaults.admin.reload | Reloads config.yml, the messages and the menus. |
Every subcommand except reload is for players only. <number> starts at 1 and is not checked against
the owner's allowance. See Staff tools.
What reload does
Two steps: configs reads config.yml and messages.yml again, applies the prefix and restarts the
checkpoint timer at the new vaults.checkpoint; menus compiles both screens again, rewriting
menus/admin/ from the jar first. The menus step also runs when ExyliaLib itself is reloaded, so a
palette change reaches the screens.
Open vaults are not touched by a reload. A new default-rows, hidden-slots or blocked-materials applies
to the next window opened.
Something missing on this page? Tell us on Discord