Tags
Creators
Details
Licensed MIT
Published 3 months ago
Updated 4 days ago
All versions
1.3.0
Release
LexCase 1.3.03 months ago 29
Compatibility
Minecraft: Java Edition
1.21.x
Platforms
Paper
Purpur
Changes
Changelog – v1.3.0 (31.07.2026)
Added
- Added a new admin GUI workflow for browsing and editing cases.
- Added direct case editor access with Shift + right-click on a placed case.
- Added support for case-specific keys in
/lc givekeyand/lc removekey. - Added a dedicated admin menu entry via
/lc guiand/lc admin. - Added new GUI permissions for admin access and direct editor access.
- Added optional opening conditions that can require a permission to use a case.
- Added
update-checksupport in the main configuration.
Fixed
- Fixed command usage and permissions to match the current case/key workflow.
- Fixed locale handling so translated text is loaded from language files consistently.
- Fixed case storage and runtime data handling for setups, keys, and luck profiles.
- Fixed the public README to reflect the current feature set and command structure.
Changed
- Changed the admin tool layer into a GUI-driven workflow.
- Changed key management from generic player keys to case-specific keys.
- Changed the command structure so key management now includes a case ID.
- Improved configuration organization for cases, rarities, locales, luck, and debug settings.
- Improved update notifications and general release clarity for server admins.
Technical
- Added new GUI infrastructure and editor menus for future admin tooling.
- Expanded project structure with GUI, prompt, and menu listener services.
- Improved maintainability by separating admin tools, menus, and core case logic.
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:kUSyT6it"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:voqgWcP0:kUSyT6it"
}

