1.0.0
Compatibility
Changes
DailyRewards v1.0.0
DailyRewards is a lightweight and flexible daily reward plugin for Paper servers.
This first release adds a clean daily login reward system with a configurable GUI, streak-based rewards and command-based reward execution. Players can open the reward menu with /daily and claim their daily reward manually through an inventory interface.
The plugin is designed to stay flexible: rewards are not locked to one economy system. Instead, rewards are executed through configurable console commands, making it compatible with Vault, CoinsEngine, crate plugins, permission plugins and many other systems.
Features
-
Daily reward GUI
-
Configurable reward days
-
Streak-based reward system
-
Reset streak when a player misses a day
-
Rewards executed through configurable commands
-
Support for internal placeholders:
%player%%uuid%%streak%%day%
-
Optional PlaceholderAPI support
-
SQLite player data storage
-
Configurable messages
-
Configurable GUI items and slots
-
/dailycommand for players -
/daily reloadcommand for admins -
Permission support
Commands
/daily— Opens the daily rewards menu/daily reload— Reloads the plugin configuration
Permissions
dailyrewards.use— Allows players to open the daily rewards menudailyrewards.reload— Allows admins to reload the configdailyrewards.admin— Gives access to admin permissions
Compatibility
- Minecraft: 1.21.11
- Server Software: Paper
- Java: 21
- Storage: SQLite
- Optional: PlaceholderAPIw
- currently only german
Notes
This is the initial release of DailyRewards. Future updates may add more admin tools, language files, improved GUI states and additional testing features.
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:7g8lMsCk:oqaoaj8G"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:7g8lMsCk:oqaoaj8G"
}

