Tags
Creators
Details
1.2.1
Compatibility
Changes
fixing these two issues:
"Server & client only sync on login, and they only sync within a radius - if the player were to move to a different location that they already have voxy LODs for then the issue still persists (server does not request a new manifest based on the player moving around).
If you use a mod like Chunky to generate chunks outside of player render distance, then the hashes can get corrupted for the client - causing holes in the world that persist beyond reconnecting, requiring them to delete their clients .voxy folder to re-pull everything."
thanks @travismlee on github.
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:fNtGd1cx:Y4Ajdttu"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:fNtGd1cx:Y4Ajdttu"
}

