Tags
Creators
Details
All versions
2.14.0
Release
DailyRewards 2.14.0last week 706
Compatibility
Minecraft: Java Edition
26.3
26.2
26.1
1.21
1.20
1.19
1.18
1.16
1.15
1.14
1.13
1.12
1.11
1.10
1.9
1.8.9
Platforms
Folia
Paper
Purpur
Spigot
Changes
Changelog:
- Fixed items being movable into the reward and settings menus, where they could get lost, and clicks in your own inventory claiming rewards or opening settings
- Fixed rewards being claimable twice by clicking quickly
- Fixed server lag caused by repeatedly clicking a reward in the menu
- Reward items now appear immediately when the menu opens
- Fixed the settings back button ignoring settings-back-position, and the settings slot working even with settings-enabled-in-menu: false
- /reward claim <type> <player> now requires the dailyreward.claim.others permission
- Fixed tab completion for /reward claim
- /reward reset now works for offline players and reports unknown reward types
- /reward import now works without a userdata folder, skips files that are not player data and no longer freezes the server
- Fixed join notifications crashing on 1.13–1.15
- Join notifications and auto-claim now run on the correct thread, fixing sound playback and Folia support
- join-auto-claim-delay is respected again
- Cancelling AutoClaimEvent now actually prevents the auto-claim
- Fixed a memory leak in auto-claim and an error when a player left before their data finished loading
- A broken reward line (e.g. an invalid firework type or color) no longer cancels the rest of the reward, it is logged instead
- [player] actions now work when written with a leading slash
- Title and subtitle are only sent when the reward defines them
- Firework colors now work with or without braces, and invalid hex colors such as <#gggggg> no longer cause errors
- Fixed daily rewards on servers with a Turkish system locale (cooldown not saved with MySQL, premium permission not working), existing data is migrated automatically
- mysql-properties from config.yml are now applied
- Missing or broken stored values and failed database reads no longer cause errors when joining or opening the menu
- Errors while loading or saving player data are now logged, including the affected file
- Reloading the plugin with players online no longer breaks loading of player data
- Custom language files can now be used, and a misspelled language falls back to English with a warning
- Fixed the join notification setting showing the auto-claim name, and the auto-claim permission message showing %permission%
- The update notification for operators works again
- Removed the dependency on commons-lang 2 for compatibility with newer server versions
- Removed the unused [bossbar] action, lines using it are now reported as an invalid action
For additional support and assistance, feel free to reach out on our Discord server, where our team and community are ready to help with any questions or issues you may have.
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:lNmhMgUv:d0Kxjddm"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:lNmhMgUv:d0Kxjddm"
}

