\n# LobbyLimboManager<\/p>\n
High-performance lobby and limbo management plugin for BungeeCord and Velocity networks.<\/p>\n
Designed for scalability, reliability, and smooth player routing across multi-server environments.<\/p>\n
## Overview<\/p>\n
LobbyLimboManager handles player distribution, fallback logic, and queue management at the proxy level.<\/p>\n
* Automatically routes players to available lobbies
\n* Uses limbo servers to keep players connected when needed
\n* Includes a built-in queue system for full or unavailable lobbies
\n* Fully configurable behavior
\n* Works on both Velocity and BungeeCord<\/p>\n
## Features<\/p>\n
### Smart Routing<\/p>\n
Automatically sends players to the most suitable lobby based on configurable strategies:<\/p>\n
* Least players
\n* Random selection
\n* Round-robin distribution<\/p>\n
### Limbo & Fallback System<\/p>\n
Prevents unnecessary disconnections when lobbies are not available.<\/p>\n
* Sends players to limbo servers when needed
\n* Keeps players connected during downtime
\n* Smoothly redirects back to lobbies when available<\/p>\n
### Queue System<\/p>\n
Handles full or unavailable lobbies efficiently.<\/p>\n
* Automatic queue handling
\n* Sends players when space becomes available
\n* Prevents connection spam and failed joins<\/p>\n
### Multiple Servers Support<\/p>\n
Built for flexible network setups.<\/p>\n
* Multiple lobby servers
\n* Multiple limbo servers
\n* Dynamic routing between them<\/p>\n
### Fully Configurable<\/p>\n
Customize behavior to fit your network.<\/p>\n
* Routing modes
\n* Server limits
\n* Fallback behavior
\n* Queue system<\/p>\n
Supports live reload with:<\/p>\n
“`
\n\/llm reload
\n“`<\/p>\n
## Commands<\/p>\n
* `\/lobby`, `\/hub` \u2192 Sends the player to an available lobby
\n* `\/llm reload` \u2192 Reloads plugin configuration (Warning: nvm, it works)<\/p>\n
## Permissions<\/p>\n
* `lobbylimbomanager.command.lobby` \u2192 Access to the \/lobby and \/hub commands
\n* `lobbylimbomanager.admin` \u2192 Access to administrative commands<\/p>\n
## Installation<\/p>\n
1. Download the latest release
\n2. Place the `.jar` in your proxy plugins folder
\n3. Start your proxy
\n4. Edit the generated configuration if needed<\/p>\n
## Compatibility<\/p>\n
* Velocity
\n* BungeeCord
\n* Waterfall (Not tested, but expected to work)<\/p>\n
## Config.yaml Example<\/p>\n “` # ———————————————————– # ============================================================ # ============================================================ # ============================================================ # Lobby Selection Mode # Limbo Selection Mode # ============================================================ # Enable fallback to another lobby when a player is kicked. # Enable fallback to limbo when no lobbies are available. # Server Fallback Control # Kick Message No-Fallback Keywords # ============================================================ # Dispatch Attempt Threshold # ============================================================ # Health Check Interval (seconds) # Failed Server Retry Interval (seconds) # Attempt Expiry (seconds) # Queue Dispatch Interval (milliseconds) # Queue Waiting Message Interval (milliseconds) # Debug Mode # Server Player Limits # ============================================================ # Shown when a player is successfully connected to a lobby. # Shown when a player is sent to a limbo server. # Shown when a player is kicked and moved to a fallback lobby. # Shown when a player is kicked and moved to a fallback limbo. # ———————————————————– # ———————————————————– “`<\/p>\n<\/details>\n ## Notes<\/p>\n * Designed for stability and long-term usage Lobby and limbo manager for BungeeCord and Velocity with smart fallback, queue system, and automatic player routing across servers.<\/p>\n","protected":false},"featured_media":94927,"template":"","meta":{"_minecraft_slug":"lobbylimbomanager","_minecraft_project_id":"q7l7u4o7","_minecraft_author":"Hall127","_minecraft_license":"Apache-2.0","_minecraft_downloads":5,"_minecraft_follows":0,"_minecraft_client_side":"unsupported","_minecraft_server_side":"required","_minecraft_storage_type":"zip","_minecraft_archive_name":"lobbylimbomanager.zip","_minecraft_size_bytes":406718,"_minecraft_version_count":1,"_minecraft_updated_at":"2026-05-16T12:16:49.535463Z","_minecraft_date_created":"2026-05-08T01:32:06.357847Z","_minecraft_date_modified":"2026-05-04T22:02:18.831965Z","_minecraft_project_url":"https:\/\/modrinth.com\/mod\/lobbylimbomanager","_minecraft_icon_attachment_id":94927,"_minecraft_imported_at":"2026-06-05T10:26:45+00:00","_minecraft_import_hash":"593963db9a9b6e805062a9d6ded39689","_minecraft_versions":"","_minecraft_links":"","_minecraft_gallery":"","_minecraft_api_metadata":""},"mod_category":[894,126,90,92,985,992],"mod_loader":[895,986,993],"minecraft_version":[62,37,40,41,73,74,38,78,79,80,81,82,83,167,163],"class_list":["post-94926","mod","type-mod","status-publish","has-post-thumbnail","hentry","mod_category-bungeecord","mod_category-management","mod_category-optimization","mod_category-utility","mod_category-velocity","mod_category-waterfall","mod_loader-bungeecord","mod_loader-velocity","mod_loader-waterfall","minecraft_version-1-21","minecraft_version-1-21-1","minecraft_version-1-21-10","minecraft_version-1-21-11","minecraft_version-1-21-2","minecraft_version-1-21-3","minecraft_version-1-21-4","minecraft_version-1-21-5","minecraft_version-1-21-6","minecraft_version-1-21-7","minecraft_version-1-21-8","minecraft_version-1-21-9","minecraft_version-26-1","minecraft_version-26-1-1","minecraft_version-26-1-2"],"yoast_head":"\nSpoiler<\/summary>\n
\n# ============================================================
\n# LobbyLimboManager Configuration
\n# ============================================================
\n# This file controls how players are routed between lobby and
\n# limbo servers on BungeeCord, Waterfall, and Velocity proxies.
\n#
\n# IMPORTANT: Server names listed below must match the names
\n# defined in your proxy configuration EXACTLY.
\n# They are NOT case-sensitive in this file, but must exist.
\n# ============================================================<\/p>\n
\n# Config Version
\n# ———————————————————–
\n# This value is managed by the plugin. Do not modify it.
\n# Changing it may reset your configuration on next reload.
\nconfig-version: 1<\/p>\n
\n# LOBBY SERVERS
\n# ============================================================
\n# List all lobby servers that players can be sent to.
\n# These are the main servers players join when logging in or
\n# being recovered from a kick.
\n#
\n# NOTE: Names MUST match the servers defined in your proxy
\n# configuration (e.g. BungeeCord config.yml or Velocity
\n# velocity.toml). The plugin looks up servers by these
\n# names at runtime.
\nlobbies:
\n servers:
\n – lobby1
\n – lobby2
\n – lobby3<\/p>\n
\n# LIMBO SERVERS
\n# ============================================================
\n# Limbo servers are lightweight holding servers used when no
\n# lobbies are available or a player is queued.
\n#
\n# NOTE: A server listed here should NOT also be listed under
\n# lobbies. The plugin will ignore overlapping names in
\n# limbo selection.
\nlimbos:
\n servers:
\n – limbo1
\n – limbo2<\/p>\n
\n# SELECTION MODES
\n# ============================================================
\n# Controls how the plugin chooses which server to send a
\n# player to.
\nmodes:<\/p>\n
\n # ——————–
\n # Determines how a lobby is chosen when a player needs one.
\n #
\n # Valid values:
\n # ROUND_ROBIN – Cycles through lobbies in order.
\n # Example: lobby1 -> lobby2 -> lobby3 -> lobby1
\n # RANDOM – Picks a random available lobby.
\n # LEAST_PLAYERS – Picks the lobby with the lowest player
\n # count at that moment.
\n lobby-mode: ROUND_ROBIN<\/p>\n
\n # ——————–
\n # Determines how a limbo server is chosen.
\n #
\n # Valid values:
\n # FALLBACK – Limbos are ONLY used when no lobby is
\n # available. This is the recommended default.
\n # ROUND_ROBIN – Rotates through limbo servers independently.
\n # STANDALONE – Limbo servers are never used automatically.
\n # They must be targeted manually.
\n limbo-mode: FALLBACK<\/p>\n
\n# FALLBACK SETTINGS
\n# ============================================================
\n# Controls what happens when a player is kicked from a server.
\n#
\n# Fallback Flow (in order):
\n# 1. If kick message contains a no-fallback keyword, the
\n# player is disconnected (no recovery attempted).
\n# 2. If fallback-to-lobby is enabled, the plugin tries to
\n# find another available lobby.
\n# 3. If no lobby is available and fallback-to-limbo is
\n# enabled, the player is sent to a limbo server.
\n# 4. If nothing is available, the kick proceeds normally.
\nfallback:<\/p>\n
\n # Set to false if you want kicked players to disconnect
\n # instead of being moved to another lobby.
\n fallback-to-lobby-enabled: true<\/p>\n
\n # If both this and fallback-to-lobby are false, kicked
\n # players will simply be disconnected.
\n fallback-to-limbo-enabled: true<\/p>\n
\n # ——————–
\n # Controls which servers are allowed to trigger fallback.
\n #
\n # Mode: allow
\n # Only servers listed below PLUS all lobby servers can
\n # trigger fallback. All other servers will disconnect
\n # players on kick.
\n #
\n # Mode: deny
\n # Servers listed below will NEVER trigger fallback.
\n # All other servers (including lobbies) will trigger
\n # fallback normally.
\n servers-fallback-disabled:
\n mode: deny
\n servers:
\n – creative<\/p>\n
\n # ———————————
\n # If a kick message contains any of these keywords (case
\n # insensitive), the plugin will NOT attempt fallback.
\n # This is useful for bans, manual kicks, or anti-cheat
\n # disconnects where moving the player is undesirable.
\n #
\n # Examples of common keywords:
\n # banned – Prevents banned players from rejoining
\n # kicked by – Prevents staff kicks from triggering fallback
\n # timed out – Connection issues usually don’t need fallback
\n kick-message-nofallback:
\n – banned
\n – kicked by
\n – timed out
\n – disconnect.spam
\n – flying<\/p>\n
\n# QUEUE SETTINGS
\n# ============================================================
\n# When all lobbies are full, players are placed in a queue.
\n# These settings control how and when they are released.
\nqueue:<\/p>\n
\n # ————————–
\n # Number of consecutive successful health checks a lobby
\n # must pass before it is considered READY for queue dispatch.
\n #
\n # This works together with health-check-interval:
\n # If health-check-interval = 30 and this value = 2,
\n # a newly started lobby must be healthy for 60 seconds
\n # before queued players are sent to it.
\n #
\n # WARNING: Setting this too low (e.g. 1) may send players to
\n # lobbies that are still warming up, causing join
\n # failures. Setting it too high delays recovery.
\n #
\n # Recommended: 1-3 for quick recovery, 3-5 for stability.
\n dispatch-attempt-threshold: 1<\/p>\n
\n# GENERAL SETTINGS
\n# ============================================================
\nsettings:<\/p>\n
\n # ——————————-
\n # How often the plugin pings all configured servers to check
\n # if they are online, full, or offline.
\n #
\n # Trade-off: Lower values detect crashes faster but increase
\n # network load. Higher values are lighter but slower to
\n # react.
\n #
\n # Recommended: 30 for small networks, 60 for large networks.
\n health-check-interval: 30<\/p>\n
\n # ————————————–
\n # When a server fails a health check, it is marked as failed
\n # and will not be selected for routing until this time has
\n # passed AND it passes a new health check.
\n #
\n # This prevents repeatedly sending players to a crashed
\n # server.
\n failed-server-retry-seconds: 60<\/p>\n
\n # ————————
\n # How long the plugin remembers that it already tried to
\n # send a specific player to a specific server.
\n #
\n # This prevents infinite loops: if a player fails to connect
\n # to lobby1, the plugin won’t try lobby1 again for this
\n # duration. After expiry, it can be retried.
\n attempt-expiry-seconds: 30<\/p>\n
\n # ————————————–
\n # Minimum time between queue processing cycles.
\n #
\n # Lower values move players faster but increase CPU usage.
\n # The plugin will still respect server capacity and readiness.
\n queue-dispatch-interval: 2000<\/p>\n
\n # ———————————————–
\n # How often queued players receive a waiting message.
\n # Set to 0 to disable waiting messages entirely.
\n queue-waiting-interval: 5000<\/p>\n
\n # ———-
\n # When enabled, the plugin prints detailed state transitions,
\n # routing decisions, and queue activity to the console.
\n #
\n # WARNING: This generates a LOT of output. Only enable when
\n # troubleshooting. Disable for production.
\n debug: false<\/p>\n
\n # ——————–
\n # Defines the maximum number of players each server can hold.
\n # This is used to determine if a lobby is FULL and to decide
\n # how many queued players can be dispatched.
\n #
\n # Valid values for each server:
\n # -1 = Unlimited. The server is never marked FULL.
\n # 0 = Auto-detect. The plugin pings the server to read
\n # its max-player value (from server.properties or
\n # the server’s own configuration).
\n # >0 = Fixed limit. The server is marked FULL when its
\n # online player count reaches this number.
\n #
\n # Example: A survival server with 50 slots should be set to
\n # 50 so the plugin knows when it is full.
\n server-limits:
\n lobby1: 100
\n lobby2: 100
\n lobby3: 100<\/p>\n
\n# MESSAGES
\n# ============================================================
\n# All messages shown to players support Minecraft color codes
\n# using the ‘&’ symbol (e.g. &a = green, &c = red).
\n#
\n# Available placeholders:
\n# %server% – Replaced with the target server name
\n# %player% – Replaced with the player’s name
\n# %position% – The player’s position in the queue
\n# %total% – The total number of players in the queue
\n#
\n# NOTE: Placeholders only work in messages that reference them.
\n# Using an unsupported placeholder will leave the raw
\n# text in the message.
\nmessages:<\/p>\n
\n connect-lobby: “&aConnecting you to lobby &e%server%&a…”<\/p>\n
\n connect-limbo: “&eConnecting you to limbo server &7%server%&e…”<\/p>\n
\n fallback-lobby: “&eThe server you were on became unavailable. Moving you to &a%server%&e…”<\/p>\n
\n fallback-limbo: “&cAll lobbies are full or unavailable. Moving you to limbo &7%server%&c…”<\/p>\n
\n # Error \/ Status Messages
\n # ———————————————————–
\n no-lobby-available: “&cNo lobby servers are currently available. Please try again later.”
\n no-limbo-available: “&cNo limbo servers are currently available. Please try again later.”
\n no-server-available: “&cNo servers are currently available. Please try again later.”
\n server-not-found: “&cThe target server could not be found.”
\n already-connecting: “&cYou are already being connected to a server.”
\n command-player-only: “&cThis command can only be used by players.”
\n already-in-lobby: “&cYou are already connected to a lobby server.”<\/p>\n
\n # Queue Messages
\n # ———————————————————–
\n # These messages are sent automatically by the queue system.
\n queue-position: “&eYou are in position &c%position% &eof &c%total% &ein the queue.”
\n queue-join: “&cAll lobbies are full. You have been added to the queue.”
\n queue-waiting: “&eYou are in the queue. Position: &c%position%&e of &c%total%&e. Please wait…”
\n lobby-available: “&aA lobby is now available! Connecting you to &e%server%&a…”<\/p>\n
\n* Suitable for both small and large networks
\n* Focused on reliable routing and clean behavior<\/p>\n","protected":false},"excerpt":{"rendered":"