Tags
Creators
Details
Licensed LGPL-3.0-only
Published 3 years ago
All versions
0.RC.1
Beta
[EMF] Release Candidate 13 years ago 1,625
Compatibility
Minecraft: Java Edition
1.20–1.20.1
Platforms
Fabric
Quilt
Supported environments
Client-side
Required content
Changes
RC-1
- OptiFine CEM appears to be officially solved in EMF and seems to be fully working for almost every single use case :)
- large rework, reimplementation, and internalisation of animation code and model variant checking. preventing all occurrences of animation de-sync and fixing animations for all modded/replaced entities/models and block entities.
- various stability fixes to model variants including texture support.
- block entities fully supported (expect a few missalignments due to possible OptiFine part name differences, report these if you can ,
e.g. lectern and enchating table books might be swapped) - physics mod compat can now choose to try render the vanilla model parts or the custom EMF model parts
- should no longer cause
part not foundcrashes or model failures - reduced the log message length of model loading errors
- fixed emf/ & mobName/mobName directory issues
- animations now support model part name hierarchy as in OptiFine. i.e
left_arm:hand:finger1works to separate partfinger1in theleft_armmodel group from theright_armone - warning structure added to detected model overrides prompting to disable setting if it crashes or to warn users of models modified by other mods
- added OptiFine name format support for all previously missing entities including sniffer and camel and block entities
- added support for render variables in animations
e.g. render.shadow_size - expanded animation model variable support to block entities, seemingly matching OptiFines output for these.
- block entity animations support variables "var.???"
- added various render modes for custom parts,
NORMAL, GREEN FLASHING, WIREFRAME, OFF, will not affect vanilla parts. - so much more i've probably forgotten some.
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:33ddTlVK"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:4I1XuqiY:33ddTlVK"
}![[EMF] Entity Model Features](https://cdn.modrinth.com/data/4I1XuqiY/6e5bbd0d06b1741bfdab6c0cfab6de8fdaf0064c_96.webp)


