Tags
Creators
Details
Licensed MIT
Published 4 years ago
Updated 2 days ago
All versions
3.1.21
Release
azurelib-neo-1.20.1-3.1.21.jar2 weeks ago 272
Compatibility
Minecraft: Java Edition
1.20.1
Platforms
Forge
NeoForge
Supported environments
Client and server
Changes
v3.1.21
Additions
- Added separate first-person animators for items. Item renderers built with
useSeparateFirstPersonAnimator()give the first-person hands their own animator, so first person and third person can play different animations on the same item stack at the same time (for example, an aimed fire in first person while other players see a hip fire). - Added
AzCommand#sendForItemFirstPerson,AzCommand#sendForItemThirdPersonandAzCommand#sendForItem(Entity, ItemStack, AzItemAnimatorView)to play a command on only one view.
Fixes
- N/A
Changes
AzCommand#sendForItem(Entity, ItemStack)now plays on every animator the stack has. For renderers that don't use a separate first-person animator this is the same single animator as before.
Developer Notes
- Added
AzItemAnimatorView(DEFAULT,FIRST_PERSON). While an item renders, the view for its display context is the current view on the render thread, soAzAnimatorAccessorlookups on anItemStackduring rendering (render layers,AzProvider, custom pipeline code) return that view's animator. Outside of rendering they return theDEFAULTanimator. - Added
AzItemRendererConfig.Builder#setAnimatorViewProvider(Function<ItemDisplayContext, AzItemAnimatorView>)for custom context-to-view mappings.AzItemRendererConfig#animatorView(ItemDisplayContext)returns the view used for a context. AzIdentifiableItemStackAnimatorCachenow stores animators per view. The existingadd(ItemStack, AzItemAnimator)andgetOrNull(UUID)still useDEFAULT; new overloads take anAzItemAnimatorView, andforEach(UUID, AzItemAnimatorView, Consumer)runs on one view or, withnull, every view.ClientUtils#getCurrentAnimationControllerand#getCurrentAnimationTickread theDEFAULTanimator when called outside of rendering. To read the first-person animator, useAzIdentifiableItemStackAnimatorCache.getInstance().getOrNull(uuid, AzItemAnimatorView.FIRST_PERSON).AzItemStackDispatchCommandPackethas a new optional view field, which changes its network format. Clients and servers must run matching AzureLib versions.
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:cZ280Dz7"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:7zlUOZvb:cZ280Dz7"
}

