Tags
Creators
Details
Licensed MIT
Published 4 years ago
Updated 2 days ago
All versions
1.1.5
Release
1.1.52 days ago 19
Compatibility
Minecraft: Java Edition
1.12.2
Platform
Forge
Supported environments
Client and server
Changes
v1.1.5
Additions
- Added spring bone colliders.
AzSpringCollideris a sphere or capsule attached to a bone, positioned in Blockbench pixels from the bone's pivot, that follows the bone's animated pose. Spring chains can't pass through them, so tails, ears and capes swing around the body instead of through it. One collider can be shared by several chains. - Added
AzSpringBone.Builder#colliderto give a chain its colliders,#radiusfor how thick the chain is, and#groundto keep the chain above the entity's feet (or the model's origin for items and block entities).
Fixes
- N/A
Changes
- Spring bone chains now bend and whip. Each joint springs towards where the animation puts it relative to the joint before it, so lag builds up towards the tip; before, every joint lagged by the same angle and chains swung as one stiff piece.
Developer Notes
- Because each joint now follows its parent, a given stiffness makes chains curl more than before. Chains tuned for the old behaviour may need a higher stiffness: around
0.3to0.5suits tails. - Collisions are resolved at the chain's joints. A collider thinner than the distance between two joints can slip between them, so keep colliders at least that thick or add some
radius. - With a
radius, a chain stays above the ground and outside colliders, but can settle partway into its own thickness. - A collider on a bone the model doesn't have is skipped. Don't put a collider on one of the chain's own bones, or overlapping the chain's animated pose, or the chain is always being pushed out and never settles.
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:57rbMw4h"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:7zlUOZvb:57rbMw4h"
}

