Introduction
What ExyliaGraves is, what it solves, and how this documentation is organised.
ExyliaGraves gives every death a grave: a player head with the dead player's face, standing where they fell, holding exactly what they dropped. One click on the head hands everything back. It is free and open source, published under the GNU General Public License v3.0 on Modrinth.
It is built so a grave can never duplicate an item. The drops leave the death and go into one database row, and only there; a grave is taken by deleting that row, and only whoever deleted it gets the items. Two players clicking the same head, two servers, an expiry and a staff action racing for one grave: it is handed over once.
It used to be the graves module of ExyliaSurvivalCore. It is its own plugin now, and it keeps the same
table, sc_graves — see Network.
What is included
Where the head goes, one-click collecting, protection, previews, experience, item rules, expiry, limits by rank and the compass after respawning.
The /graves menuEvery grave a player has on every server, with live countdowns and an optional paid teleport.
Staff toolsAnybody's graves from /gravesadmin: look inside, teleport, hand back or remove. Every grave goes to
the audit log.
One table for the whole network, Redis to take a head down where it stands, and contents delivered by player id.
Requirements
| Requirement | Detail |
|---|---|
| Server | Paper 1.21.4 or newer. Folia supported. |
| Java | 21 |
| Required dependency | ExyliaLib — installed automatically when missing |
| Optional dependencies | PlaceholderAPI; an economy (ExyliaEconomy or Vault) only for a paid teleport |
The configuration files, the menus, the database and Redis, the holograms, the reward store that hands a grave's contents over, the offline notices, the audit log and the teleports all come from ExyliaLib. ExyliaGraves is the part that decides what goes into a grave and who may take it.
How to read this documentation
Getting started
Installation, what the first start creates, and a first death to see it working.
Graves
What happens on death, collecting and protection, the /graves menu, the staff tools and running it
on a network.
Reference
Commands, permissions, placeholders, every configuration key and message, and the questions that come up.
Conventions
- Values marked as default are what the plugin writes the first time it starts. If the file already exists, your value is kept.
- Identifiers between
<and>are variables./gravesadmin list <player>means/gravesadmin list Steve. - Times in
config.ymlare minutes as a bare number, or written out:30m,2h,1d. - Colours use ExyliaLib palette tokens (
{primary},{success},{highlight}), so recolouring the server never means editing these files.
Something missing on this page? Tell us on Discord