Tags
Creators
Details
Licensed ARR
Published 2 years ago
Updated 2 years ago
All versions
1.0.5
Release
1.20.1-1.0.52 years ago 137
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Forge
Supported environments
Client and server
Changes
- Added a cooldown for the Wilted targeting mobs that attack it. 4 seconds for non-players and 10 seconds for players, the cooldown is overridden if the Wilted is attacked by a player and its current target isn’t a player
- Cats within 50 blocks of the Wilted will now randomly hiss
- Wolves within 50 blocks of the Wilted will now randomly howl
- Tamed Wolves will no longer run away from the Wilted
- Tamed Wolves will now attack the Wilted
- The Wilted can no longer use its break blocks ability if mobGriefing is false
- The Wilted can no longer break blocks with a destroy time equal to or higher than 50
- The Wilted will now add a cooldown to Lava Buckets like it does with light emitting block items
- The Wilted will now add a cooldown to Fire Charges like it does with light emitting block items
- Dispensers with Light Extinguishers blocking them will no longer work
- Light Extinguishers that have extinguished air will now be deleted
- The Wilted will no longer try to extinguish flowing fluids
- Attempted to improve performance of Light Extinguishers by stopping them from performing unnecessary entity behaviours
- Attempted to improve performance of Light Extinguishers by stopping them from rendering if there are other Light Extinguishers on all sides
- Portal travel will now be prevented while the Wilted is active
- The Wilted will now destroy Nether Portal blocks instead of extinguishing them
- The fog is now closer
- Fixed an issue where the fog would be extremely dense if Enlightend was installed
- Fixed a bug where the Wilted wouldn’t spawn on snow layers
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:44mGKYce:gVUcrKox"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:44mGKYce:gVUcrKox"
}

