1.2.2-fabric+1.21
Compatibility
Changes
2025/02/17 1.2.2
Corrected errors in the document and added some missing information
*Added Item Component mapperplugin:attack_event mapperplugin:use_event
*Fixed In Custom HUD File , optional filling may result in errors, ItemPart add custom item model data, and fixed LayerDrawComponent animation
*Fixed mp:animate unable to stop animation issue
*Fixed mp:pose server and client un-synchronized issue
*Fixed GameRule playerDamageInvulnerable change invalid issues
*Modify simplified particles mapperplugin:abstract_custom_particle parameter requirements, there are default values now
*Modify recode mp:particle sphere algorithm for graphic generation
*Removed mp:nbt ,then /data can merge player data
*Removed mp:ride ,then /ride allow riding players (but there is still an un-synchronized issue when canceling riding)
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:buDSWrhP:Pz6aWkjw"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:buDSWrhP:Pz6aWkjw"
}

