Tags
Creators
Details
Licensed BSD-3-Clause
Published last year
Updated 9 hours ago
All versions
0.0.5-1.21.10
Beta
Odin 0.0.5-1.21.108 months ago 2,451
Compatibility
Minecraft: Java Edition
1.21.10
Platform
Fabric
Supported environments
Client-side
Required content
Any compatible version
Any compatible version
Changes
- Fixed
/catacommand not working when the Inventory API is disabled - Fixed custom-size dungeon waypoints not being placed correctly
- Fixed Starts With Terminal simulator not counting clicks
- Fixed Blue Dragon entity never being detected
- Fixed SuperTall not detecting rotation
- Fixed commands (e.g.
!kick) using your own name instead of the provided target - Fixed invincibility timer not displaying in
HudManagerwheninBossis enabled - Fixed Melody solver not displaying the solution in certain scenarios
- Fixed Mimic sending a “Mimic killed” message when using the Berserker ultimate ability
Improvements
- HUDs no longer render while in F1
- All sound settings now support configurable volume and pitch
- Updated room cores for:
- Banners
- Carpets
- Knight
- Higher Blaze
- Lower Blaze
- Trap
- Pit
- Rare Overgrown
- Three Floors
- Vinny 8-Ball
- Actively dragged panels now render on top in the ClickGUI
- Changed Leap Menu keybinds from corner-based to class-based
- Reworked Simon Says solver to properly handle skips
- Updated Quiz solver answers
- Reduced overall performance impact when using the mod
Additions
- Added Iris compatibility for 3D rendering
- Added BetterPartyFinder module (auto-kick and auto-stats)
- Added Croesus module to display profit from dungeon chests
- Added auto-draft to Puzzle Solvers
- Added Speed HUD to the PlayerDisplay module
- Added MageBeam module
- Ported additional RenderOptimizer settings from 1.8.9
- Added Room Secrets HUD under the MapInfo module
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:jJJLywXp:LkrTP870"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:jJJLywXp:LkrTP870"
}

