2.4.0
Compatibility
Changes
This update introduces significant changes to the plugin's architecture:
The clan mechanic has been reworked: The internal logic for managing clans has been optimized. System stability has been improved, bugs have been fixed, and overall performance has been enhanced.
MySQL support has been removed: the plugin no longer uses MySQL. All data is now stored exclusively in local files.
New GUI system: The GUI system has been completely rewritten. Its new design and architecture allow for the customization of all menus via configuration files located in the 'gui' folder. Every slot, item, piece of text, and action can be edited.
Clan storage system updated: The clan data storage system (including inventory and member information) has been overhauled to ensure greater reliability and prevent data loss during restarts.
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:P8E5nb4w:J1ybaEgd"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:P8E5nb4w:J1ybaEgd"
}

