GravesEpic — Death Graves, Holograms & GUI

What Is GRAVES EPIC?

When a player dies, GravesEpic stores their inventory, armor, off-hand and XP in a grave at the death location. A floating player head and hologram mark the spot — no map blocks placed by default (stand-only mode).

Players recover loot by right-clicking the grave or using /grave recover. Staff and admins get tools to inspect and manage graves.

At a Glance

• Author: Lewt_
• Languages: 13 built-in (en, es, pt, fr, de, it, ru, pl, nl, tr, ja, zh, ko)
• WorldGuard: Optional soft hook (disable graves in regions)
• API: GravesEpicAPI via Bukkit ServicesManager
• Album: Screenshots

Important — Read Before Installing

• Changing language (language: in config.yml + /grave reload) overwrites config.yml and messages.yml with the JAR pack for that language. Back up both files before switching.
• Default lock: graves are private for 30 seconds (unlock-seconds). Only the owner can open them until the timer ends.
• Max graves per player: default 6 (max-graves). Oldest grave is removed when the limit is exceeded.
• Auto cleanup: graves expire after 120 minutes by default (auto-delete-min).

How It Works

1. Death → grave created

• Loot and XP are saved — vanilla drops are cleared
• Floating skull + hologram spawn at a safe spot (void, water, stacking supported)
• Chat message with coordinates + hint

2. Hologram & lock timer

• Shows owner, grave ID, item count, XP, and lock status
• Live countdown until the grave opens to everyone
• Denied access feedback: sound, particles, action bar (all configurable)

3. Recovery GUI

• Right-click the grave or use /grave recover [id]
• Take items slot-by-slot or Collect All
• Recover stored XP with one click
• Grave overview panel (owner, ID, contents, access status)

Commands & Permissions

Command	Permission	Description
/grave list	—	List your active graves
/grave recover [id]	graves.recover (default: true)	Open a grave remotely
/grave staff list <player>	graves.staff	Staff: list player graves
/grave staff open <#id>	graves.staff	Staff: open a grave GUI
/grave delete <player>	graves.admin	Delete a player's graves
/grave deleteall	graves.admin	Delete every grave on the server
/grave toggle [on|off]	graves.admin	Enable/disable new grave creation
/grave reload	graves.admin	Reload config and messages

Alias: /graves. Subcommand aliases can be translated in messages.yml (command-aliases).


Configuration Highlights

Everything is editable in config.yml and messages.yml:

• max-graves — graves per player (default: 6)
• unlock-seconds — private lock duration (default: 30)
• auto-delete-min — auto-remove old graves (default: 120)
• grave-placement — stand-only (default) or block mode
• world-mode — all / whitelist / blacklist worlds
• platform-block — void platform material (default: CRYING_OBSIDIAN)
• GUI slots, hologram layout, sounds, particles — fully configurable
• Permission node names — perm-recover, perm-admin, perm-staff

13 Languages

Set in config.yml:

Then /grave reload (or restart). Back up config.yml and messages.yml first.

Code	Language
en	English
es	Spanish
pt	Portuguese
fr	French
de	German
it	Italian
ru	Russian
pl	Polish
nl	Dutch
tr	Turkish
ja	Japanese
zh	Chinese
ko	Korean

Public API

Other plugins can hook via ServicesManager:

Use /grave toggle off or the API to disable graves during events (tournaments, minigames, etc.).


Installation

1. Drop GravesEpic-1.0.0.jar in plugins/
2. Set language: en (or your language) in config.yml before first run if needed
3. Restart the server
4. Edit plugins/GravesEpic/config.yml and messages.yml
5. /grave reload after changes

Requirements: Java 17+, Paper/Purpur/Spigot 1.20+ (legacy 1.20/1.21) or 26.x. WorldGuard optional. Not supported below 1.20.


FAQ








Test Server

See GravesEpic running on a live network:

• Survival RPG with custom graves system
• Spanish UI available (language: es)

Support

Use the Discussion section. Include server version, Java version, platform (Paper/Purpur/Spigot), and steps to reproduce.