Tags
Creators
Details
Licensed MIT
Published 3 months ago
Updated 4 days ago
All versions
1.2.0
Release
LexCase 1.2.03 months ago 24
Compatibility
Minecraft: Java Edition
1.21.x
Platforms
Paper
Purpur
Changes
Changelog – v1.2.0 (28.07.2026)
Added
- Added strict configuration validation during startup and reload.
- Added detailed diagnostics for invalid
raritiesand configuration entries. - Added automatic storage backups for
keys.ymlandluck.ymlbefore saving. - Added storage schema versioning with support for future data migrations.
- Added protection preventing players from opening multiple cases simultaneously.
- Added spawn area validation before both case placement and case opening to prevent overlapping structures.
Fixed
- Fixed several issues that could break the automatic case opening sequence.
- Fixed reward finalization edge cases caused by failed visual reveal states.
- Fixed problems related to placing multiple case locations in close proximity.
- Fixed locale configuration defaults and corrected language/fallback order.
- Removed unnecessary development files from release archives.
Changed
- Refactored the case lifecycle into separate services for lifecycle management, visual handling, and reward finalization.
- Improved overall project architecture, making the codebase easier to maintain and extend.
- Updated the README to match the current configuration structure and localization system.
- Improved reward summary output by merging identical rewards into a single message with the total amount for both players and the server console.
- Improved update notifications by migrating them to Adventure Components with clickable links and hover text.
Technical
- Improved configuration safety by preventing invalid case configurations from silently using fallback rewards.
- Improved internal storage reliability and preparation for future database backends such as SQLite.
- Improved maintainability through cleaner service separation and stricter validation flow.
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:voqgWcP0:VlaaXgf6"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:voqgWcP0:VlaaXgf6"
}

