Tags
Creators
Details
All versions
4.2.8-mc26.1
Release
4.2.8 (26.1)4 months ago 8,210
Compatibility
Minecraft: Java Edition
26.1.x
Platforms
Fabric
Quilt
Supported environments
Client and server
Required content
Any compatible version
Any compatible version
Changes
- Bumped Wilder Wild's protocol version to 19.
- Added a config option to toggle whether Azaleas can generate when Bone Mealing a Moss Block.
- The
wilderwild:moss_patch_bonemeal_no_azaleafeature will be used while this option is enabled. - This option is disabled by default as to not break existing farms.
- Added the
block_mossoption to Wilder Wild's mixin config.
- The
- Termite Mounds now only hold a single Termite Swarm at a time.
- Termite Mounds placed by Players could previously hold three Termite Swarms at a time.
- This change should make Termite Mounds more acceptable in terms of game balance and volume/particle count.
- As a result of this change, the
can_spawn_termitesBlockState property has been removed.- The
termites_awakeproperty now takes into account the conditions thecan_spawn_termitesproperty was previously set under.
- The
- Updated and optimized how Termite Mounds sync Termite Swarm data to clients.
- Syncing now only occurs if a Termite Swam was spawned, removed, or had its position/eating state changed.
- Syncing would previously occur each tick while a Termite Swarm was present.
- Significantly reduced the amount of data required to be sent in order to sync Termite Swarm data to clients.
- Syncing now only occurs if a Termite Swam was spawned, removed, or had its position/eating state changed.
- Termite Particles are now created on the client instead of being sent from the server.
- Added the
#wilderwild:cannot_support_upwards_termite_movementBlock tag.- Contains the
#minecraft:inside_step_sound_blocks,#minecraft:replaceable_by_trees, and#minecraft:flowersBlock tags by default. - This tag is used to define which Blocks a Termite Swarm cannot travel upwards into.
- Contains the
- Fireflies now spawn directly from Firefly Bushes when the
Firefly Bush Spawningconfig option is enabled.- Fireflies will spawn in groups of 3-6 when a Firefly Bush is randomly ticked.
- Spawning will fail if:
- The brightness level is higher than 13.
- More than 16 Fireflies are present within 8 blocks of the Firefly Bush.
- More than 4 Fireflies are present within 4 blocks of the Firefly Bush.
- A Player is not present within 24 blocks of the Firefly Bush.
- Removed the
Firefly Bush Swarmsconfig option and merged its functionality with theFirefly Bush Spawningconfig option. - When the config option is disabled, these changes will no longer apply.
- This change was made to both significantly boost performance on lower-end devices, while being more accurate to Vanilla's Firefly particle spawning.
- Fireflies now despawn within 40 blocks of a Player instead of 80.
Optional dependencies
Any compatible version
Any compatible version
Any compatible version
Any compatible version
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:AtHRJSUW:9BVggOkx"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:AtHRJSUW:9BVggOkx"
}

