1.2.0
Compatibility
Changes
EliminationPlus v1.2.0
What's New
Mob Death Toggle
Player deaths caused by mobs no longer trigger any elimination events by default. This means spectator mode, chat messages, title displays, sounds, and Discord webhook notifications are all silently ignored when a mob is the cause of death — keeping your event clean without any manual workarounds.
- Added
/ep mobdeathscommand to toggle mob death triggers on/off at any time - Mob deaths are disabled by default — only player kills trigger elimination events
- The toggle state is saved between restarts (respects the existing
save-statesetting) - Mob death status is now visible in
/ep status
Config
A new mob-deaths option has been added under the toggle section of config.yml:
toggle:
mob-deaths: false # Set to true to allow mob kills to trigger elimination events
Existing configs will automatically use the
falsedefault no manual migration needed.
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:VK30LAwj:9DGv7MBM"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:VK30LAwj:9DGv7MBM"
}

