Links
Tags
Creators
Details
0.1.4
Compatibility
Changes
Fixed crash on dedicated servers. Transitioned to a (minor) abuse of AuxiliaryLightManager, which seems to have resolved lighting issues on server (re)start. Let me know if there are any lingering lighting issues.
Improved logging of flowing fluids (blocks are no longer deleted; fluids can now flow into and between logged blocks) when enabled in config. However, the issue with delayed visual updates has proven difficult to resolve. For now, you can return to menu and reopen the world if you want to see the correct light levels; just placing a block anywhere in the chunk is enough to see the correct fluids. Remember - this is a low priority, WIP, feature. Feel free to submit bugs, but don't expect a quick turn around.
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:IVZOJ4vN"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:uCiJe7yI:IVZOJ4vN"
}

