Tags
Creators
Details
Licensed MIT
Published 2 years ago
Updated 10 months ago
All versions
1.8
Release
LazyChests 1.810 months ago 243
Compatibility
Minecraft: Java Edition
1.21.x
1.20.x
Platforms
Bukkit
Paper
Purpur
Spigot
Changes
Changelog
Added
- Admin GUI to view all players with Lazy Chests (online and offline)
- Admin GUI to view all Lazy Chests owned by a selected player
- Pagination support for player and chest list GUIs
- Teleport and inspect actions for Lazy Chests via admin GUI
- Persistent lifetime earnings tracking per Lazy Chest
- Earnings display directly in the Lazy Chest inventory title
- Permission-based Lazy Chest limits, including unlimited access
- New permissions for admin listing, teleporting, and inspecting
/lazychest listcommand to open the admin Lazy Chest GUI/lazychest reloadcommand to reload configuration and prices/lazychest pause <player>command to pause selling for a specific player’s Lazy Chests/lazychest resume <player>command to resume selling for a specific player’s Lazy Chests/lazychest pauseallcommand to pause selling for all Lazy Chests/lazychest resumeallcommand to resume selling for all Lazy Chests- Improved
/lazychest give <player>command handling
Changed
- Improved teleport positioning to place admins safely in front of chests
- Refactored selling logic to support reload-safe task handling
- Improved sell broadcast formatting for clarity and accuracy
- Refactored core systems into dedicated managers for maintainability
- Improved handling of offline player data in admin tools
Fixed
- Inventory interaction issues caused by overly aggressive event cancellation
- Incorrect sell message totals and currency formatting
- Issues with chest title updates not reflecting live earnings
- Potential chunk loading issues during automated selling
- Cleanup of Lazy Chests that no longer exist
- Minor edge cases related to hopper input and chest access validation
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| sourcecode.zip | Unknown | 21.19 KiB |
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:oYqTARbV:zq1Rcb1R"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:oYqTARbV:zq1Rcb1R"
}

