Configure NuVotifier and protect vote-receiver credentials

NuVotifier receives notifications from server-list voting sites and passes vote events to a reward listener. Receiving a vote and granting a reward are separate jobs. Test delivery first so reward configuration does not conceal a network or credential problem.

Check the installed platform and release

NuVotifier's public setup documentation is older than many current Minecraft releases. Do not interpret that as a guarantee that every old JAR supports the latest Paper or Java build. Check the actual release, platform instructions and startup result on a test copy before introducing it to your live server.

Keep a backup of the existing configuration and vote/reward data. Use the plugin installation guide for a standalone Paper setup. Proxy networks require the forwarding design documented by NuVotifier rather than independent public receivers that might reward the same vote twice.

Create the receiver endpoint

1. Confirm an unused TCP allocation assigned to your service. The default Votifier port from an example is not automatically yours.
2. Start the installed plugin once to generate configuration and credentials, then stop normally before editing.
3. Set the receiver port to that allocation and use the bind arrangement supported by your service. A container may not bind directly to its public address.
4. Start and check Console for the listener. If it reports an occupied or invalid address, resolve that exact issue before entering credentials on a voting site.
5. Register the public receiver address and port with a trusted server list, using the protocol and credentials it supports.

TCP web or game availability does not prove that the separate vote endpoint is reachable. Keep an endpoint record for each service so future migrations do not leave a listing pointed at an old machine.

Understand keys and tokens

Legacy Votifier-style RSA credentials have a public key and a private key. Share only the public key with a legitimate server list. Never upload the private key into a public ticket, screenshot, paste service or website configuration.

NuVotifier tokens are a different mechanism. They are secrets shared only with the intended list or forwarding component. A token does not replace an RSA public key on a site that expects the older protocol. Preserve matched keys when moving an existing service; regenerating them requires updating the corresponding listings.

Test delivery before real rewards

Use the trusted list's test facility with a controlled player identity. Note the time and check Console for the vote event. A locally simulated listener event tests the reward plugin but does not prove that an external site can reach your receiver.

Once delivery is confirmed, configure one modest reward in the chosen listener and test it separately. Avoid running several reward listeners unless you deliberately want each to respond. Record whether offline-player votes should wait until the player returns.

For failures, send support the server ID, receiving port, list name, timestamp and redacted error. Never include private keys or tokens. See collecting useful logs. Further reading: NuVotifier setup and forwarding and official release links.

Looking for another plugin? Browse the Minecraft plugin guide directory.