Tags
Creators
Details
Licensed MIT
Published 3 months ago
Updated 4 days ago
All versions
1.5.0
Release
LexCase 1.5.0last month 28
Compatibility
Minecraft: Java Edition
1.21.x
Platforms
Paper
Purpur
Changes
Changelog – v1.5.0 (18.09.2026)
1.5.0
Reliability
- Added persistent pending-reward delivery for failed/offline/full-inventory item rewards and failed command rewards.
- Isolated reward delivery errors per roll so one broken reward does not stop subsequent rewards.
- Added immediate durable flush when a pending reward is queued.
- Added safe
/lc reloadsemantics that preserve active sessions by default and an explicit/lc reload forcepath. - Made key consumption exact/atomic for normal case openings and hardened key arithmetic against integer overflow.
- Hardened reward-weight arithmetic against integer overflow.
Player experience
- Added
/lc keys [ID]. - Added
/lc rewards. - Added
/lc history [ID]. - Added persistent recent case history.
- Added join-time retry for pending rewards.
Admin experience
- Added
/lc status. - Added
/lc health. - Added pending-reward count to the dashboard.
- Added rarity pagination and editable numeric rarity tiers.
Integrations
- Added PlaceholderAPI placeholders for case-specific keys/open counts, total opens, Luck values and pending rewards.
- Improved the Modrinth update checker to consider only listed release versions compatible with Paper/Purpur and the current Minecraft major/minor series.
Data and migration
- Added schema-versioned
history.ymlandpending-rewards.ymlfiles. - Added atomic write + backup handling for the new files.
- Added a one-time 1.4.x → 1.5.0 startup migration marker.
- Added automatic timestamped pre-migration backups with SHA-256 manifests.
- Added protection against starting on a newer unsupported LexCase data schema.
- Existing 1.4.x key/luck data remains in its compatible schema; no destructive conversion is performed.
Optional dependencies
Any compatible version
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:aphtqpdz"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:voqgWcP0:aphtqpdz"
}

