ВЕРСИИ (18)

# 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: ```properties 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`: ```yaml 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: ```text /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](https://monban.miyu.pw/getting-started/upgrading-to-3-3/) 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/](https://monban.miyu.pw) Thanks to everyone using monban and sharing feedback along the way (˶ ¯ ꇴ ¯ ˶)

# 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: ```properties 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`: ```yaml 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: ```text /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](https://monban.miyu.pw/getting-started/upgrading-to-3-3/) 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/](https://monban.miyu.pw) Thanks to everyone using monban and sharing feedback along the way (˶ ¯ ꇴ ¯ ˶)

# 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: ```properties 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`: ```yaml 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: ```text /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](https://monban.miyu.pw/getting-started/upgrading-to-3-3/) 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/](https://monban.miyu.pw) Thanks to everyone using monban and sharing feedback along the way (˶ ¯ ꇴ ¯ ˶)

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: ```text 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: ```properties 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/](https://monban.miyu.pw) Thanks to everyone who tested the new network administration features and helped me find the weird parts of hybrid forwarding (˵ •̀ ᴗ - ˵ ) ✧

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: ```text 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: ```properties 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/](https://monban.miyu.pw) Thanks to everyone who tested the new network administration features and helped me find the weird parts of hybrid forwarding (˵ •̀ ᴗ - ˵ ) ✧

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: ```text 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: ```properties 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/](https://monban.miyu.pw) Thanks to everyone who tested the new network administration features and helped me find the weird parts of hybrid forwarding (˵ •̀ ᴗ - ˵ ) ✧

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 `/monban` help - Runtime `/monban whitelist enable` and `/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 / Spigot - `monban-paper-folia-3.1.0.jar` — Paper / Folia - `monban-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: ```properties white-list=false ``` monban becomes the whitelist authority and provides `/monban whitelist` for administration The whitelist can now be enabled or disabled at runtime: ```text /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 whitelist` for global NETWORK access - `/monban access` for scoped grants - `/monban lookup` for player identity and whitelist information - `/monban status` for 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/](https://monban.miyu.pw) Thanks to everyone who kept using monban and helped me turn it into a more comfortable plugin to administer /ᐠ ˵> ˕ <˵マ

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 `/monban` help - Runtime `/monban whitelist enable` and `/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 / Spigot - `monban-paper-folia-3.1.0.jar` — Paper / Folia - `monban-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: ```properties white-list=false ``` monban becomes the whitelist authority and provides `/monban whitelist` for administration The whitelist can now be enabled or disabled at runtime: ```text /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 whitelist` for global NETWORK access - `/monban access` for scoped grants - `/monban lookup` for player identity and whitelist information - `/monban status` for 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/](https://monban.miyu.pw) Thanks to everyone who kept using monban and helped me turn it into a more comfortable plugin to administer /ᐠ ˵> ˕ <˵マ

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 `/monban` help - Runtime `/monban whitelist enable` and `/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 / Spigot - `monban-paper-folia-3.1.0.jar` — Paper / Folia - `monban-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: ```properties white-list=false ``` monban becomes the whitelist authority and provides `/monban whitelist` for administration The whitelist can now be enabled or disabled at runtime: ```text /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 whitelist` for global NETWORK access - `/monban access` for scoped grants - `/monban lookup` for player identity and whitelist information - `/monban status` for 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/](https://monban.miyu.pw) Thanks to everyone who kept using monban and helped me turn it into a more comfortable plugin to administer /ᐠ ˵> ˕ <˵マ

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 `ONLINE` and `OFFLINE` player identities - Network-wide whitelist enforcement on Velocity - `SERVER_GROUP` and `SERVER` access grants - Per-backend `OPEN` and `GRANT_REQUIRED` access policies - Optional hybrid `ONLINE` / `OFFLINE` authentication-flow selection for Velocity - Unified `/monban whitelist` administration across supported platforms - `/monban access` and `/monban status` for 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 / Spigot - `monban-paper-folia-3.0.0.jar` — Paper / Folia - `monban-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: ```properties 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: [https://monban.miyu.pw/](https://monban.miyu.pw) Thanks to everyone who kept using monban, asked about Velocity support, or gave me a reason to come back to this project (˵◝ ⩊ ◜˵マ

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 `ONLINE` and `OFFLINE` player identities - Network-wide whitelist enforcement on Velocity - `SERVER_GROUP` and `SERVER` access grants - Per-backend `OPEN` and `GRANT_REQUIRED` access policies - Optional hybrid `ONLINE` / `OFFLINE` authentication-flow selection for Velocity - Unified `/monban whitelist` administration across supported platforms - `/monban access` and `/monban status` for 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 / Spigot - `monban-paper-folia-3.0.0.jar` — Paper / Folia - `monban-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: ```properties 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: [https://monban.miyu.pw/](https://monban.miyu.pw) Thanks to everyone who kept using monban, asked about Velocity support, or gave me a reason to come back to this project (˵◝ ⩊ ◜˵マ

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 `ONLINE` and `OFFLINE` player identities - Network-wide whitelist enforcement on Velocity - `SERVER_GROUP` and `SERVER` access grants - Per-backend `OPEN` and `GRANT_REQUIRED` access policies - Optional hybrid `ONLINE` / `OFFLINE` authentication-flow selection for Velocity - Unified `/monban whitelist` administration across supported platforms - `/monban access` and `/monban status` for 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 / Spigot - `monban-paper-folia-3.0.0.jar` — Paper / Folia - `monban-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: ```properties 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: [https://monban.miyu.pw/](https://monban.miyu.pw) Thanks to everyone who kept using monban, asked about Velocity support, or gave me a reason to come back to this project (˵◝ ⩊ ◜˵マ

## NekoList v2.0.0 - Major Update with Database Support & Folia Compatibility The biggest update yet! Complete architectural overhaul with database support, Folia compatibility, and enhanced performance. ### 🔥 What's New #### Database Support: - **MySQL/MariaDB Integration:** Store whitelist data in external databases - **Smart Fallback:** Automatically switches to file storage if database connection fails - **Real-time Sync:** Seamless data synchronization across server restarts #### Performance & Architecture: - **Folia Compatibility:** Full support for Folia servers with adaptive schedulers - **Modular Design:** Complete codebase restructuring for better maintainability - **Advanced Caching:** Optimized whitelist caching with TTL and smart reloading - **MiniMessage Support:** Modern text formatting with `<color>` tags #### Enhanced Reliability: - **Connection Pooling:** HikariCP for efficient database connections - **Error Recovery:** Graceful fallback mechanisms and detailed logging - **Configuration Validation:** Improved config validation with helpful error messages - **Update Checker:** Automatic version checking via Modrinth API #### Discord Bot Improvements: - **Command Cooldowns:** Prevent spam with configurable cooldown system - **Enhanced Validation:** Better permission checking and input validation - **Improved Stability:** Better error handling and connection management ### 📋 Features - **Complete Whitelist Management:** In-game commands for all operations - **Database Support:** MySQL/MariaDB with automatic fallback to files - **Folia Compatibility:** Works on Folia servers with adaptive scheduling - **MiniMessage Formatting:** Modern `<color>` tags instead of legacy & codes - **Multi-language Support:** 9 languages including EN, ES, JA, RU, ZH - **Permission Integration:** Compatible with LuckPerms and other permission systems - **Minecraft 1.21.1+ Support:** Updated for latest Minecraft versions - **Metrics Integration:** Optional bStats metrics (anonymous usage data) ### 🚨 Breaking Changes #### ⚠️ Important Note: Version 2.0.0 introduces breaking changes: 1. **Velocity Support Removed:** This version supports only Bukkit, Paper, Purpur, and Folia servers 2. **MiniMessage Formatting:** Language files now use MiniMessage format (`<color>`) instead of legacy `&` codes ### 📥 Installation #### For Paper/Purpur/Folia servers: 1. Download the jar file below 2. Place in your server's `plugins` folder 3. Restart server 4. Configure in `plugins/NekoList/config.yml` #### Database Setup (Optional): 1. Edit `plugins/NekoList/config.yml` 2. Set `database.type: "mysql"` 3. Configure your MySQL/MariaDB credentials 4. The plugin will automatically create required tables ### 🔄 Upgrade Instructions #### From v1.x to v2.0.0: 1. **Backup your data:** Copy `plugins/NekoList/whitelist.yml` and `plugins/NekoList/config.yml` 2. Remove old plugin jar 3. Install v2.0.0 4. **Manual language file update:** Copy old messages from your language files to new format (see example below) #### Language File Migration Example: ```yaml # Old format (v1.x) player-added: "&aPlayer %player% has been added to whitelist." # New format (v2.0.0) player-added: "<green>Player %player% has been added to whitelist." ```` ### 📊 System Requirements - **Java 21** or higher - **Minecraft 1.21.x** - **Bukkit/Paper/Purpur/Folia** server - **MySQL/MariaDB** (optional, for database mode)

## NekoList v1.2.1 - Stability & Correctness Fixes This patch release focuses on improving the stability, correctness, and maintainability of the plugin, addressing several issues identified in v1.2.0. ### 🔧 Fixed - **Critical: Duplicate Class Definitions**: Resolved the issue where `DiscordBot` and `DiscordEventListener` were incorrectly defined as identical classes. The codebase now correctly separates concerns between the bot instance and its event listeners. - **Enhanced Token Validation**: Improved the check for the Discord bot token. The bot will now fail to start cleanly if the token is missing or remains the default placeholder `"YOUR_BOT_TOKEN_HERE"`, preventing unintended attempts to connect with invalid credentials. - **Dependency Cleanup**: Removed unnecessary `snakeyaml` dependency. The plugin now correctly relies on the built-in YAML support provided by Bukkit/Spigot and Velocity APIs, reducing the final JAR size. - **Resource Handling**: Corrected the Gradle build script's `processResources` task. It now correctly includes only `.yml` files from the resources directory, as these are the only types used by the plugin, removing the redundant `.yaml` inclusion. - **Removed Unused Dependency**: Eliminated the unused `compileOnly("net.luckperms:api:5.4")` dependency from the build configuration. - **Refined Shadow JAR Exclusions**: Updated the `shadowJar` task to correctly exclude Paper and Velocity API dependencies only when they are included via `implementation`. The existing `compileOnly` declarations already handle this correctly for the target platforms. - **Documentation Accuracy**: Corrected instructions in the README regarding building from source (`./gradlew build`) and clarified platform-specific sections (Paper/Forks, Velocity/Forks). - **Translation Consistency**: Updated the "ping" command response translation placeholders in the example configuration and language files to ensure consistency (e.g., "¡Pong!" in Spanish is now correctly "¡Ping!"). ### 🏗️ Internal Improvements - **Code Structure**: Refactored internal structures to ensure better separation of logic between core plugin, Bukkit module, and Velocity module. - **Build Process**: Streamlined the Gradle build process for clarity and efficiency. - **Maintainability**: Addressed structural issues that could lead to confusion or errors in future development.

Advanced whitelist management system with UUID support and enhanced reliability! **What's New in v1.2.0:** - **UUID-Based Whitelist System**: Advanced player verification for licensed servers - **Nickname Change Protection**: Players stay whitelisted even after changing names - **Enhanced Data Reliability**: Guaranteed data integrity across plugin reloads - **Universal Compatibility**: Works seamlessly across all server types **UUID System Features:** - **Smart Verification**: Checks UUID first, falls back to nickname for compatibility - **Automatic Updates**: Real-time synchronization of player data on login - **Migration Support**: Automatic upgrade from legacy nickname-only entries - **Mode Awareness**: Different behavior for licensed vs offline servers **Licensed Servers (online-mode=true):** - Players remain whitelisted after nickname changes - Protection against nickname spoofing - Automatic UUID registration on first join **Offline Servers (online-mode=false):** - Classic nickname-based verification - Full backward compatibility - Simple and predictable behavior **Reliability Improvements:** - Fixed data loss issues during plugin reloads - Enhanced file handling and error recovery - Synchronized operations preventing corruption - Robust configuration parsing **Features:** - Complete whitelist management with in-game commands - Discord bot integration with modern slash commands - Multi-language support (13 languages) - Cross-platform compatibility (Bukkit/Paper/Velocity) - Permission system compatibility - Minecraft 1.21.x support **Installation:** For Bukkit/Paper servers: 1. Download the jar file below 2. Place in your server's `plugins` folder 3. Restart server 4. Configure in `plugins/NekoList/config.yml` For Velocity proxy: 1. Download the jar file below 2. Place in Velocity's `plugins` folder 3. Restart proxy 4. Configure in `plugins/NekoList/config.yml` **Upgrade Note:** This version maintains full compatibility with previous configurations. Existing whitelists will be automatically upgraded to the new format.

Advanced whitelist management system for Minecraft servers with Discord integration - now with major performance improvements! **What's New in v1.1.1:** - **Major Performance Boost**: In-memory whitelist caching for instant player checks - **Code Architecture Overhaul**: Simplified and optimized plugin structure - **Enhanced Discord Bot**: Better configuration validation and localization - **Improved Reliability**: Fixed reload functionality and permission systems **Performance Improvements:** - Whitelist checks now happen in memory (100x faster) - Eliminated disk I/O during player login events - Optimized configuration reloading - Better resource management **Bug Fixes:** - Fixed Discord bot permission validation - Resolved language file loading issues - Corrected Velocity reload commands - Improved configuration error handling **Features:** - Complete whitelist management with in-game commands - Discord bot integration with modern slash commands - Multi-language support (13 languages) - Cross-platform compatibility (Bukkit/Paper/Velocity) - Permission system compatibility - Minecraft 1.21.x support **Installation:** For Bukkit/Paper servers: 1. Download the jar file below 2. Place in your server's `plugins` folder 3. Restart server 4. Configure in `plugins/NekoList/config.yml` For Velocity proxy: 1. Download the jar file below 2. Place in Velocity's `plugins` folder 3. Restart proxy 4. Configure in `plugins/NekoList/config.yml` **Upgrade Note:** This version maintains full compatibility with v1.1.0 configurations.

Advanced whitelist management system for Minecraft servers with Discord integration - now with Velocity support! **New in v1.1.0:** - Full Velocity proxy compatibility - Support for Bukkit, Spigot, Paper, Purpur, and Velocity - Cross-platform configuration system - Automatic platform detection **Features:** - Complete whitelist management with in-game commands - Discord bot integration with modern slash commands - Multi-language support (13 languages) - Permission system compatibility - Works with both standalone servers and proxy networks - Minecraft 1.21.x support **Installation:** For Bukkit/Paper servers: 1. Download the jar file below 2. Place in your server's `plugins` folder 3. Restart server 4. Configure in `plugins/NekoList/config.yml` For Velocity proxy: 1. Download the jar file below 2. Place in Velocity's `plugins` folder 3. Restart proxy 4. Configure in `plugins/NekoList/config.yml`

Initial release of NekoList - Advanced Whitelist Management Features: - Complete whitelist management system - Discord bot integration with slash commands - Multi-language support (13 languages) - Permission system compatibility - Real-time player management