Storage & Database
Ascendra persists all grave data so graves survive restarts and crashes.
Database
- Engine: SQLite.
- File:
plugins/Ascendra/graves.db - Driver: SQLite JDBC, shaded directly into the plugin jar — no external database setup required.
The database stores:
- Active graves — every grave currently in the world, its owner, location, contents, and timers.
- Death history — records of past grave outcomes, viewable via the history GUI.
Backups
The entire dataset lives in a single file (plugins/Ascendra/graves.db). To back it up, copy that file while the server is stopped (or after a clean save).
Inventory Storage Modes
The storage-mode option controls how recovered items are returned to players.
| Mode | Behaviour |
|---|---|
EXACT | Preserves original slot positions — items return to the exact inventory slots they were in at death. |
COMPACT | Fills available inventory slots efficiently rather than restoring exact positions. |
storage-mode: EXACT
- Choose
EXACTfor the most faithful recovery experience. - Choose
COMPACTif you'd rather items always slot into whatever space is free (useful when a player's inventory layout has changed since death).
Death History
Ascendra keeps a record of recent death history, viewable by admins through a GUI:
/ascendra history <player>
This opens a GUI showing recent death history records for the named player. It is a player-only command and requires the ascendra.history permission.
note
Death history is a record of grave outcomes only. Ascendra does not provide separate death logs, obituaries, or item filtering beyond this history view.