1.5
Compatibility
Changes
Cobblemon Leaderboards 1.5
A big quality-of-life update focused on stability, cleanup, and making leaderboard management much easier after updates.
New
-
Automatic startup cleanup Old orphaned leaderboard displays are now cleaned up automatically when the server starts. This helps remove broken leftovers from older versions without manual intervention.
-
New
/leaderboard cleanupcommand Server admins can now force a full cleanup at any time. It removes orphaned displays and rebuilds active leaderboards safely. -
Polish language support Added
pl_pllocalization support for players using Polish.
Changes
-
Better recovery after version updates Leaderboards now recover much more cleanly when older board or hologram entities are still hanging around from previous versions.
-
Shared cleanup logic Automatic cleanup on startup and manual cleanup use the same rebuild process, so results are more predictable and reliable.
Fixes
-
Fixed hologram targeting for commands Commands like
info,remove,refresh looked, andrepair lookedcan now properly detect hologram leaderboards when you look at them. -
Fixed admin issues with old holograms and boards Legacy displays from older versions could become impossible to modify or delete. Cleanup and detection have been improved so these cases are much easier to resolve.
-
Fixed orphaned display buildup Broken or outdated board/hologram displays could stack up over time. These are now cleaned up automatically and can also be removed manually with the new cleanup command.
-
General command stability improvements Leaderboard management commands were cleaned up and made more reliable overall.
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:Vb1pXlt5:Evkv1sM5"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Vb1pXlt5:Evkv1sM5"
}

