1.2
Compatibility
Changes
Changelog
All notable changes to LootrPlugin will be documented in this file.
The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.
[1.0.0] - 2026-02-09
🎉 Initial Release
✨ Added
-
Core Functionality
- Per-player unique loot system for structure chests
- Automatic detection of vanilla loot table chests (temples, dungeons, ancient cities, etc.)
- Virtual inventory system — each player has isolated loot
- Persistent data storage (YAML-based)
- Auto-save system (configurable interval, default 5 minutes)
-
Protection System
- Break protection with admin double-confirm (must break twice within 3 seconds)
- Explosion protection (creeper, TNT, bed, respawn anchor)
- Hopper extraction protection
- Piston push/pull protection
-
Visual Features
- Particle effects on unopened chests (configurable type)
- Option to show particles only on unlooted chests
- Sound effects on chest open/close
-
Admin Tools
/lootr help— Command list/lootr reload— Hot-reload config and data/lootr info— View chest information (look at chest)/lootr stats— Plugin statistics (uptime, chests, player entries)/lootr clear <player|all>— Clear loot data/lootr reset— Reset specific chest (everyone gets fresh loot)/lootr list [page]— Paginated list of all registered chests- Tab completion for all commands
-
Configuration
- 20+ configurable options in
config.yml - Per-world disable system
- Customizable messages (all chat messages editable)
- Adjustable particle types and behavior
- Configurable protection features (individually toggleable)
- Bypass permission for admins
- 20+ configurable options in
-
Permissions
lootr.admin— Full accesslootr.break— Break chests with double-confirmlootr.bypass— See vanilla chest behaviorlootr.use— Use Lootr chests (default: true)
-
Data Persistence
chests.yml— Stores registered chest locations and loot table infoplayerdata/<uuid>.yml— Individual player loot data- Async auto-save to prevent lag
- Safe shutdown handling
🛠️ Technical Details
- Package:
com.fetal.lootr - API Version: 1.20+
- Java Version: 17+
- Dependencies: None (standalone)
- File Structure:
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:4ykhAK59:DJdQ2Vqa"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:4ykhAK59:DJdQ2Vqa"
}

