Tags
Creators
Details
3.3.0
Compatibility
Changes
What's Changed
This update focused on improving the plugin's architecture and maintainability. We did the following updates:
- Using DI pattern to make plugin architecture better
- Dependencies are now downloaded through our own Quark framework and no longer shaded into plugin JAR file
- Using OrmLite + DAO to better work with the database
- Switched to Lamp command framework
- Switched to own task scheduler system, so Folia is now supported
- and other changes like Gradle and it's plugins
⚠️ Please note If you find any problems with the plugin or the new dependency system, please let us know!
Full Changelog: https://github.com/BX-Team/NDailyRewards/compare/v3.2.1...v3.3.0
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:ZiFzQAnz:x6sTKatr"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ZiFzQAnz:x6sTKatr"
}

