Permissions

Permissions

VelocityLimboHandler uses a small set of permission nodes to control queue behaviour and administrative access. These can be assigned through any Velocity-compatible permissions plugin (e.g. LuckPerms).

---

Permission Nodes

Permission	Description
vlh.queue.bypass	Skip the queue entirely on all servers — reconnects before all other players
vlh.queue.bypass.<server>	Same as above, but only for the specified server
vlh.queue.priority	Move ahead of normal players in the queue on all servers
vlh.queue.priority.<server>	Same as above, but only for the specified server
vlh.admin	Access to /vlh
vlh.admin.reload	Access to /vlh reload
vlh.admin.status	Access to /vlh status
vlh.admin.queue	Access to /vlh queue

Replace <server> with the backend server name as defined in your Velocity config, e.g. vlh.queue.priority.survival.

---

Queue Tiers

Permissions map to three internal tiers. When a server becomes available, players are reconnected in this order:

1. BYPASS — reconnected first, regardless of how long others have waited
2. PRIORITY — reconnected after all bypass players, but before normal players
3. NORMAL — default tier, first-come first-served

Within each tier, players are ordered by how long they've been waiting.

---

Admin Permissions

Administrative permissions are separate from queue priority permissions and control access to VelocityLimboHandler management commands.

• vlh.admin grants access to the base /vlh command
• Sub-permissions such as vlh.admin.reload or vlh.admin.status can be assigned individually for more granular access control
• It is recommended to grant vlh.admin.* only to trusted staff roles

---

Global vs. Server-Specific

Each queue permission has both a global and a server-specific variant:

• Global (vlh.queue.bypass, vlh.queue.priority) — applies to every server's queue
• Server-specific (vlh.queue.bypass.<server>, vlh.queue.priority.<server>) — applies only to that server's queue

Server-specific permissions take precedence if both are assigned. For example, a player with vlh.queue.bypass.survival gets bypass on survival even if they don't have the global vlh.queue.bypass.

---

Notes

• Players with no permission node default to the NORMAL tier automatically — no explicit permission is needed
• BYPASS should be granted sparingly; a large number of bypass players will consistently push normal players further back
• There is no permission to restrict players from being queued — the queue applies to everyone who connects to an unavailable server
• Administrative permissions do not affect queue priority or reconnect order