Tags
Creators
Details
Licensed AGPL-3.0-only
Published 3 weeks ago
Updated last month
All versions
1.0.1
Release
RexGraves 1.0.1last month 185
Compatibility
Minecraft: Java Edition
26.3
26.2
26.1.x
1.21.x
1.20.x
1.19.x
1.18.x
1.17.x
Platforms
Bukkit
Folia
Paper
Purpur
Spigot
Changes
Added
- Storage backends: YAML (default), SQLite, and MySQL
- Periodic autosave (
storage.autosave-seconds, default 30) - Atomic YAML writes (temp file + replace)
blacklisted-death-causes(empty by default)- AxGraves converter via
/rexgraves admin convert axgraves [path]
Performance
- Saves are coalesced into one write per tick and autosave skips when nothing changed
- Grave items are serialized once when they change, so saves no longer re-serialize every item of every grave
- A failed save (e.g. MySQL down) is retried by the next autosave instead of being treated as written
- SQL storage only upserts changed rows and deletes removed ones instead of rewriting the whole table
- Grave tick skips unloaded graves, and holograms/particles only update when a player is within 64 blocks
- Holograms skip MiniMessage parsing and entity updates when their text did not change
- AxGraves convert reads and parses the file async, and no longer force-loads chunks to spawn visuals
/rexgraves admin list <player>scans offline players async- Interacting with non-grave armor stands no longer scans every world
Fixed
- Experience graves now store the player's real total XP (not vanilla death-drop, which is capped at 100)
- Graves stay exactly where the player died (lava, fire, mid-air) instead of being moved to a "safe" spot, which could end up on the Nether roof
- Void deaths place the grave on the same X/Z at the first standable Y above the void
- Out-of-order async saves could overwrite newer grave data with an older snapshot (e.g. restoring already-looted XP/items after a restart)
- Grave GUI changes are saved on every click, not only on close, so a crash with the GUI open cannot duplicate items
- Open grave GUIs are synced and closed on shutdown
- A grave no longer stays locked forever if another plugin cancels opening its GUI
- Duplicate markers/holograms after restarts (visuals are now reconciled when chunk entities load)
- Curse of Vanishing items are destroyed on death like vanilla instead of being stored in the grave
- Items other plugins keep on death (soulbound etc.) stay in the inventory
- XP is not taken into the grave when another plugin keeps the player's level on death
- AxGraves import no longer expires graves instantly (expiry starts from import time)
- AxGraves item decode no longer silently drops every stack
- AxGraves convert on Paper/Purpur 26+ (use ItemStack.deserializeBytes)
- Keep-inventory and disabled-world messages now send on death
- Nearest-grave lookup no longer crashes across worlds
protect-from-explosionsis respected (destroy + drop when disabled)
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:w02ntftQ:5qc1GNBn"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:w02ntftQ:5qc1GNBn"
}

