Tags
Creators
Details
Licensed MIT
Published 2 years ago
Updated 7 months ago
All versions
1.4.0-beta+1.21.10
Beta
[1.21.10] Accessories [Fabric] - 1.4.010 months ago 8,545
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.10
Platform
Fabric
Supported environments
Client and server
Required content
Any compatible version
Any compatible version
Changes
Update to Minecraft 1.21.10 and adjust API with recent rendering changes
Fixes:
- Extra Data for unique slots properties were not sync to the client leading to issues
Changes:
- Adjust dump commands to give more useful information
- Add ability to set custom default values for accessory screen
- Add ability to open creative screen instead of accessories while in creative mode
API:
- Accessory Renderers now have a dedicated
AccessoryRenderStateused to store info unpacked for the given stack used to render later and general state setup for the given equipped accessory to prevent collisions. - Renders now have central
shouldRendercheck used for checking if the given accessory should render in general. If you want to check for if something should render in first person, useAccessoriesRenderStateKeys.ARM - Remove deprecated methods for translations to specific model parts
- Remove unused z-index of screens using owolib
- Disable Data driven rendering functions ability to render using delegate renderer for the time being
- Adjust setup to run using
AccessoriesRenderStateKeys.setupStateForAccessoriesand only usecreateRenderStatefor setting up needed state for rendering accessories - Rework EndecDataLoader for changes to resource loader registration on fabric and fix issue with registry existing after reload
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| accessories-fabric-1.4.0-beta+1.21.10-sources.jar | Unknown | 662.65 KiB |
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:jtmvUHXj:RIa8JoNX"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:jtmvUHXj:RIa8JoNX"
}

