Feature Request: Multiple Specifications for Hub Sender [Not A Bug]
R00tB33rMan opened this issue · comments
VelocityTools is very versatile and effective for large production networks that are desiring additional useful features for their networks.
In my opinion, this resource could be perfected by allowing the specification for multiple servers when executing /hub & /lobby, in acting as a load balancer to mitigate the use of other plugins, when this one could easily do this for us.
To visualize, it could look like this:
hub:
enabled: true
servers: ["Hub-1", "Hub-2", "Hub-3"]
# Set to "" to disable.
you-got-moved: "&aYou have been sent to a lobby."
disabled-server: "&cThis server is currently unavailable."
disabled-servers:
- "foo"
- "bar"
aliases:
- "hub"
- "lobby"
I thank you for being so diligent in ensuring this resource is production-ready and hope to see this feature implemented. Thanks for reading! (I wasn't sure where else to post this).
Bro if rootbeer said it, it's a fact and should be implemented.
Vouch from bluejay owner of Valatic the biggest fastest-growing server in existence.
This is a very crucial feature that should be implemented.
🤔
🤔
Aha. They're all friends of mine that would like to see this implemented. snap + MultiLobby isn't entirely ideal. We've encountered some issues.
Okay, I'll do it today.
You're amazing. Keep up the excellent work. I do have some other implementations in mind, but they might go beyond the simplicity of your resource. (More specifically for on-join balancing).