All versions
2.0-1.21.1
Release
Deathledger 2.05 months ago 49
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.1
Platform
Fabric
Supported environments
Client-side
Changes
DeathLedger Changelog
v2.0
Supported versions: Minecraft 1.21.1 – 1.21.11 (Fabric)
✨ New Features
- Teleport to Death Location — A new button in the death detail panel allows OP players (permission level 2+) to instantly teleport to their death coordinates, including cross-dimension support.
- Restore Items — A new button lets OP players restore all items from a death entry directly into their inventory. Items are placed back into their exact original slots (hotbar, inventory, armor, offhand), so your loadout feels exactly like before you died. Command feedback is automatically silenced during the restore to keep chat clean.
🐛 Bug Fixes
- Fixed deaths below Y=0 not being recorded — Deaths in caves, the deep dark, or anywhere below Y=0 were incorrectly saved as Y=0. The void detection threshold has been lowered from Y=0 to Y=-128, so deaths underground are now recorded at the correct position. Only actual void deaths (below Y=-128) use the last known safe position as a fallback.
⚙️ Changes
- Default keybind changed to
K— The default key for opening the Death Ledger GUI is nowK. - Improved keybind display — The controls menu now shows "Open Death Ledger" under the "Death Ledger" category instead of raw translation keys.
🔧 Multi-Version Support
- Ported to Minecraft 1.21.1 – 1.21.11 with two builds:
deathledger-1.21.1.jar— for Minecraft 1.21.1deathledger-1.21.2-1.21.11.jar— for Minecraft 1.21.2 through 1.21.11
📦 Downloads
| Version(s) | File |
|---|---|
| 1.21.1 | deathledger-1.21.1.jar |
| 1.21.2 – 1.21.11 | deathledger-1.21.2-1.21.11.jar |
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:BwB1DCfk:MqBkdzDp"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:BwB1DCfk:MqBkdzDp"
}

