Links
Tags
Creators
Details
1.4.1-beta.1
Compatibility
Changes
1.4.1-beta1 Changelog
Added
- Added automated GitHub Actions build and release workflows for Java 25/Gradle builds, tests, verified plugin artifacts, and SHA-256 checksums.
- Added automated tests for leaderboard ordering, TOP mode behavior, Discord message-length trimming, and death-update scheduling.
Changed
- Changed the Gradle project version to
1.4.1as the base version for the1.4.1prerelease/stable series. - Changed
plugin.ymlversion handling so the plugin version is sourced from Gradle during the build. - Pinned the Paper 26.2 API dependency to a specific build for reproducible builds.
- Changed death-triggered update scheduling to track scheduled, in-flight, and pending update states while preserving the existing configurable debounce delay.
Fixed
- Fixed issue #7: deaths that occur after a leaderboard snapshot starts, including while the Discord request is still in progress, now queue a fresh follow-up update instead of being silently missed.
- Fixed rapid in-flight deaths so they coalesce into one follow-up update rather than producing unnecessary duplicate requests.
- Fixed the Gradle 9.3 test runtime configuration by explicitly including the JUnit Platform launcher.
What's Changed
- 7 deaths can be missed while a discord request is in progress by @mccreeper1318 in https://github.com/mccreeper1318/deathstodiscord/pull/24
Full Changelog: https://github.com/mccreeper1318/deathstodiscord/compare/1.4...1.4.1-beta.1
⚠️ Beta Release Warning
Beta versions are pre-release builds intended for testing. They may contain bugs, incomplete changes, or unexpected behavior and may not be as stable as the latest full release.
Before installing a beta:
Back up your server and plugin configuration. Review the changelog for known changes. Be prepared to roll back if problems occur.
Beta builds are recommended for testing environments or users comfortable troubleshooting issues. For production servers, use the latest stable release whenever possible.
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:ef07rUfW:1VlbwV89"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ef07rUfW:1VlbwV89"
}

