VGRAVES
Features
This page focuses on what VGraves can do in practice: reclaim methods, GUI flow, storage, integrations, cleanup behavior, and developer-facing extension points.
Reclaim Modes
- Ticket reclaim restores a grave without charging currency and consumes a ticket usage.
- Currency reclaim supports fixed or calculated pricing, optional balance verification, and refund logic if restore fails after withdrawal.
- Give up dissolves the grave, drops saved contents at the death location, and removes the stored entry.
Storage and Lifecycle
Storage backends
LOCALstores one JSON file per player.MYSQL,MARIADB, andH2are supported through HikariCP.- The SQL backend uses a relational layout and supports a configurable table prefix.
Expiration lifecycle
- Every grave has an expiration timestamp.
- Expired graves can be processed on startup, repeating cleanup, and on load.
- Configured actions are
DELETEorDROP.
Integrations and Runtime Behavior
PlaceholderAPIdrives balance lookup, optional placeholder replacement, and plugin expansions.WorldGuardadds region-aware death handling.HeadDatabasesupportsHDB-<id>materials in GUI configs.- Debug mode adds detailed save/load and GUI logs.
- The plugin can auto-merge missing config keys on startup or reload.
Developer Extension Points
- Public API access through Bukkit
ServicesManagerorVGraves.getInstance().getApi(). - Custom events for grave creation, claim, give-up, expiration, removal, and ticket changes.
- Manager and helper accessors for deeper integration with runtime systems.