NexusShout 1.7.0

Added

Multi-proxy bridge: share global chat, /nmsg, /nr, the online player list, and the global chat toggle across several Velocity proxies through Redis. Off by default. Set it up in the new multi-proxy section of config.yml.
Each shared feature can be turned on or off: chat, private messages, online player list, toggle state, and cooldowns. Cooldown sharing is off by default, since it adds one Redis call per chat message.
The same discord.yml can run on every proxy. Chat goes to Discord only from the proxy where it was sent, and each Discord message reaches Minecraft once.
/nmsg and /nr work across proxies. Tab completion lists players on other proxies, and replies reach the player on whatever proxy they are on.
A player's global chat toggle follows them across proxies.
The proxy where a message is sent fills in the placeholders (rank, custom name, server display name) before sharing it, so the message looks the same on every proxy, even when permission data only exists on one.

If Redis cannot be reached at startup, a warning is logged and local chat keeps working.
If Redis goes down later, cross-proxy messages are lost while it is down, NexusShout reconnects on its own (waiting 1 to 30 seconds between tries), and the shared player list expires.
If Redis is down when a Discord message arrives, each proxy shows it to its own players once, without duplicates after Redis is back.
A crashed proxy's players drop off the shared player list after three times heartbeat-interval seconds.
With the bridge on, the first start creates plugins/nexusshout/proxy-id.txt with a random ID. Set multi-proxy.proxy-id to choose your own.
The new multi-proxy section is added to existing config.yml files on update.
Bundles Jedis 5.2.0 as the Redis client.
Treat Redis as trusted: anyone who can reach it can post into the chat channels. Use a password and a private network.
Use the same format on every proxy, since the sending proxy builds the message.
nshoutreload reconnects to Redis.