Links
Tags
Creators
Details
Licensed MIT
Published 2 years ago
Updated last week
All versions
26.201.0
Beta
worldweaver-26.201.03 months ago 5,009
Compatibility
Minecraft: Java Edition
26.2
Platform
Fabric
Supported environments
Client and server
Required content
Any compatible version
Changes
Features
- Cross-mod validation: does wover:betterx survive other mods present
- Item tint trait for blocks colorized by a block tint
- Add ToolSlot.SPEAR_SLOT for vanilla's new spear items
- Chiseled bookshelves for wooden block sets
- Shelves for wooden block sets
- Add SyncedRecipes for reading custom recipe types on the client
- Enforce a real client/common source split
Changes
- Item-/BlockModelBindings are only created on a client Datagen run
- Honour level-type on servers, and order biome_data before the Nether preset
- Filter block_properties by namespace
Fixes
- Update AddonSurfaceRuleProvider off renamed dyed-block constants
- Dedicated servers ignored an explicitly chosen level-type
- Runtime biome_tags modifications were invisible to Holder.is(tag)
- EquipmentSet's generic tool item used the tier gate tag as its mining tag
- FoodItemDefinition: stop beforeBuild() from silently overwriting a directly-set FoodProperties
- Only claim the head half of a bed as a villager's home POI
- Migrate legacy generator IDs when importing Worlds Together settings
- Surface testmod did not compile
- Remove the per-process noise cache retired by the NoiseFilter fix
- NoiseFilter reads its noise from the world, not from a static cache
Validation
- ✅ wover-generator-api / BiomesOPlenty + Terralith (BiomesOPlenty-fabric-26.2-26.2.0.0.26.jar, Terralith_26.2_v2.6.4.jar, GlitchCore-fabric-26.2-26.2.0.0.0.jar, TerraBlender-fabric-26.2-26.2.0.0.2.jar, lithostitched-1.7.13-fabric-26.2.jar, tested: gametest+worldgen)
Optional dependencies
Any compatible version
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:RiN8rDVs:55JGg6nL"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:RiN8rDVs:55JGg6nL"
}

