Multi Proxy REDIS

Multi-Proxy REDIS

Configure each proxy as its own working VotingPlugin proxy network before enabling multi-proxy support. Each proxy network may use a different backend forwarding method.

When a proxy network already uses BungeeMethod: REDIS, give each network a different regular Redis prefix so their backend traffic does not overlap.

Use the following command to check multi-proxy connectivity:

/votingpluginbungee multiproxystatus

A status message should appear in the console of each configured proxy.

Primary proxy

Choose one proxy as the primary proxy. The primary normally receives votes from VotifierPlus and coordinates the multi-proxy system.

Example configuration

MultiProxySupport: true

# Enable only on the primary proxy.
PrimaryServer: true

# Give only one network reward when configured with the matching options.
MultiProxyOneGlobalReward: false

# Current multi-proxy methods include REDIS and SOCKET.
MultiProxyMethod: REDIS

MultiProxyRedis:
  # Reuse the normal Redis connection only when the proxy itself uses BungeeMethod: REDIS.
  UseExistingConnection: false
  Host: localhost
  Port: 6379
  Username: ''
  Password: ''

# Unique name for this proxy.
ProxyServerName: proxy1

# Names of the other proxies. A non-primary proxy normally lists the primary.
ProxyServers:
  - proxy2
  - proxy3

For one global reward across the entire multi-proxy network, configure both options as follows on every proxy:

MultiProxyOneGlobalReward: true
SendVotesToAllServers: false

Leaving SendVotesToAllServers enabled can forward the same vote to multiple backend servers and allow more than one reward.

Multi-proxy support is advanced. Test vote forwarding, duplicate prevention, reconnect behavior, and reward delivery before using it in production.

AI disclosure: This documentation update was written with assistance from ChatGPT.