How to Configure NuVotifier on a BungeeCord Minecraft Network

Overview

Server voting is one of the most common ways to promote a Minecraft network, and NuVotifier is the plugin many owners use to handle vote notifications. On a single server, the process is fairly direct. On a BungeeCord network, there are more moving parts because the proxy and each backend server need to communicate correctly.

The goal is simple: a vote arrives at the proxy, the proxy forwards it to the right backend server, and VotingPlugin runs the reward commands. The setup is not difficult, but one wrong port, token, or spacing issue can make the whole thing sulk quietly in a corner.

This guide explains how to install NuVotifier and VotingPlugin for a BungeeCord network, configure plugin messaging, add vote rewards, and fix the most common problems.

Install the Plugins

Before starting, make sure your BungeeCord proxy is already working and that your backend servers are connected. You will need NuVotifier and VotingPlugin installed where voting should be handled.

1. Open the NuVotifier and VotingPlugin pages on Spigot, then download both plugin `.jar` files.

1. Go to your server panel and open your FTP / file manager.

1. Sign in with your panel password, open the `plugins` folder, then choose Upload.

1. Upload the NuVotifier and VotingPlugin `.jar` files and wait until each upload reaches 100%.

1. Return to the main server panel and restart the BungeeCord server.

Repeat the needed plugin uploads for the backend servers in your network. The proxy must be able to receive votes, and the backend servers must be able to process them.

Configure NuVotifier on BungeeCord

After the restart, NuVotifier should create its configuration files. Start with the proxy, since this is where external voting sites will send vote data.

1. Open your server panel and return to your FTP / file manager.

1. Log in, then browse to:

`/plugins/NuVotifier/`

1. Open `config.yml` with the editor.

1. Find the default `port: 8192` value and change it to another open port, such as `8024`. Dedicated IP setups can often use `8192`, but some hosts may require help assigning or opening the port.

1. In the forwarding section, change `Method` to `pluginMessaging`.

1. Save the proxy file, then open the FTP area for each connected backend server.

1. Go to the backend NuVotifier or Votifier folder:

`/plugins/Votifier/`

1. Edit `config.yml` and copy the server's `Token` value.

1. In that same backend configuration, set the port to `-1` and set the method to `pluginMessaging`.

1. Return to the proxy's NuVotifier `config.yml`, then paste the backend server token into the server entry near the bottom of the file.

Make sure the backend server name, IP address, port, and token match the server you are adding. Repeat this for every backend server that should receive vote data.

You can optionally set `onlySendToJoinedServer` to `true`. With that enabled, votes are sent only to the backend server where the player is currently connected.

After saving the files, test a vote using the public RSA key from the BungeeCord NuVotifier setup. The key is stored in the plugin's `rsa` folder. If the test produces a message in-game, the forwarding path is working.

Set Up VotingPlugin Rewards

VotingPlugin can also be configured through MySQL, which is usually better for larger networks. That setup stores vote data in a shared database and is worth considering if you manage many servers. For smaller or simpler networks, configuring VoteSites on each backend server is usually enough.

1. Send test votes from every voting site you plan to use. This lets VotingPlugin generate the needed site entries.

1. Open the server panel for a backend server and open your FTP / file manager.

1. Log in, then open:

`/plugins/VotingPlugin/`

1. Edit `VoteSites.yml` and locate the generated voting site entries.

1. Under the `Rewards` section, add command rewards if none were created. Commands should not include a slash. Use `%player%` wherever the command needs the voter's username.

Example structure:

```yaml Rewards: Commands:

• give %player% diamond 1
• eco give %player% 100

```

Spacing matters in YAML, so keep indentation consistent. YAML is very polite until it is not.

1. Save the file once the rewards and messages match what you want players to receive after voting.

Repeat this process for each voting site on each backend server that should grant rewards.

Troubleshooting

Votes Do Not Register

Start by checking the proxy's NuVotifier configuration. The IP address and port for each backend server must be correct, and the forwarding method should be set to `pluginMessaging`.

Next, confirm the backend server configuration. The backend port should be `-1`, and its method should also be `pluginMessaging`. If either side uses the wrong method, votes may reach the proxy but never arrive at the backend server.

Finally, compare the token in the backend server's config with the token entered in the proxy's NuVotifier config. These must match exactly so the backend server can verify the vote data.

Rewards Do Not Run

If votes register but rewards fail, inspect `VoteSites.yml` carefully. Most reward problems come from incorrect YAML spacing, wrong command formatting, or missing placeholders.

Do not add `/` before reward commands. For example, use `give %player% diamond 1`, not `/give %player% diamond 1`.

If one voting site refuses to behave, delete that site's generated section, send another test vote, and configure the rewards again from the newly generated entry.

Useful References

• BungeeCord setup documentation
• NuVotifier BungeeCord wiki
• VotingPlugin BungeeCord guide