All versions
1.0+mod
Release
(ST) Graves 1.03 days ago 36
Compatibility
Minecraft: Java Edition
26.3
26.2
26.1.x
Platforms
Fabric
Forge
NeoForge
Quilt
Supported environments
Server-side
Singleplayer
Changes
ST Graves 1.0
âĻ New
- ðŠĶ 3D tombstone â instead of a mannequin and loot carts, dying now leaves one tombstone holding everything, armor and offhand included, with a floating sign (your name, the day, the grave number and how many stacks it still holds) and a thread of souls drifting up from it. One right-click returns every item to its slot, plus your XP; whatever doesn't fit stays in the grave and the compass comes back until it's empty.
- ðĻ 27 styles â the tombstone follows where you died: Overworld biomes, caves, underwater (sea pickles instead of candles), every Nether biome and the End.
ð§ Improved
- Glowing sign â the text is readable even in the darkest cave, and tombstones made by older versions get it too.
- Lighter tick â everything per player now runs in a single pass over the players.
ð Fixed
- Tombstone facing â it now looks the way you were facing, rounded to the nearest quarter turn. It used to always round down.
- Empty graves â dying with an empty inventory and no XP no longer leaves an empty tombstone and a compass.
â ïļ Notes
- Graves left by the previous version keep working and clean themselves up.
- Open the in-game menu with the [Open the menu] button in the welcome message or
/trigger stg_menu set 1; its switch turns graves on or off for the whole server, no permissions needed. - The tombstone model comes from Capupack 1.2 (the zip also carries it); without it graves work the same but show a plain wall block.
- Supports Minecraft 26.1 â 26.3. For 1.21 â 1.21.11 download the other file.
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:9LMsDbdk:8OGjMRBE"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:9LMsDbdk:8OGjMRBE"
}

