Tags
Creators
Details
1.6.0
Compatibility
Changes
🚀 LexCase 1.6.0 — Upgrader Update
LexCase 1.6.0 introduces a completely new Upgrader system and expands the plugin with a dedicated risk/reward gameplay mechanic.
🎰 New — Upgrader System
-
Added a new Upgrader subsystem with dedicated core logic and GUI interfaces.
-
Added player-facing Upgrader menu accessible through:
/upgrader/lc upgrader
-
Added configurable ALL IN upgrade attempts.
-
Players can put an item at risk and attempt to upgrade it into a selected target item.
-
Added configurable success chances for individual upgrade options.
-
Added configurable target multipliers such as
1.5x,2x,5x,10x, etc. -
Added configurable upgrade costs:
FREEMONEYITEMS
-
Added Vault integration for money-based Upgrader costs.
-
Added support for multiple item costs per upgrade option.
📈 Automatic Upgrade Targets
- Added
upgraders_cost.ymlfor configurable item values. - Added automatic generation of upgrade targets based on configured item values.
- Added automatic multiplier calculation for generated targets.
- Added configurable chance calculation based on target value.
- Added configurable minimum and maximum success chances.
- Added support for custom Upgrader definitions alongside automatically generated ones.
🎰 New Roulette Animation
Replaced the previous Upgrader presentation with a dedicated roulette-style animation.
- Added a high-speed roulette spin with acceleration and deceleration.
- Added multiple configurable full rotations.
- Added dedicated WIN and LOSS zones.
- Added a precision pointer represented by a single visible dot.
- Added a visual circumference around the pointer trajectory.
- Added a central display of the target item.
- Added near-miss handling for failed attempts that stop close to the WIN zone.
- Added configurable final wobble before the result.
- Added final
WIN/LOSEpresentation. - Removed unnecessary intermediate result messages from the final animation.
👤 Player-Only Animation
The Upgrader animation is rendered specifically for the player performing the attempt.
Other players do not see the active Upgrader roulette animation.
This keeps the animation personal to the player and prevents multiple simultaneous Upgrader sessions from appearing visually mixed together.
🔊 Improved Roulette Audio
- Added continuous spin sound during the roulette animation.
- Spin sound frequency dynamically follows the pointer speed.
- Sounds are played more frequently while the roulette is moving quickly.
- Sound intervals progressively increase as the roulette slows down.
- Added dedicated success and failure sounds.
✨ Particle System
-
Added configurable particle detail levels:
LOWMEDIUMHIGH
-
Particle density can now be adjusted according to server performance and visual preferences.
-
Reduced unnecessary particle updates during animation.
-
Optimized roulette geometry rendering to reduce the number of particle operations.
-
Reduced repeated entity and display updates where possible.
🧰 New Upgrader Administration
Added a dedicated administration workflow for Upgraders:
- Upgrader list
- Upgrader editor
- Input item editor
- Upgrade option editor
- Result item editor
- Chance configuration
- Multiplier configuration
- Cost editor
- Animation configuration
- Enable / disable controls
- Custom Upgrader management
⚙️ Configuration
Added dedicated Upgrader configuration options for:
- Automatic target generation
- Item value registry
- Success chance calculation
- Chance limits
- Upgrade multipliers
- Animation duration
- Rotation count
- Particle detail
- Roulette geometry
- Pointer position
- Pointer visual settings
- Spin sound behaviour
- Near-miss behaviour
- Final wobble
- Result display timing
🛠️ Internal Improvements
- Added a dedicated Upgrader service layer.
- Separated Upgrader business logic from GUI and animation logic.
- Added dedicated models for Upgrader definitions and options.
- Added reusable cost and economy services.
- Improved handling of configurable ItemStack-based upgrade results.
- Added additional validation for Upgrader configuration values.
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:ZsJ5HcxP"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:voqgWcP0:ZsJ5HcxP"
}

