Links
Tags
Creators
Details
Licensed ARR
Published 4 months ago
Updated 23 hours ago
All versions
v1.6
Release
hClans3 months ago 16
Compatibility
Minecraft: Java Edition
26.2
26.1.x
1.21.x
Platforms
Bukkit
Paper
Purpur
Spigot
Changes
- En/ru localization has been added (by default, ru is set if you have already created a plugin folder)
- The config is divided into several files
- Documentation for placeholders “placeholders.txt” has been added
- Complete transition to MiniMessage
- A built‑in clan top with various flexible placeholders has been added so you don’t have to struggle
- Standard placeholders have been expanded
- Optimization of work with PlaceholderAPI
- Clan levels are balanced in the default config + 5 new ones added
- Role permissions have been reworked to store explicitly enabled/disabled roles
- /clan assistance now depends on your specific role in the clan
- Maximum optimization of the GUI, plugin commands, basehead, and much more
- The [achivement] action has been removed
- Support for H2/MARIADB has been added
- The invitation expiration check has been optimized.
- XSeries has been updated (13.5.0 --> 13.7.1) to work with new versions, optimizations, etc.
- API registration has been improved (there may be failures related to add‑ons; some users may need to rewrite something slightly).
- The add‑on loader has been improved; now you can simply place an add‑on in plugins/hClans/addons without moving it into the plugin folder.
- Dependencies have been updated and new ones added. A lot of work has been done — far more than just an hour or two. A bunch of different options have been tested, and the best possible peak in the plugin’s optimization/performance has been achieved. Most likely, this is the final update to the plugin’s functionality — from now on, there will only be fixes and optimizations (and even that’s not guaranteed). For addon developers: it’s now better to use ClanSkullAPI.createHead() in addons and reuse the head, rather than calling applyHead() every time you update your GUI.
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:6vtTkhKe:ndf6ucoJ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:6vtTkhKe:ndf6ucoJ"
}

