Effortlessly manage player reconnections with a structured queue system
Find a file
Repository files (latest commit first)
Filename Latest commit message Latest commit date
2026-08-22 15:15:09 +02:00
.github Update Java version matrix in test workflow 2026-02-12 19:07:00 +01:00
src Version checker 2026-08-05 17:34:58 +02:00
.gitignore first commit 2025-02-12 23:45:40 +01:00
CODE_OF_CONDUCT.md Create CODE_OF_CONDUCT.md 2025-06-25 13:39:21 +02:00
CONTRIBUTING.md Update contact email for reporting issues 2026-01-03 01:48:00 +01:00
LICENSE Create LICENSE 2025-02-13 00:56:45 +01:00
pom.xml Bump version from 1.8.3 to 1.8.4 2026-06-12 18:12:17 +02:00
readme.md Update Minecraft versions compatibility in README 2026-08-22 15:15:09 +02:00
SECURITY.md Update SECURITY.md 2025-07-27 17:04:01 +02:00

VelocityLimboHandler

🌀 A smart limbo & queue handler for Velocity
Keeps your players connected, calm, and coming back even when backend servers crash.


GitHub release GitHub downloads License Modrinth


Why VelocityLimboHandler?

  • 🚦 Per-Server Smart Queue players only wait for the server they were on, not behind others stuck elsewhere
  • 📢 Queue Updates automatic position notifications keep players informed
  • 🔒 Protected Limbo blocks unwanted commands to prevent bypasses
  • 🛠️ Maintenance Support respects whitelist & bypass permissions
  • 🤝 Authentication Ready seamless integration with authentication plugins such as LibreLogin or nLogin

👉 Full setup & advanced features in the Wiki.

Made to work with LOOHP's Limbo server, but any other server is also fine.


🧩 Compatibility

  • 🖥️ Proxy: Velocity (all recent versions)
  • 🎮 MC Versions: All versions
  • 📜 License: GPL-3.0

🚀 Quick Install

  1. Grab the latest .jar from Releases.
  2. Drop it into your Velocity plugins folder.
  3. Restart the proxy (config files will generate).
  4. Adjust config.yml + messages.yml to your liking.
  5. Restart once more — done! 🎉

⚙️ Config Highlights

# config.yml
limbo-name: "limbo"                  # The name of your limbo server
direct-connect-server: "lobby"       # Where to send direct connections
task-interval: 3000                  # Queue processing interval (milliseconds)
reconnect-batch-size: 8              # Maximum backend queues checked per processing run
queue-notify-interval: 30            # How often to tell players their position
queue-notify-batch-size: 64          # Maximum due notifications sent per dispatcher tick
disabled-commands: ["server","hub"]  # Commands blocked in limbo

The batch limits smooth work across scheduler ticks. Increase them for faster catch-up on very large networks, or lower them to cap short CPU bursts on constrained proxies.

👉 Messages can be tweaked in messages.yml so your players see exactly what you want.


🖧 Proxy Setup Example

[servers]
default = "lobby"
limbo = "limbo"

[forced-hosts]
"pvp.example.com" = ["pvp", "limbo"]
"build.example.com" = ["build", "limbo"]

🛡️ Permissions & Integrations

  • Players get queued automatically, no setup required.
  • Commands blocked per config.
  • LibreLogin support ensures login/auth flow isnt broken.
  • Maintenance plugins are respected (bypass logic included).

🤝 Contributing

Pull requests are welcome! Just follow the style already in place. Check CONTRIBUTING.md for details.


📖 License

Licensed under GPL-3.0 — free to use, modify, and share under the same license.