All versions
1.1
Release
Daily Rewards 1.1-SNAPSHOT2 years ago 356
Compatibility
Minecraft: Java Edition
1.21–1.21.4
Platform
Paper
Changes
New Features:
- Auto Claim on Join: Players can now automatically receive their daily rewards upon joining the server. This feature can be enabled or disabled via the autoClaimOnJoin setting in the config.yml.
- Premium Rewards: Implemented support for premium rewards. Players with the dailyrewards.premium permission will receive additional premium rewards automatically if the auto claim feature is enabled.
- Custom Messages: Added customizable messages for both standard and premium rewards when automatically claimed. These can be configured using autoClaimMessage and autoClaimPremiumMessage in the config.yml.
Improvements:
- Database Management:
- The SQLite database is now created in the plugin's data folder, ensuring better organization and accessibility.
- Improved error handling and logging for database operations, including connection and query execution.
- Added a method to close the database connection when the plugin is disabled, ensuring resources are properly released.
Bug Fixes:
- Fixed issues with cooldown messages not displaying correctly.
- Resolved potential conflicts with reward claiming logic to ensure players only receive rewards once per day.
Configuration Changes:
- Updated config.yml to include new settings for auto claim messages and improved cooldown message formatting.
General:
- Enhanced logging to provide better insights into plugin operations and player interactions. Please ensure to update your config.yml with the new settings to take full advantage of these features. As always, backup your existing configuration and database before updating.
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:khryd2S4:LhAuMtl5"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:khryd2S4:LhAuMtl5"
}

