Tags
Creators
Details
All versions
2.13.0
Release
DailyRewards 2.13.02 weeks ago 867
Compatibility
Minecraft: Java Edition
26.2
26.1.x
1.21.x
1.20.x
1.19.x
1.18.x
1.17.x
1.16.x
1.15.x
1.14.x
1.13.x
1.12.x
1.11.x
1.10.x
1.9.x
1.8.8–1.8.9
Platforms
Bukkit
Folia
Paper
Purpur
Spigot
Changes
Fixed
- Menu clicks now use raw slots, so clicking your own inventory can no longer claim rewards or open the settings menu.
- Clicks are cancelled before the empty-slot check and drags into the menu are blocked, so items can no longer be moved into (and lost inside) a menu.
- NullPointerException on quit when a player disconnected before their data finished loading.
- [player] reward actions no longer pass a leading slash, so they actually execute.
- Rewards can no longer be claimed twice by rapidly clicking; the cooldown is applied before the reward actions run instead of after.
- Cancelling AutoClaimEvent now actually prevents the auto-claim.
- /reward claim <type> <player> now requires dailyreward.claim.others. Claiming for yourself is unchanged.
- Join notifications and auto-claim no longer touch the Bukkit API from an async thread, fixing sound playback and Folia support.
- Auto-claim entries are released on quit; they were kept forever and leaked the player object.
- join-auto-claim-delay is respected again; auto-claim was reusing join-notification-delay.
- The update notification for operators is registered again and no longer fires before the version lookup has finished.
- Missing or malformed stored values no longer throw while joining or opening a menu. Cooldowns fall back to "not claimable", and failed database reads are logged instead of being swallowed.
- /reward import works on a server with no userdata folder, skips files that are not player data, and runs off the main thread instead of freezing the server while it waits.
- The join-notification setting shows its own name instead of the auto-claim one.
- Title and subtitle are only sent when the reward defines them.
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:7hxBNyEN"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:lNmhMgUv:7hxBNyEN"
}

