Tags
Creators
Details
2.1.0
Compatibility
Changes
🩸 DeathPulse v2.1.0
🆕 Added
-
Config Version Detection System Added a new section named
config-versioninconfig.yml. This section allows DeathPulse to detect the configuration version currently in use. If a server is running the latest plugin version but still uses an older configuration file, DeathPulse will automatically append any missing sections or options to ensure compatibility with newer updates. -
Cause Exclusion Modifier (
::EXCLUDE) Each death type configuration (Ignore,IgnoreDay,Increase,IncreaseDay,Decrease,DecreaseDay) now supports an additional modifier::EXCLUDE. This modifier can be used to exclude certain death causes from a given death type category. Example:increase: cause: - FALL::EXCLUDEIn this case, FALL deaths will be excluded from the “Increase” type handling.
⚙️ Changed
-
Permissions Handling Simplified Internal permission checks have been refactored for cleaner and more efficient logic. This change does not affect existing permission node names and remains fully backward-compatible.
-
Minecraft API Update DeathPulse now officially targets Minecraft 1.21.10 Spigot API. (No functional code changes were required, but this version aligns the build target with the latest server API for improved consistency and future compatibility.)
🧩 Notes
- Existing configurations will automatically be updated with the new
config-versionfield upon startup if missing. - The
::EXCLUDEmodifier provides more granular control over which death causes are handled in each category, offering improved flexibility for custom setups. - This update remains fully backward-compatible with all prior 2.x configurations.
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:mvw3xF8Q:e6k9ru4P"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:mvw3xF8Q:e6k9ru4P"
}

