2.1
Compatibility
Changes
✨ New Features
- Prefix Support: Added a practical prefix feature managed from a single place, which can be used commonly across all messages.
⚡ Improvements
- Code & Architecture Optimization: Class structures were optimized to make message and prefix management more centralized, clean, and high-performing.
- Future-Proof Infrastructure: Build and dependency management were modernized to enhance the plugin's stability and long-term compatibility.
⚠️ Important Note: Due to major changes in the code structure, it is strongly recommended to back up and delete your old config.yml file before updating, and allow the plugin to generate a fresh new config file.
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:KFuCcsZc:PrO5VyC5"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:KFuCcsZc:PrO5VyC5"
}

