Links
Tags
Creators
Details
1.0.0-1.21.1
Compatibility
Required content
Changes
Release
Now all basic features which were planned for this mod are finished! 🎉
This release makes use of the Cardinal Components API which improves data handling and network syncing in almost all aspects and potentially opens up mod compatibility if another mod decides to make use of the BodyPart component system.
Oh and those pesky Second Layers of Player Skins? They are fixed too!
Details
- joining and leaving servers respects hidden parts of players
- hidden body parts stay synced, even if the modification happened for other player entities, which were not in tracking range
- Second Skin Layer settings are correctly saved and won't be overwritten by toggling the visibility of Body Parts
- Second Skin Layers of other players won't be tied to client's own layer settings
- general improvements with CCA's Component system targeting data storage, data handling and network handling
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:soaGz3MF:BuDvpJix"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:soaGz3MF:BuDvpJix"
}

