Tags
Creators
Details
Licensed LGPL-3.0-only
Published 5 years ago
Updated last month
All versions
4.4.0
Release
Entity Texture Features 4.4.03 years ago 121
Compatibility
Minecraft: Java Edition
1.19.3
Platform
Forge
Supported environments
Client-side
Changes
- full
NBTproperty parity with OptiFine, ETF now parses the examples in this link correctly (https://optifine.readthedocs.io/syntax.html#nbt) - added ETF only
NBT"raw:" syntax variant "print_raw:" which will act just like "raw:" but will also print what that raw value is for testing purposes - added ETF only
NBTproperty syntax which will print the entire entities NBT data to the log, not just the specific compound, if theNBTproperty text starts with "print:", this will not affect the function of text after the "print:" - vanilla texture variants like
wolf_tame.pngwill fall back towolf.propertiesifwolf_tame.propertiesdoesn't exist (this is true for wolf, bee, ghast & strider texture variants) (only for vanilla textures) - the
Blocksproperty now utilizes the full OptiFine blocks syntax[namespace:]name[:property1=value1,...:property2=value1,...]allowing matches such as"blocks=oak_stairs:facing=east,west:half=bottom" - made
Name,Names,BiomesandTeamsproperties more robust and all 3 can now utilise Regex and Pattern not justNames - added support for emissive textures on mob head blocks
- added support for emissive and enchanted skin features on player head blocks (will only work for a player online that you have seen at least once that session, I may expand this in future)
- resolved injection warning on mod load
- improved resource reloading mixin
- altered the livingEntityMixin structure to accommodate plans for
EMF - some API additions for
EMF
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:Jgnmccap"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:BVzZfTc1:Jgnmccap"
}![[ETF] Entity Texture Features](https://cdn.modrinth.com/data/BVzZfTc1/af683d206d50b05258d865b0d6e4aa2f2cee12f2_96.webp)

