
LootLedger
LootLedger tracks every container interaction in your world. See who opened a chest, what items were added or removed, and when it happened, in singleplayer and multiplayer. Simply open any container and click the book icon to view its full history.
Links
Tags
Creators
Details
1.0.5
Compatibility
Required content
Changes
LootLedger v1.0.5 — Patch Notes
New: Configurable Entry Limit You can now configure how many log entries are stored per container. Open the settings via the new ⚙ button in the Container History panel and choose between 32, 64, 128 (default), 256, or Unlimited. Selecting "Unlimited" will display a warning about potential memory usage.
Multiplayer Permissions
- On servers, only operators can change the entry limit. The setting applies globally to all players.
- Non-operator players can view the current setting but cannot modify it. A subtle note indicates the value was configured by a server operator.
- In singleplayer, the setting is always editable.
UI Improvements
- Added a ⚙ settings button to the Container History header.
- Scroll buttons now display ▲/▼ arrows instead of A/V.
- The current entry limit is displayed in the sub-header bar (e.g. "Limit: 128").
- An entry counter is now shown at the bottom of the panel (e.g. "1-8 / 50").
New Mod Icon
- Updated the mod icon with a new custom design.
Technical
- Default max entries increased from 50 to 128.
- Entry limit is saved per world and persists across restarts.
- Config is synced to all players on join and on change.
- Fully backwards-compatible with existing world saves.
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| lootledger-1.0.5-sources.jar | Sources jar | 1.55 MiB |
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:cksyM3CQ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:I73SkmZm:cksyM3CQ"
}
