All versions
2.4.2
Beta
Voxy WorldGen 2.4.22 weeks ago 23K
Uploaded by
Compatibility
Minecraft: Java Edition
26.2
Platform
Fabric
Supported environments
Client and server
Required content
Any compatible version
Any compatible version
Changes
- fixed players without the mod getting kicked with invalid player data when joining a neoforge server, the mod is optional now and vanilla clients just don't get lod data
- stopped generating chunks around players who don't have the client mod, no point since they can't render it anyway
- active task count in f3 holds steady near your configured max instead of bouncing between the cap and a low number, load easing is smoothed now
- fixed chunks generating unevenly when lots of players are on (one player used to hog all the work, now it's split fairly)
- fixed catch-up leaving permanent white holes (chunk got marked synced even when it never sent)
- chunk loads no longer spam every player every time, skips people who lack the mod or already have the chunk
- block edits no longer tax every single block change on the server, bails early when no one has the mod
- dirty section backlog is capped now so a redstone/fluid storm can't blow up memory
- block edit resend timing actually uses the update_interval config instead of a hardcoded value
- send queue is capped so a broadcast storm can't grow memory forever
- stopped sending chunks to players who already left or walked out of range
- synced chunks get cleared on dimension change so old stuff doesn't block syncing in the new world
- client ingest sorts once per tick instead of scanning the whole queue every time, way less lag
- when the queue overflows it drops the farthest chunk instead of the oldest
- empty block light is sent as null now instead of a dead 2048 byte array, saves bandwidth
- added a protocol version to the handshake so mismatched versions just don't sync instead of breaking
- fabric client ingest now matches the neoforge design (queued + drained per tick nearest-first)
- you can use config menu on server to edit server config if your op
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:xT0lnNE9:II0QK5sq"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:xT0lnNE9:II0QK5sq"
}

