Tags
Creators
Details
All versions
1.0.0-Beta.10+1.21.10
Beta
1.0.0-Beta.10 for 1.21.10last year 54
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.10
Platform
Fabric
Supported environments
Client-side
Required content
Any compatible version
Any compatible version
Any compatible version
Changes
Added
- Support for 1.21.10 (#271) - celeste
- Note that there are still some known issues with 1.21.10 (especially around slayer highlighting), but things should mostly work fine.
- This update also includes many substantial changes to how world rendering is handled on 1.21.5 and 1.21.8 in order to better support this and future versions; please report any unintended changes from this update!
- Fire overlay tweaks (#288) - nobaboy
- Revert fall damage sound behavior to match 1.8.9 (#295) - celeste
Changed
- Mod API errors have been made to be less noisy by default (#292) - celeste
- Attribute menu quick search now adds Shard to the search query (#289) - nobaboy
/noba filtersnow also acceptsfilteras an alias (#295) - celeste
Fixed
- Hide Armor now works on the player rendered in the inventory on 1.21.8 (#284) - celeste
- The catch timer HUD element should no longer persist when switching lobbies with a bobber still active (#285) - nobaboy
- Invisibug highlight no longer highlights Frog pets (#286) - nobaboy
- Hiding Blessing messages should no longer result in irrelevant error spam (#292) - celeste
- Hypixel's Discord warning message no longer breaks player chat parsing (#291) - celeste
- Rift timer data not being saved (#289) - nobaboy
- Bobber timer no longer incorrectly reveals the fishing bobber's nametag (#271) - celeste
- Diana burrow waypoints now support the new Ancestral Spade upgrades (#295) - celeste
- Proper Diana v2 support is planned in a future rewrite of these features
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:ZrHxHT33:MEhgKPEu"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ZrHxHT33:MEhgKPEu"
}
