Tags
Creators
Details
Licensed MIT
Published 3 months ago
Updated 4 days ago
All versions
1.4.0
Release
LexCase 1.4.03 months ago 135
Compatibility
Minecraft: Java Edition
1.21.x
Platforms
Paper
Purpur
Changes
Changelog – v1.4.0 (03.08.2026)
Added
- YAML remains the default storage mode, with SQLite available as an opt-in path
- Safe locale migration that backfills missing keys without overwriting custom translations
TextDisplay-based holograms to reduce entity load on busy servers- Stacked loot summary output that merges identical drops into one line
- Async export/import/restore flows with GUI progress feedback
- Case templates for cloning full setups, including loot, visual settings, and conditions
- Import/export presets for rarities and loot tables
- PlaceholderAPI support for dynamic server placeholders
- Admin audit log with a config toggle
- Case geometry caching for chest positions, footprint, and space validation
- Performance dashboard panels for active sessions, average session duration, entities per case, and storage size
- Reload duration reporting in localized reload messages
- Backup GUI slot fixes so backup entries no longer overwrite action buttons
Changed
- Storage keeps YAML as the safe default for existing 1.3.0 servers
- Locale handling now merges bundled translations into existing user files instead of replacing them
- GUI text now shows translated messages consistently after reload
- Reward and backup operations now use debounce and async paths where appropriate
- Case editing now supports template-driven cloning and preset-based transfer workflows
- Hologram rendering now uses a lighter implementation for better server performance
- Admin tooling now includes more detailed diagnostics and audit visibility
Fixed
- Locale keys that could fall back to raw IDs during migration
gui.common.yes/gui.common.no/gui.common.true/gui.common.falsefallback handling- Reload language switching so
/lc reloadno longer requires a full server restart - Reward summary localization and stacked loot display
- Backup GUI slot collisions
- Storage-mode and GUI compatibility issues uncovered during build verification
- Several API compatibility issues during the 1.4.0 rollout
Notes
- Paper 1.21.11 and Java 21 remain the target platform
- YAML remains the default storage path for public upgrades from 1.3.0
- SQLite, audit logging, and advanced admin tooling are controlled upgrades rather than forced migrations
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:ALEmSWfM"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:voqgWcP0:ALEmSWfM"
}

