monban 3.3.0 — Geyser & Floodgate Release

monban 3.3.0 is a Geyser and Floodgate update that brings authenticated Bedrock players into monban's access-control model on Velocity

Bedrock connections can now resolve as a distinct FLOODGATE identity instead of being treated as Java ONLINE or OFFLINE players. Floodgate remains optional: Java-only networks do not need it, and existing Java access records keep their meaning

Highlights

• Optional Geyser and Floodgate integration on Velocity
• New FLOODGATE identity type, separate from Java ONLINE and OFFLINE
• Floodgate Java usernames are normalized and used as the durable access key
• Configured prefixes and space replacement work with the default .Name format
• XUID is retained as optional metadata and does not change identity matching
• Floodgate selectors are available across whitelist, scoped access, groups, and direct permissions
• Explicit identity.floodgate configuration in Velocity files
• Floodgate integration is disabled by default
• Floodgate is an optional Velocity dependency with correct plugin load order
• Once a provider has been discovered, provider failures deny the connection instead of silently falling back to a Java identity
• require-provider: true makes a missing Floodgate API fail visibly at startup
• Existing Java identity handling and access records remain compatible

Downloads

Choose the JAR for your platform:

• monban-bukkit-spigot-3.3.0.jar — Bukkit / Spigot
• monban-paper-folia-3.3.0.jar — Paper / Folia
• monban-velocity-3.3.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 remains the local whitelist authority and provides /monban whitelist for administration

Floodgate identity resolution belongs to the Velocity build. Standalone and backend builds continue to use Java ONLINE and OFFLINE identities

Velocity networks

Velocity remains the central authority for network admission, scoped backend access, player groups, and permissions

Existing Java access records and backend synchronization continue to work as before

Geyser and Floodgate

Install Geyser, Floodgate, and monban on Velocity. Enable the integration in plugins/monban/config.yml:

identity:
  mode: AUTO
  floodgate:
    enabled: true
    require-provider: true

Floodgate is disabled by default. require-provider: true is recommended when Bedrock access control is part of the production network: monban will fail visibly at startup if the Floodgate API cannot be discovered

Once a provider has been discovered, a provider error during login denies the connection instead of silently falling back to a Java identity

Use the Floodgate Java username reported to monban, including the configured prefix for unlinked accounts. XUID remains optional metadata and is not the matching key:

/monban whitelist add floodgate .BedrockName
/monban access grant server survival floodgate .BedrockName
/monban user .BedrockName floodgate group add bedrock

For linked accounts, the Java username reported by Floodgate may differ from the raw Bedrock name. Use the value monban actually reports

Synchronized backend permissions continue to apply to the Java ONLINE or OFFLINE identity resolved by the backend. Floodgate groups and direct permissions are evaluated on Velocity and are not re-matched as FLOODGATE on a backend in 3.3.0

Upgrading

Existing Java access records keep their ONLINE and OFFLINE meaning. Velocity configurations without a Floodgate block receive explicit defaults, so review the rewritten configuration after upgrading. Floodgate remains disabled until it is explicitly enabled

See the 3.3 upgrade guide for the full checklist

Documentation

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

https://monban.miyu.pw/

Thanks to everyone using monban and sharing feedback along the way (˶ ¯ ꇴ ¯ ˶)