Links
Tags
Creators
Details
1.2.0+26.3
Compatibility
Changes
LootLedger 1.2.0 · Minecraft 26.3
This release brings LootLedger from Minecraft 26.1 to 26.3.
New
- Container break and placement records. Regular container histories now show when a block was broken, removed, or placed. Direct player actions include the player's name. If the cause is unknown, the history says so.
- Private shulker histories per placement. Picking up or breaking a shulker ends its history. A chest or another shulker placed at the same coordinates cannot see its transfers.
- Mod Menu integration. Open Mods → LootLedger → Configure to access the same settings available in-game, plus a shortcut to Minecraft's key-bind settings.
Changed
- Press H inside a supported container to open its history. The configurable shortcut replaces the old book button. Esc returns you directly to the container.
- Redesigned the history screen and added a new in-game icon.
- Improved multiplayer tracking so simultaneous transfers are attributed to the correct player. Double chests now keep separate records for each half, and histories are separated by dimension.
- Added English and German interface translations with automatic language selection.
Upgrading from 26.1
LootLedger backs up the original world log before importing it. Older entries did not identify which type of container they came from, so they appear as Legacy entries only for server operators and the singleplayer host. Entries without dimension data are imported into the Overworld.
On multiplayer servers, update LootLedger on the server and on clients that use the history viewer.
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:I73SkmZm:1tYVY8k4"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:I73SkmZm:1tYVY8k4"
}

