Tags
Creators
Details
1.0.4
Compatibility
Changes
xDay v1.0.4 - Now with Automatic Update Notifications!
This version introduces a smart update checker to keep your server running the latest and greatest version of xDay.
✨ What's New:
Automatic Update Checker: The plugin now automatically checks for new versions on Modrinth. Players with the xday.update permission will be notified when a new version is available. You can disable this feature in the config.yml.
Code Refinements: General improvements to the code for better performance and stability.
Thank you for your continued support!
Option 2: More Detailed & Professional Version 1.0.4 Release Notes
Hello everyone! This update focuses on improving the user experience by adding a much-requested feature and enhancing the plugin's internal structure for future development.
🚀 New Features
Modrinth Update Checker:
xDay will now automatically check for new versions on Modrinth to ensure you're always up-to-date.
In-game notifications are sent to players with the xday.update permission upon joining.
This feature is fully configurable and can be disabled in the config.yml. The notification message can also be customized.
🛠️ Improvements & Fixes
API Enhancements: The plugin's API has been improved to use Enums instead of Strings for time and weather types, making it more robust and easier for other developers to integrate with.
Performance Optimizations: We've refactored parts of the code to ensure the plugin runs as efficiently as possible.
Cleaner Packaging: The final plugin .jar no longer includes unnecessary Maven project files.
As always, if you encounter any issues or have suggestions, please let me know!
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| xDay-1.0.4.jar | Unknown | 315.8 KiB |
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:r6WAKpDi:n2MnOwOa"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:r6WAKpDi:n2MnOwOa"
}

