Support for Multiple Velocity instances

[vjh0107]

Hello, is there a way to use PlasmoVoice with multiple Velocity instances?
My server is currently running multiple Velocity instances behind a load balancer.
This is a common setup for large networks (1000+ players) using:

                                    ┌─────────────┐
                                ┌──→│ Velocity #1 │──┐
┌─────────┐    ┌─────────────┐  │   └─────────────┘  │   ┌─────────────┐
│ Players │───→│ LoadBalancer│──┼──→│ Velocity #2 │──┼──→│ Paper Server│
└─────────┘    └─────────────┘  │   └─────────────┘  │   └─────────────┘
                                └──→│ Velocity #3 │──┘
                                    └─────────────┘

Questions:

1. If the plugin is made with this in mind, how do I set it up?
2. is multiple proxy support on the roadmap?
3. Would you be open to a PR that adds Redis based session storage?

[apehum]

1. Depends on what you're trying to achieve.
   If you just want to make it work without Velocity-side addons support between proxies (e.g. groups, broadcast): create plugins/plasmovoice/aes-key (or use PLASMO_VOICE_AES_KEY env) with identical UUID (you can generate one here: https://www.uuidgenerator.net/) on all Velocity servers. This way players on the same backend (Paper Server) will hear each other on different Velocity servers.
2. data sync / packet forwarding between Velocity servers is not planned.
3. I'm not really sure what you want to achieve with Redis based session storage. Can you elaborate further on that?