Command Blocking - AkselGlyholt/velocity-limbo-handler GitHub Wiki
🚫 Command Blocking in Limbo
To keep players from bypassing the reconnect queue or accessing parts of your network too early, VelocityLimboHandler lets you block specific commands while players are in the Limbo server.
This prevents common issues like:
- Players using
/server
to switch out of Limbo - Joining other game modes manually before their original server is ready
- Abusing shortcuts like
/hub
or/lobby
while in queue
⚙️ How It Works
The plugin watches for commands typed by players in Limbo. If a command matches one listed in the disabled-commands
section of config.yml
, it gets cancelled — and the player receives no response.
🧾 Config Example
disabled-commands: ["server", "lobby", "hub"]
This will block:
/server
/lobby
/hub
Even if the player tries capitalized versions or uses extra arguments, the plugin will catch and block them (/server skyblock
, /hub
, etc.).
💡 Best Practices
- Always block
/server
unless you have a good reason not to, or you have disabled reconnection - Block any custom shortcuts that let players escape Limbo early
- Keep the list short and focused to avoid confusing players
You don’t need to block normal chat or helpful commands like
/msg
, unless they cause problems.
LuckPerms
🛡 Optional: Add Context withWant finer control over what players can do in Limbo?
You can combine command blocking with LuckPerms context-based permissions:
/lp group default permission set velocity.command.server false server=limbo
This denies /server
only when a player is on the Limbo server — even if they’re normally allowed to use it.
Useful for:
- Preventing access without completely disabling commands everywhere
- Keeping admin/debug commands available while still locking down Limbo
❌ Disabling Command Blocking
If you don’t want to block any commands in Limbo, simply just leave it empty:
disabled-commands: []
🧪 What It Doesn't Do
- It doesn’t block plugin messages or BungeeCord plugin channels
- It doesn’t interfere with server-side command blocks or backend execution