In the standard layout, VotifierPlus and VotingPlugin run on the proxy, while VotingPlugin runs on each backend server. Custom vote-routing layouts may differ.
The MYSQL method uses a shared MySQL-backed message queue. It creates the VotingPlugin_message_queue table and may not be compatible with every MySQL-compatible service.
bungeeconfig.ymlBungeeMethod: MYSQL
Configure the shared MySQL connection and provide enough connections for the proxy and backend workload. The current documentation recommendation is at least five total connections across a small network, with additional headroom for larger installations.
Restrict the database listener to the proxy and backend addresses, use a
dedicated account with only the required schema permissions, and never post
the connection password in logs or support screenshots. See
Data storage and migration
for released MariaDB/PostgreSQL driver selection and JDBC prerequisites.
BungeeSettings.ymlUseBungeecord: true
BungeeMethod: MYSQL
Server: SERVERNAMEHERE
Each backend must have a unique Server value that matches the name known by the proxy.
Config.ymlConfigure the same MySQL database used by the rest of the network.
The proxy and backend settings are separate and use different capitalization:
# Backend Config.yml
AllowUnjoined: true
bungeeconfig.yml: AllowUnJoinedConfig.yml: AllowUnjoinedIn the standard proxy-managed layout, keep proxy AllowUnJoined: false so the
proxy rejects votes for players it cannot validate, and set backend
AllowUnjoined: true so forwarded votes are not rejected a second time.
Disable SendVotesToAllServers when the network should give only one server reward per vote. Leave it enabled when each applicable backend should process the forwarded vote.
/votingpluginproxy status
/votingpluginproxy vote <player> <site>
Check the proxy and backend consoles for status results and queue-processing errors.
Server value.VotingPlugin_message_queue can be created and updated./votingpluginproxy status before testing vote rewards.