Links
Tags
Creators
Details
26.1.2-0.1.9
Compatibility
Changes
The only user-facing change is a minor bugfix - flowing fluids now correctly emit light.
There was also some behind the scenes refactoring; we're using NeoForge attachment synchronization again (with a custom sync handler to cut down on packet size in chunks with large amounts of logged blocks). This may have a small effect on performance, or cause/fix sync bugs we're currently unaware of.
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:uCiJe7yI:9f4ASEBN"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:uCiJe7yI:9f4ASEBN"
}

