Tags
Creators
Details
1.1.19
Compatibility
Required content
Changes
1.1.19
MCWIND_PROVIDER_VERSION 11500, was 11400.
One new symbol: mcw_occRegion.
WindLink still requires PlunderEngine 0.1.18. Nothing it calls moved the engine changed underneath it.
Both changes are engine-side - the occupancy producer and the header, both ship in plunderengine.
- The occupancy window stops being a constant that the header and the atlas each hardcode.
mcw_occRegionpublishes its width once a frame and the header reads it, so the volume can be resized while the game runs and every voxel read still lands in the right tile. A pack that never touches it sees the shipped 96 exactly as before, andmcw_readVoxeloutside the window answers unknown as it always did./plunderengine occupancy window <blocks>moves it, 16 to 384, snapped to whole chunks. It does not save on restart. mcw_readAiranswersknown = falsein the Nether, instead of answering "sealed".- So
mcw_caveCalmstops holding Nether foliage at its minimum.
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:9ZhzxPJ0:JVk2Exfy"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:9ZhzxPJ0:JVk2Exfy"
}

