Tags
Creators
Details
Licensed LGPL-3.0-only
Published 3 years ago
All versions
1.1.0
Release
[EMF] Entity Model Features 1.1.03 years ago 88.2K
Compatibility
Minecraft: Java Edition
1.19.2
Platforms
Forge
NeoForge
Supported environments
Client-side
Required content
Changes
1.1.0
- fixed
rule_indexvariable using the wrong value - fixed
random()method breaking when used with no args - fixed
Non [a-z0-9/._-] character in pathcrash with modded entities having model id's that do not create valid Identifiers/ResourceLocations - fixed wolf collar models only being separate from the base model if a wolf_collar.jem was present (wolves share their base model with the collar renderer in vanilla)
- fixed
!boolean inverting not applying tovarbvariable booleans - added
keyframe()&keyframeloop()animation methods to simplify keyframe format animations, the format iskeyframe(k, a, b, c,...)withkbeing the linear progress of the keyframes (typically a timer), and all further values being the individual keyframes value. In practise, k=0 will output the value of keyframea, k=1 will output the value of keyframeb, and k=1.5 will give a linear output halfway betweenb&c. In effectkis the timer playing through the keyframes, with each keyframe value at a whole number withabeing 0.keyframeloop()will wrap around from the final frame back to frameaand so on askincreases past the last frame. whereaskeyframe()will only display the last frame for higherkvalues.kwill be treated as a positive number even if negative. - fixed
print()&printb()methods only printing once if the x value had logically resolved to a constant - now requires
ETF 4.6.1or higher - added
nanvariable that resolves to Float.NaN in runtime mostly for debugging purposes, it being used should make any math function/equation give its failure outcome.
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:4I1XuqiY:IvKEtlkS"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:4I1XuqiY:IvKEtlkS"
}![[EMF] Entity Model Features](https://cdn.modrinth.com/data/4I1XuqiY/6e5bbd0d06b1741bfdab6c0cfab6de8fdaf0064c_96.webp)


