
monban (Whitelist)
Modern Minecraft access control for standalone servers and Velocity networks
Список изменений
monban 3.1.0 is an administration and UX update focused on making everyday access management clearer and more convenient
This release adds shared presentation across supported platforms, interactive pagination, automatic ONLINE profile lookup, runtime whitelist control, and a new Velocity player lookup command
Highlights
- Shared Adventure presentation layer for whitelist, access, help, lookup, and status output
- Interactive whitelist and scoped-access pagination with filter-preserving navigation
- Clickable page navigation with compact ONLINE UUID display
- Automatic ONLINE profile resolution through the official Mojang profile endpoint
- Explicit UUID input remains available and bypasses profile lookup
- Permission-aware
/monbanhelp - Runtime
/monban whitelist enableand/monban whitelist disable - Atomic persistence for runtime whitelist policy changes
- New Velocity
/monban lookup <player>command - ONLINE and OFFLINE identity details with whitelist status in lookup results
- Clearer operator-facing success, error, and validation messages
Downloads
Choose the JAR for your platform:
monban-bukkit-spigot-3.1.0.jar— Bukkit / Spigotmonban-paper-folia-3.1.0.jar— Paper / Foliamonban-velocity-3.1.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
The whitelist can now be enabled or disabled at runtime:
/monban whitelist enable
/monban whitelist disable
The configuration is saved before the runtime policy changes. If saving fails, the current runtime state remains unchanged
Velocity networks
The Velocity build continues to act as the network access authority
It provides:
/monban whitelistfor global NETWORK access/monban accessfor scoped grants/monban lookupfor player identity and whitelist information/monban statusfor a runtime access summary
ONLINE player names can be resolved automatically, while explicit UUID input remains available when profile lookup should be bypassed
Documentation
Full setup guides, configuration reference, commands, permissions, Velocity setup, backend policies, hybrid authentication, and administration documentation:
https://monban.miyu.pw/
Thanks to everyone who kept using monban and helped me turn it into a more comfortable plugin to administer /ᐠ ˵> ˕ <˵マ
