Tags
Creators
Details
Licensed MIT
Published 6 years ago
Updated yesterday
All versions
2.2.0-a+thermite
Release
Thermite 2.2.0-a3 days ago 345
Compatibility
Minecraft: Java Edition
26.3-snapshot-8
26.2
26.1.2
26.1
Platforms
Fabric
NeoForge
Supported environments
Client-side
Changes
- Fixed digitigrade legs and emissives not honoring skin layers being disabled in the Skin Customization menu
- Common Consumers: This is a breaking change to
EarsRenderDelegatein Common. The following methods have been added:isHatEnabled()ZisLeftSleeveEnabled()ZisRightSleeveEnabled()ZisLeftPantEnabled()ZisRightPantEnabled()Z- No abstract delegates override these methods, as they're important state that doesn't have a reasonable default
- Ports to versions before the Skin Customization menu should return
truefrom all the new methods
- Common Consumers: This is a breaking change to
- Fixed geometry memoization not consistently differentiating between emissive and base layers
- Common Consumers: This is a breaking change to
EarsRenderDelegatein Common:memoizeGeometrynow expects you to check whether or not the delegate has been put in emissive mode, and if so, store the geometry data separately from base data- The
Immediateabstract delegate does this by doubling the size of its backing array and addingGeometryTag.SIZEto the tag if emissive mode is enabled
- Common Consumers: This is a breaking change to
- Reified the meaning of the version number:
API.COMMON.FEATURE-PATCHAPIwill be incremented in the case of breaking changes to theears-apiartifact- If we ever break API, there will be a compatibility layer if feasible, so this is more an indicator that API integrations should be double-checked rather than expecting them to crash the game
COMMONwill be incremented on breaking changes to theears-commonartifact- This is used by third-party Ears ports (e.g. ReIndev, NFC, NSSS, BTW:CE)
FEATUREwill be incremented when new player-visible features are added that modify the skin formatPATCHis a single letter, starting ata, which will be incremented when bugs are fixed without player-visible changes (i.e. does not change the meaning of a feature config or UV mapping)
- Tightened up loader metadata version restrictions
- (Pre-1.8 only) LegacyHelper no longer infinitely retries profile lookup, which would cause log spam when Mojang is down or there is a local connection issue
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:mfzaZK3Z:V171BG0A"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:mfzaZK3Z:V171BG0A"
}

