5.0
Compatibility
Changes
Release 5.0 - Full 1.21.x Compatibility
OVERVIEW
Clumps v5.0 focuses on compatibility, ensuring full support for all Minecraft 1.21 versions—from 1.21 to 1.21.8. This update maintains the core principles of the plugin: silent operation, zero logs, and admin-focused control—while broadening its usability across the latest Minecraft server versions.
KEY CHANGES
1. Full 1.21.x Compatibility
- Supported Versions: Clumps v5.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
- Seamless Functionality: All plugin features, including clumping mechanics and admin commands like
showconfig, function as expected on these versions.
2. No Console Logs (Continued from v3.0 & v4.0)
- Zero Logging Philosophy: The plugin remains fully silent in operation—no logs are written to console except in the event of critical errors.
3. No Log Files (Continued from v3.0 & v4.0)
- No Disk Writes for Logs: No
/logs/directory usage, keeping your server clean and efficient.
4. Error Handling (Continued from v3.0 & v4.0)
- Minimal Alerts: Critical failures produce one-time error messages, with no stack traces or verbose logs.
5. Continued Support for showconfig Command
- Admin Utility:
/clumps showconfigremains available, allowing admins to view configuration in-game or via the console. - Permission Required: Still restricted to users with the
clumps.adminpermission node.
⚙️ After a long hiatus, the Clumps project is officially back in active development, bringing new updates and broader version support!
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:29n2GNua"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:IahtO7tM:29n2GNua"
}

