6.0
Compatibility
Changes
Release 6.0 - Expanded 1.21.x Support & Folia Compatibility
OVERVIEW
Clumps v6.0 expands compatibility even further, adding support for the latest Minecraft 1.21 releases up to 1.21.11, while introducing native Folia support. As always, Clumps remains lightweight, silent, and focused on delivering reliable experience clumping with zero unnecessary overhead.
KEY CHANGES
1. Full 1.21.x Compatibility
-
Supported Versions: Clumps v6.0 now supports all Minecraft 1.21 versions, including:
- 1.21
- 1.21.1
- 1.21.2
- 1.21.3
- 1.21.4
- 1.21.5
- 1.21.6
- 1.21.7
- 1.21.8
- 1.21.9
- 1.21.10
- 1.21.11
-
Seamless Functionality: All plugin features, including experience clumping, orb merging, and admin commands, work consistently across every supported version.
2. Native Folia Support
- Folia Compatible: Clumps now fully supports Folia servers, ensuring safe scheduling and smooth operation within Folia's region-based threading model.
- No Configuration Changes Required: The plugin automatically operates correctly on both Paper and Folia without requiring separate builds or configuration.
3. No Console Logs (Continued)
- Zero Logging Philosophy: Clumps continues to operate silently during normal use, only displaying a concise message if a critical startup failure occurs.
4. No Log Files (Continued)
- Clean Server Environment: No log files are created, and the plugin performs no unnecessary disk writes for logging purposes.
5. Improved Error Handling
- Minimal Alerts: Critical errors generate a single, easy-to-read message without verbose stack traces or repeated console spam.
6. Continued Support for showconfig Command
- Admin Utility:
/clumps showconfigremains available for quickly viewing the active configuration in-game or from the server console. - Permission Required: Access continues to require the
clumps.adminpermission node.
⚙️ Clumps v6.0 continues the project's goal of providing a lightweight, maintenance-free experience with expanded Minecraft compatibility and full support for modern server software, including Folia.
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:IahtO7tM:PUyRJEEy"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:IahtO7tM:PUyRJEEy"
}

