Tags
Creators
Details
Licensed MIT
Published 4 years ago
Updated last month
All versions
3.0.0
Release
fabric 3.0.02 years ago 7,670
Compatibility
Minecraft: Java Edition
1.21.1
Platforms
Fabric
Quilt
Supported environments
Client and server
Changes
v3.0.0
- Rewrite Entity animation system. See guide for converting here: https://moddedmc.wiki/en/project/azurelib/docs/updating/entities
- No longer have to supply a cache.
- No longer have to use a GeoEnity interface.
- Rewrite Item animation system. See guide for converting here: https://moddedmc.wiki/en/project/azurelib/docs/updating/items
- Fixes issue with Item animations not working the first time due to missing NBT tag check.
- No longer have to supply a cache.
- No longer have to use a GeoItem interface.
- "Item" rendering/animating is now considered "ItemStack" rendering/animating.
- No longer register the render in the Item.
- This is done in your clients onInitializeClient for Fabric and NeoForges FMLClientSetupEvent using AzItemRendererRegistry#register.
- Rewrite Block Entity animation system. See guide for converting here: https://moddedmc.wiki/en/project/azurelib/docs/updating/blockentities
- No longer have to supply a cache.
- No longer have to use a GeoEntity interface.
- Rewrite Armor animation system. See guide for converting here: https://moddedmc.wiki/en/project/azurelib/docs/updating/armor
- No longer have to supply a cache.
- No longer have to use a GeoItem interface.
- "Item" rendering/animating is now considered "ItemStack" rendering/animating.
- No longer register the render in the Item.
- This is done in your clients onInitializeClient for Fabric and NeoForges FMLClientSetupEvent using AzArmorRendererRegistry#register.
- Animations are now done fully using a trigger animation call from the Az<Type>Animator.
- New system fixes Animations not firing properly on Items on first use.
- You have to now register your item in your mods onInitialize for Fabric and NeoForges FMLCommonSetupEvent using AzIdentityRegistry#register
- AzIdentityRegistry#register can take 1 item or multiple if you have a lot of item.
- You have to now register your item in your mods onInitialize for Fabric and NeoForges FMLCommonSetupEvent using AzIdentityRegistry#register
- New system fixes Aniamtions not pausing correctly when in singleplayer. (Old system/Geckolib "pauses" it but it still ticks so doesn't hold the animations spot properly)
- New system fixes Animation triggers not working with armors.
- New system shows about a 40% drop in memory usage compared to old systems/Azurelib.
- Move to new Az Naming scheme from Geo
- Fixes crash with Minecolonies when using new render.
Known issues
- PLAY_ONCE animations have an odd bug with bones resetting in between triggers.
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:7zlUOZvb:p96V8u85"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:7zlUOZvb:p96V8u85"
}

