Tags
Creators
Details
Licensed LGPL-3.0-only
Published 3 years ago
Updated 2 weeks ago
All versions
5.12.0+mc1.19.2
Release
5.12.0+mc1.19.23 years ago 16.5K
Compatibility
Minecraft: Java Edition
1.19.2
Platform
Fabric
Supported environments
Client-side
Server-side
Client and server
Changes
Depending on the size of this release, there may be a human-readable changelog available on the wiki page.
Changes since 5.11.1+1.19.2
- Update for 1.19 model data manager changes - embeddedt
- Avoid refresh loop if no model data needs refreshing - embeddedt
- Do not actually load all models in replaceAll, use clever trick instead - embeddedt
- Slightly optimize entity capability retrieval - embeddedt
- Suppress mixin forceload logging when clear_mixin_info is on - embeddedt
- Bump Fabric Loader - embeddedt
- Update MixinExtras - embeddedt
- More ClientOnlyMixin - embeddedt
- Mark WorldSelectionList mixin as client-only - embeddedt
- Shadow annotations project so they are in the production jar - embeddedt
- Use correct comment style - embeddedt
- Generate config options from both 'mixins' and 'client' keys - embeddedt
- Apply excludedTaskNames in the testmod subproject rather than globally - embeddedt
- Eliminate extraneous casts (#327) - Fury_Phoenix
- Generate mixin configs automatically using custom AP (#305) - Fury_Phoenix
- Disable dynamic DFU when Litematica is installed - embeddedt
- Prevent mod mixins from applying if there is a Forge loading error - embeddedt
- Only call put on the model map if the replacement model is different - embeddedt
- Make replaceAll implementation more robust, add warning - embeddedt
- Track duration of model bake events when dynamic resources is enabled - embeddedt
- Add Mekanism to model bake event helper - embeddedt
- Support replaceAll on the wrapping model registry - embeddedt
- Make handlers not static - embeddedt
- Disable ModelDataManager fixes if Rubidium is installed - embeddedt
- Update mixin for 1.19 model data changes - embeddedt
- Suppress mixin remap error - embeddedt
- Fix some concurrency issues in Forge's ModelDataManager - embeddedt
- Remove testmod genSources task (#333) - Fury_Phoenix
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:nmDcB62a:2HMvqcxJ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:nmDcB62a:2HMvqcxJ"
}

