Tags
Creators
Details
5.0
Compatibility
Changes
ETF 5.0 is a massive rework of the code, ETF is now almost an entirely different mod in its application from what v4.5 was. It should now universally affect every entity and entity render feature.
- the
blocksproperty now again additionally checks the block below block entities differing from OptiFine's behaviour - all entities have enchanted overlay support via "_enchant.png" just like emissives with "_e.png"
- much improved and more helpful right click debug printout
- all possible texture variants are now preloaded on the first instance of a texture being used.
- texture variation is now implemented at the creation of entity render layers allowing all entity textures and features to be modified by ETF
- emissive rendering now occurs within the normal rendering of all models
- fixed entity spawn conditions not saving for all non update-able properties (e.g. the heights property would not always save the entities original spawn height in v4.6)
- fixed the ETF & EMF config screen getting faded black in recent versions
- removed iris z-fighting fixes for everything except armor emissives as they don't appear to be needed anymore
- several changes and optimizations that are not worth listing.
- Added a new config screen category
Debug settings. the debug right click option is now here. the log texture creation setting is now here. - added a new debug button in the debug settings screen that will print ALL currently cached ETF texture data to the log, details of every known texture and every variant, as well as telling you which textures can and cannot be varied. for example elytra.png shows up in the list of textures that can be varied with random entity rules ;)
- removed the ETF cape skin feature, it was fun working with putting a cape inside the skin texture, but it added quite a lot of overhead, when the minecraftcapes.net mod is just more effective. With this removed I plan to add support for player skin feature emissives in whatever cape texture is being used at a future time. Which will be more freeing than only applying skin feature emissives to etf loaded capes
- fixed for sodium 0.5.4
removed features due to them now being possible, and preferred, via EMF
- removed elytra thickness tweak feature
- removed async elytra feature
- removed lectern book unique texture feature
- removed piglin ear model visibility feature
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:pwgniYj5"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:BVzZfTc1:pwgniYj5"
}![[ETF] Entity Texture Features](https://cdn.modrinth.com/data/BVzZfTc1/af683d206d50b05258d865b0d6e4aa2f2cee12f2_96.webp)

