Tags
Creators
Details
Licensed CC-BY-NC-SA-2.0-UK
Published 2 years ago
Updated 4 months ago
All versions
7.11.0
Release
BanManager v7.11.04 months ago 489
Compatibility
Minecraft: Java Edition
1.21.11
1.21.4
1.21.1
1.20.1
Platform
Fabric
Supported environments
Dedicated servers only
Required content
Any compatible version
Changes
What's New
- Versioned database migration system (#1060) — internal infra for safe future schema rollouts. No new migrations ship in this release beyond the existing
V1__baseline.sql. - Query efficiency + shutdown safety pass (#1061) — large refactor across the data layer to resolve TODOs, optimise hot queries, and harden plugin shutdown ordering.
- Pad empty lines in messages with a space for chat rendering (#1057) — fixes blank lines being dropped in some chat clients.
- Pass kick message through
PlayerBannedEvent(#1056) — third-party plugins can now read and modify the kick message before delivery. - Player punishment count prefixes (#1048) — display total punishments alongside player names in command output.
getPlayerExactonCommonServer(#1046) — exact-match lookup helper for plugins consuming the BanManager API.- LiteBans converter (#1036) — migrate punishment history from LiteBans into BanManager.
- Fabric 1.21.11 support (#1040) — new build target alongside the existing 1.20.1, 1.21.1, and 1.21.4 jars.
- Webhook duplicate / silent-propagation fixes (#1037, #1039, #1041) — eliminates duplicate webhook deliveries and propagates failures for visibility.
- Console UUID generation fix (#1038) — stable console identity across restarts.
- Route dependency logs through plugin logger (#1059) — third-party library logs now respect the BanManager log channel.
- Javadoc site re-enabled — published from CI for the public API.
Download Bukkit Download BungeeCord Download Velocity Download Sponge Download Sponge 7 Download Fabric 1.20.1 Download Fabric 1.21.1 Download Fabric 1.21.4 Download Fabric 1.21.11
Supplementary resources
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:7mgpQoBb:Pyu5EI4G"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:7mgpQoBb:Pyu5EI4G"
}

