monban (Whitelist)

monban 3.2.0 adds built-in player groups and permissions, along with centralized permission synchronization for Velocity networks

This release turns monban into a more complete access-control layer: groups, scoped permissions, backend access, and whitelist administration can now be managed from Velocity, while Bukkit and Paper backends apply the synchronized state locally

Highlights

• Built-in player groups, separate from Velocity SERVER_GROUP definitions
• Group and direct player permissions with NETWORK, SERVER_GROUP, and SERVER scopes
• Group access grants for individual backend servers and server groups
• Effective access lookup showing groups, permissions, and their origins
• New Velocity commands for group management, group assignments, group permissions, and direct player permissions
• Centralized whitelist, group, and permission administration on Velocity
• Signed state synchronization from Velocity to Bukkit and Paper backends
• Automatic sync.yml generation on Velocity when backend permissions are enabled
• Local backend permission attachments without requiring LuckPerms
• Backend access checks fail closed until the first verified synchronized state is received
• Automatic creation of server-groups.yml on backends
• Correct ONLINE / OFFLINE identity handling for forwarded hybrid connections
• Backend permissions are applied before command visibility is sent to players
• Command-tree refresh after permission updates, so tab completion reflects the player's actual permissions

Downloads

Choose the JAR for your platform:

• monban-bukkit-spigot-3.2.0.jar — Bukkit / Spigot
• monban-paper-folia-3.2.0.jar — Paper / Folia
• monban-velocity-3.2.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

Velocity networks

Velocity is the central authority for network whitelist, backend access, groups, and permissions

Install monban on Velocity and on every Bukkit/Paper backend that should apply synchronized permissions. Enable backend-permissions on Velocity and monban will create plugins/monban/sync.yml automatically. Copy the generated file to each enabled backend and set its server-name to the exact registered server name from Velocity

In centralized mode, backend servers do not provide a separate local monban administration path. This keeps whitelist, group, and permission state consistent across the network

The backend creates server-groups.yml automatically. It only needs matching server-group mappings when SERVER_GROUP permissions or access grants are used

Example:

monban group create moderator
monban group moderator access grant server lobby
monban group moderator permission add server lobby chunky.command.start
monban group moderator permission add server lobby chunky.command.cancel
monban user hanamuramiyu offline group add moderator

After assigning permissions, reconnect the player and check /chunky tab completion on the backend

Standalone servers

For standalone Bukkit, Spigot, Paper, or Folia servers, Minecraft's native whitelist must be disabled:

white-list=false

monban remains the local whitelist authority and provides /monban whitelist for administration

Documentation

Full setup guides, configuration reference, commands, permissions, Velocity setup, backend synchronization, and hybrid authentication documentation:

https://monban.miyu.pw/

Thanks to everyone who tested the new network administration features and helped me find the weird parts of hybrid forwarding (˵ •̀ ᴗ - ˵ ) ✧