Tags
Creators
Details
All versions
1.0.3
Release
Clans 1.0.34 months ago 155
Uploaded by
Compatibility
Minecraft: Java Edition
26.1.x
1.21.x
1.20.x
Platforms
Paper
Purpur
Changes
VRXClans v1.0.3
General
- Plugin version updated to 1.0.3.
- Prepared compatibility for Paper 1.20 up to 1.26+.
- Refactored the project into a more stable and modern structure.
Performance & Database
- Switched database access to HikariCP connection pooling.
- Separated clan data handling into cleaner repository, service, and cache structures.
- Added a migration system for future database changes.
- Optimized region protection using chunk-based caching.
- Clan vaults are now only saved when they were actually modified.
Clan System
- Added clan logs for:
- Deposits
- Withdrawals
- Kicks
- Promotions and demotions
- War events
- Diplomacy events
- Clan roles can now be renamed in the GUI.
- Ally, rival, and neutral requests now expire after a configurable timeout.
- Added war kill-farming protection.
- Added configurable clan level rewards.
Commands
- Added
/clan topwith categories:levelbankkillskdr
- Added
/clan logs. - Added
/clana inspect. - Improved TabComplete for
/clan:- Subcommands
- Clan names
- Player names
- Top categories
- Diplomacy actions
- War wagers
- Bank amounts
GUI
- Added an admin inspect GUI for clans.
- Expanded the roles and permissions GUI.
- Improved clan vault handling.
- Optimized GUI navigation and displays.
Bug Fixes
- Fixed a bank exploit with negative amounts.
- Fixed vault persistence after server restarts.
- Fixed XP level-ups when receiving large amounts of XP.
- Fixed join cooldown reset.
- Improved SQL safety.
- Reworked async chat handling to use Paper-compatible events.
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:yIXOVma6:8kCM4D7O"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:yIXOVma6:8kCM4D7O"
}

