Tags
Creators
Details
0.5.2
Compatibility
Changes
What's new?
- ModelEngine blueprints can now be used as structure models!
- Combined parts "blade_1" and "blade_2" into "blades" for Windmill
- Changed model config format (your model files will automatically update)
API news:
- ResourceLocation now provides Resource (which contains both File and InputStream) instead of InputStream
- Added abstraction layer for model parts
- Added RendererConfigLoader registration (for loading models from custom providers)
- Added PlayerStructureInteractEvent event
Important: ModelEngine models can not be used for animated parts of machines YET! I'm working on state-based and multipart models and animation controllers; once that is done, ModelEngine can be used for all machine parts.
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:SNa6VDKR:JGFOoTt2"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:SNa6VDKR:JGFOoTt2"
}

