Best Practices - AkselGlyholt/velocity-limbo-handler GitHub Wiki

πŸ›‘οΈ Best Practices

Setting up VelocityLimboHandler properly ensures your players always have a stable fallback experience, especially during server restarts or maintenance. This page outlines recommended setups, performance tips, and security practices based on real-world usage.

🧭 1. Set Up Your Velocity Routing Correctly

In velocity.toml, use the try list or forced-hosts to send players to the Limbo server when their target server is unavailable.

Example using try:

try = ["main", "limbo"]

Or use forced-hosts for domain-based routing:

[forced-hosts]
"play.example.com" = ["main", "limbo"]

The name "limbo" must match your limbo-name in config.yml.

πŸ” 2. Keep task-interval Reasonable

  • Default is 3 seconds, which works well for most setups
  • Lower values (1–2 seconds) mean faster reconnects but slightly more load
  • Higher values (5–10 seconds) reduce load but delay reconnects

Adjust based on your proxy size and how quickly your backend servers boot up.

πŸ”” 3. Tweak queue-notify-interval for Player Clarity

Set to:

  • 20–30 seconds to give players occasional updates without spam
  • 0 to disable queue messages entirely

A good message rhythm helps reduce confusion, especially if the queue is long.

🚫 4. Always Block /server in Limbo

Add this to your config:

disabled-commands: ["server", "lobby", "hub"]

This prevents players from bypassing the reconnect queue. Combine it with LuckPerms for even tighter control (see Command Blocking).

πŸ§ͺ 5. Use Maintenance Mode When Restarting Servers

If you're using KennyTV’s Maintenance plugin, mark servers as under maintenance before restarting them.

This stops queue attempts until the backend is ready again β€” no spam, no wasted checks.

🧼 6. Keep the Limbo Server Clean

The Limbo server should be:

  • Lightweight (few/no plugins)
  • Empty or have minimal UI
  • Not your main lobby β€” treat it as a temporary holding zone

Some server owners use LimboAPI to create an ultra-fast, zero-resource Limbo server.

πŸͺ› 7. Monitor Your Logs

Keep an eye on the proxy logs for messages like:

[VelocityLimboHandler] Player xyz reconnected to main-server

Or any repeated failures. This helps you spot:

  • Broken backend names
  • Unreachable hosts
  • Excessive reconnect loops

βœ… Summary

Tip Why It Matters
Use try or forced-hosts Sends players to Limbo correctly
Tune task-interval Balances speed and performance
Block escape commands Keeps queue logic reliable
Use maintenance detection Prevents reconnect spam
Keep Limbo simple Reduces bugs and load