Configuration
Grave slots, PvP graves, fallback graves, auto-claim, and visuals/holograms are covered in depth on Mechanics — this page covers everything else in config.yml.
File layout
config.yml # grave slots, PvP/fallback grave, auto-claim, visuals, hologram, sounds, world settings
messages.yml # every player-facing message + prefix
inventories/mainpage.yml, settings.yml, confirm.yml # GUI layouts
playerdata/ # runtime — one file per player, grave/settings data
config-version
config-version — it drives the plugin's own auto-migration when a config's shape changes between updates.Storage save interval
save-interval-ticks: 6000 # 20 ticks = 1s, so 6000 = every 5 minutesHow often dirty player profiles (grave contents, settings, cooldown timers) are flushed to disk. Lower this on a server with frequent unexpected shutdowns if you're worried about losing a few minutes of grave state; the tradeoff is more frequent disk writes.
Sounds
sounds:
grave_open: UI_BUTTON_CLICK
grave_close: UI_BUTTON_CLICKPlayed when a physical grave (fallback or PvP) is opened/closed. Use any name from Bukkit's Sound enum, or none to disable a given sound entirely.
Per-world settings
world-settings:
disabled-worlds: [] # graves fully off — items drop naturally, exactly like vanilla
no-fallback-worlds: [] # slot system still works, but no physical graves ever spawn hereUse disabled-worlds for a world you want completely untouched by this plugin (e.g. a creative or minigame world). Use no-fallback-worlds when you want the grave-slot system active but don't want physical graves cluttering that specific world — if every slot happens to be full there too, items just drop naturally instead.
Reload vs. restart
/agraves reload re-reads config.yml, messages.yml, and every inventory layout file. Visual changes (grave-visual.scale, animation) apply immediately, even to graves that already exist in the world. It does not reload compiled Java — anything changed by updating the plugin jar itself needs a full server restart.