Links
Tags
Creators
Details
2.2.8
Compatibility
Changes
Changes & Fixes:
-
WorldGuard Integration: Updated WorldGuard flags: SDS_EVENT, SDS_BREAK, SDS_REMOVE will now automatically default to DENY if they are not explicitly set in a region.
-
Advanced Player Drops: Added support for SkinRestorer player head drops.
-
Witch Scrolls: Added a new Weakness effect modifier: weak-duration (How long will the weakening effect last?)
-
Arrow & Projectile Tweaks: Firework Arrows: Slightly lowered the firework spawn height to improve hit accuracy on players. Shocking Skeleton Arrow: Reduced hurt animation.
-
Electricity Shock: Reduced hurt animation.
-
Dangerous Coal: Added support for DEEPSLATE_COAL_ORE.
-
Blood Moon: Added a new Zombie modifier: max-mobs-per-chunk (Modify maximum number of zombies that can be spawned in a chunk?)
-
Meteor Rain: Added new boolean modifier: meteor-crater (create meteor crater or not) crater-recovery (recover terrain after event close) The meteorite crater will now slowly restore its original topography over time. The core will remain deep underground, becoming a small mineral deposit.
-
Zombie Break Block: Fixed an issue where zombies incorrectly throw broken blocks. Added a new Zombie target modifier: max-target-distance (Zombie tracking distance) drop-blocks (Does a block destroyed by a zombie will drop?) drop-remove-interval (How long will it take for the dropped item to disappear?) Improved and adjusted zombie block-breaking logic.
GUI and Commands:
- Monster Editor GUI: Fixed an issue where the egg item did not match the mob type.
- Removed the /sdmob remove command due to duplication with /sdmob delete.
Source code:
- Remove unused class, package.
- Decomposing the heavy logic of the Main class into the Manager classes.
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:6p05TBta:djQca20E"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:6p05TBta:djQca20E"
}

