We use a RedisBungee fork for Velocity on a single Velocity instance (for non-standard reasons) but as of VelocityControl 1.0.8, if RedisBungee is detected it always uses it for communications (which we don't want right now).
There's two issues here:
I'd like the option to disable Redis integration, even if RedisBungee is detected.
The Redis integration doesn't seem to work. Chat seems to break entirely with the Redis integration. Looking at the code, it seems like VC only sends messages to other proxies via Redis and not to local backend servers via plugin messages. Is this intended? How do local backend servers receive messages in this scenario?
It's possible my setup is different to expected or not compatible somehow, but currently we are unable to use VC 1.0.8 until at least the first issue is fixed.
Hope this description makes sense? Not sure what other logs/info I can provide?
Error log (if applicable)
No response
"/chc debug" output (strongly recommended)
No response
Information about the issue/bug
We use a RedisBungee fork for Velocity on a single Velocity instance (for non-standard reasons) but as of VelocityControl 1.0.8, if RedisBungee is detected it always uses it for communications (which we don't want right now).
There's two issues here:
It's possible my setup is different to expected or not compatible somehow, but currently we are unable to use VC 1.0.8 until at least the first issue is fixed.
Hope this description makes sense? Not sure what other logs/info I can provide?