How to connect NuVotifier and reward votes

· MinecraftRating administration

NuVotifier receives vote events; VotingPlugin or another listener executes rewards. Installing the receiver alone does not grant items. Our own Paper test confirmed the complete website → receiver → listener → scoreboard command path.

Official resources

Use NuVotifier releases, its setup guide, VotingPlugin, reward documentation and Paper requirements. Choose compatible stable versions. The CI build used in our isolated test is not a production recommendation.

Install and link

Stop Minecraft, place both plugin JARs in plugins, start it and confirm both are enabled. Configure NuVotifier with a free TCP port, for example:

host: 0.0.0.0
port: 8192
disable-v1-protocol: false
forwarding:
  method: none

This standalone example is not proxy-network configuration. MinecraftRating currently sends v1. Allow that protocol and the selected TCP port through your hosting firewall, preferably restricted to monitoring senders; do not expose RCON. In My servers, verify ownership using MOTD, open Votifier integrations and save the public host, port and plugins/Votifier/rsa/public.key. Never upload private.key; localhost/private container addresses are not externally reachable.

Configure rewards

VotingPlugin must match ServiceSite: 'MinecraftRating.com'. Add an enabled vote site in VoteSites.yml with this service, a vote URL and DisplayItem such as DIAMOND. Example reward:

Rewards:
  Commands:
  - 'give %player% minecraft:diamond 1'

This command requires an online player. Configure deferred/offline rewards using the plugin documentation. ForceOffline only allows an offline command; it does not make give support offline inventories. Keep UUID mode consistent with your server. The website allows one vote per server/account/day in Moscow time and counts each vote for two calendar months; do not add a conflicting rolling cooldown without testing.

Verify delivery

Save the integration and send its test, then cast a real vote with the correct in-game nickname. Check NuVotifier logs, the reward handler and the actual command result. Our isolated offline test used scoreboard players add %player% mcr_votes 1, an existing dummy objective and explicit offline execution. Duplicate claims did not grant another point. Inventory, economy and permissions plugins need their own command checks.

FAQ

In v1 it means the packet was sent, not that the receiver decrypted it or executed a reward. Our wrong-key test reached SENT without changing the scoreboard. Check the current public key, ServiceSite, nickname, listener and online/offline rules.

Connection failed. Check public host, port, container mapping and firewall. A closed-port test produced a bounded TCP retry; restoring the endpoint restored reward execution. A local plugin test does not verify the monitoring network path.

No. Our container had a noexec /tmp; native SQLite could not load. We used a dedicated writable native directory and -Djava.io.tmpdir=/data/cache/native, with JNA/Netty directory settings. Use paths appropriate to your setup; do not broadly disable system protection.

The current MinecraftRating integration needs v1 compatibility. v2 support is a separate development task.

All articles