Tags
Creators
Details
4.3.0.fabric.1.18.2
Compatibility
Changes
[V4.3.0]
Update summary
ETF 4.3 brings with it many fixes and stability issues as well as compatibility features and some long time missing
features.
Most notably ETF's skin features now have full compatibility with the 3D Skin Layers mod and any skin changing mod
as well as fixing a notorious Tinkers construct crash on forge.
Added:
- added Minecart, Boat, Evoker Fang, and Llama carpet texture support
- added an option 'enabled by default' to set ETF to not tamper with any textures that have PBR textures attached, to preserve PBR functionality, only if shader mods are present
- added an option 'enabled by default' to set ETF to not tamper with any textures that has
moremcmeta modanimations, to preserve animation functionality, only ifmoremcmetais present
Changed:
- changed handling of block entity features, should clear up several issues and be very stable compared to before
- skin features rework:
- should now be compatible with most skin changer mods e.g.
diguise-heads,impersonate, orfabric tailor - much faster implementation
- updates the clients skin in game after uploading, so you don't need to restart (doesn't update other players, that still requires a restart)
- should now be compatible with most skin changer mods e.g.
- changed the
[Allow broken texture paths]setting, it can now be set tooff|entities only|all resources, all resources is not recommended - made a few large source code refactors, no functionality change
Fixed:
- fixed
Tinkers constructcrash - fixed
3D skin layers modcompatibility with ETF skin features - fixed skin changing mod compatibility (e.g.
disguise-heads,impersonate,fabric tailor) - fixed updatable properties for additional mob textures, like sheep_fur.png and villager types, not updating if the base texture doesn't
- fixed tooltip lines ignoring line breaks in 1.19.3
- fixed an issue with the
[Allow broken texture paths]setting preventing resource packs with broken paths from loading correctly in 1.19.3 - fixed an issue with chest emissive textures
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:BVzZfTc1:4OthHiGq"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:BVzZfTc1:4OthHiGq"
}![[ETF] Entity Texture Features](https://cdn.modrinth.com/data/BVzZfTc1/af683d206d50b05258d865b0d6e4aa2f2cee12f2_96.webp)

