Tags
Creators
Details
3.0.0-velocity
Compatibility
Changes
monban 3.0.0 is a major rewrite of the plugin, with redesigned access control, explicit player identity handling, and restored Velocity support
This release moves monban beyond a simple standalone whitelist and introduces proper network-wide and scoped access control for Velocity servers
Highlights
- Restored full Velocity support
- Standalone whitelist support for Bukkit, Spigot, Paper, and Folia
- Explicit
ONLINEandOFFLINEplayer identities - Network-wide whitelist enforcement on Velocity
SERVER_GROUPandSERVERaccess grants- Per-backend
OPENandGRANT_REQUIREDaccess policies - Optional hybrid
ONLINE/OFFLINEauthentication-flow selection for Velocity - Unified
/monban whitelistadministration across supported platforms /monban accessand/monban statusfor Velocity- Strict, versioned YAML configuration and persistent access state
- Fail-closed access enforcement for security-sensitive failures
Downloads
Choose the JAR for your platform:
monban-bukkit-spigot-3.0.0.jar— Bukkit / Spigotmonban-paper-folia-3.0.0.jar— Paper / Foliamonban-velocity-3.0.0.jar— Velocity
Do not install multiple platform builds on the same server
Java
monban targets Java 21 bytecode
Runtime requirements still depend on the Minecraft platform and version. In particular, Paper 26.1+ requires Java 25
Standalone servers
For standalone Bukkit, Spigot, Paper, or Folia servers, Minecraft's native whitelist must be disabled:
white-list=false
monban becomes the whitelist authority and provides /monban whitelist for administration
Velocity networks
The Velocity build acts as the network access authority
It can enforce both the global network whitelist and access to individual backend servers or server groups
Hybrid authentication-flow selection is also available for networks that need both ONLINE and OFFLINE identities
Documentation
Full setup guides, configuration reference, commands, permissions, Velocity setup, backend policies, and hybrid authentication documentation:
Thanks to everyone who kept using monban, asked about Velocity support, or gave me a reason to come back to this project (˵◝ ⩊ ◜˵マ
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:MUXv6Dpt:ba2ABSls"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:MUXv6Dpt:ba2ABSls"
}

