VZone Plugins/VGraves/Overview

VGRAVES

Overview

VGraves is a Paper plugin that saves a player's inventory state on death and lets that saved state be viewed, reclaimed, managed, expired, logged, and stored through a configurable grave system.

Core Purpose

When a player dies, the plugin can snapshot storage contents, armor, offhand, XP, location, timestamps, and reclaim price. That snapshot becomes a grave entry that can later be inspected and restored through GUI flow instead of fragile text commands.

The plugin is designed around a grave lifecycle: save on death, browse through menus, reclaim with tickets or currency, give up and drop the contents, or let expiration cleanup remove or release the grave automatically.

Player Flow

Saved on death

  • Main inventory, armor, offhand, and total XP are captured.
  • The death world, coordinates, creation time, and expiration time are stored.
  • The reclaim price is calculated or loaded from fixed pricing rules.

Recovered later

  • The player opens /vgraves to see their saved graves.
  • One grave can be opened in detail.
  • The player can reclaim it with currency, a ticket, or give it up and drop the contents.

Admin Flow

  • Admins can open another player's grave list through /vgravesadmin graves <player> or /vgravesadmin open <player>.
  • The admin detail menu supports delete, self-claim, and restore-to-owner actions.
  • Ticket commands let staff add, remove, check, and give physical ticket items.

Requirements and Compatibility

  • Platform: Paper 1.21.x.
  • Java version: 21.
  • Optional integrations: PlaceholderAPI, WorldGuard, and HeadDatabase.
  • Storage backends: local JSON files or SQL through HikariCP.
  • Public API and custom events are available for other plugins.

File Layout

plugins/VGraves/
|- config.yml
|- database.yml
|- plugin.yml
|- guis/
|  |- main.yml
|  |- view.yml
|  |- admin_main.yml
|  `- admin_view.yml
`- lang/
   |- lang_en.yml
   `- lang_hu.yml
The configuration section of this wiki breaks these files down into dedicated pages so users can understand both the runtime role and the key options of each file.
PreviousWelcomeNextFeatures