Tags
Creators
Details
2.3.5
Compatibility
Changes
-
Added a new config option that allows using the
/killcommand to kill players with the KILL_PLAYER effect as that's more consistent across different server software than using the API -
Added meta effects WHEN_DAMAGED & WHEN_HEALED. These allow triggering effects only when conditions are met due to the player taking damage or regenerating. For example,
when_damaged/sound/minecraft:entity.bogged.hurtateffects.BODY.INTERMEDIATEwould trigger the sound when the state of your body changes from NEARLYFULL to INTERMEDIATE (damage), but NOT when it changes from DAMAGED to INTERMEDIATE (regeneration). -
Categorized effects into persistent, one-time and meta effects
-
Improved effect keyword matching to allow case-insensitive identifiers
-
Updated validation methods to reflect the above
-
Corrected config comments
Optional dependencies
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:DwIZUWS0:cIKu7S0D"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:DwIZUWS0:cIKu7S0D"
}

