Staff tools
Anybody's graves from /gravesadmin list, looking inside, teleporting, handing back or removing one, restoring all of a player's graves, and the audit log.
Every staff tool takes a grave the way a player does, by deleting its row. Staff handing a grave back while a looter clicks it, or while it expires, hands it over once.
/gravesadmin list
/gravesadmin list <player> (permission exyliagraves.admin.view, players only) opens a screen with
every grave that player has, on every server of the network. The player can be online, offline or on
another server, as long as ExyliaLib knows the name.
| Click | What it does | Needs |
|---|---|---|
| Left | Teleport to the grave, free, ignoring combat and whether teleporting is on. | exyliagraves.admin.view |
| Right | Look inside, protected or not. | exyliagraves.admin.view |
| Shift-left | Hand it back to its owner, after a confirmation. | exyliagraves.admin.restore |
| Shift-right | Remove it and everything in it, after a confirmation. | exyliagraves.admin.remove |
Each row's click hints list only what the viewer may do. After a confirmation, or after cancelling one, staff are taken back to that player's graves.
The screen is lang/<code>/menus/admin/graves.yml, rewritten from the jar on every start and every menu
reload.
Handing graves back
Hand back deletes the grave and gives its items and experience to the owner by id, through ExyliaLib's reward store: straight into their inventory when they can take it, otherwise on their next join, on any server. Staff read "Grave handed back to Steve."
/gravesadmin restore <player> (permission exyliagraves.admin.restore, players only) does it for every
grave the player has, on every server, after one confirmation: "Hand 3 grave(s) back to Steve?" The
answer counts the graves this call actually took: "3 grave(s) handed back to Steve." A grave somebody
else took in between is simply not counted. With none standing: "Steve has no graves standing."
Removing a grave
Remove deletes the grave and everything in it. Nothing is dropped or delivered. The audit log keeps a summary of what it held.
Where the head comes down
A head only ever comes down on the server it stands on. A grave taken from another server is taken down there at once when Redis is configured; without Redis, it stays until somebody clicks it there ("That grave is gone.") or it reaches its expiry. See Network.
Audit log
Every grave goes to ExyliaLib's audit log, read in game with /exylialib logs <player> (or * for
everybody), optionally filtered by plugin and action (permission exylialib.logs).
| Action | When | Recorded with |
|---|---|---|
grave-create | A death made a grave. | The owner, where, and every item. |
grave-collect | The owner collected it. | Every item. |
grave-loot | Somebody else collected it. | Who, the owner, and every item. |
grave-expire | It expired and dropped, or was tipped out by the limit. | A summary of its contents. |
grave-delete | It expired with on-expire: DELETE. | A summary of its contents. |
grave-restore | Staff handed it back. | Who, the owner, and a summary. |
grave-remove | Staff removed it. | Who, the owner, and a summary. |
The summary is the list of stacks and the experience, as text. Only grave-create, grave-collect and
grave-loot keep the items themselves.
Reloading
/gravesadmin reload (permission exyliagraves.admin.reload) reads config.yml, messages.yml and both
menus again. The menus are also reloaded when ExyliaLib itself is reloaded, so a palette change reaches
them. Graves standing are not touched.
Something missing on this page? Tell us on Discord