Tags
Creators
Details
0.6.4
Compatibility
Changes
Updated to 1.19.4
More parities with Forge Rendering API (Multipart Models, lightning in BlockRenderer, correct ModelData collecting in ChunkRenderRebuildTask, fixed overlay sprites in FluidRenderer)
Fixed broken animations on any texture
Fixed crash when disabling "Animate Only Visible Textures" feature
Fixed memory leak
Added optimized cloud rendering
Improved the performance of special effects, such as the enchanted item glint (up to 300% faster.)
Improved the performance of mob and block entity rendering (up to 20% faster.)
Improved the performance of chunk rendering by exchanging a small amount of memory for a reduced number of draw calls (up to 10% faster.)
Fixed a memory leak which would cause copies of chunks to remain in cache even if they were no longer needed.
Fixed a problem where animated textures which used interpolation would not have their alpha channel handled correctly.
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:4ZqxOvjD:lCbMhmSa"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:4ZqxOvjD:lCbMhmSa"
}
