A vote has two separate jobs: it counts on the server list, then a notification reaches your Minecraft server so a reward plugin can act on it. If the first part works and the player gets nothing, the missing step is usually the notification or the reward listener.
This guide covers a single Java server first, followed by proxy networks. You need access to the server files, startup logs, network port allocation and your MinecraftIP listing. Take a configuration backup before changing a working setup.
What you need before starting
- A compatible receiver: NuVotifier receives vote notifications. Download it from the project's own links and check support for your server platform.
- A reward listener: a plugin such as VotingPlugin decides what to give a player. Installing the receiver alone does not define rewards.
- An allocated TCP port: ask your host for an additional port if your panel does not let you allocate one. The Minecraft game port and the vote port are different services.
- A test player: use an account whose inventory and reward balance you can inspect. Test notifications can trigger real rewards.
The NuVotifier project provides its supported platforms and setup documentation. The VotingPlugin wiki covers reward configuration. Follow the instructions for the versions you actually install rather than copying an old configuration wholesale.
Install and configure the receiver
- Stop your server cleanly. Install the compatible NuVotifier build in the location required by your server platform, then start the server to generate its configuration.
- Read the startup log. Resolve plugin loading errors before editing the listing; a correctly filled web form cannot reach a receiver that never started.
- Stop the server again and configure the listener's bind address and allocated port. The bind address belongs to the server's local network configuration. It is not necessarily the public address players use.
- Allow inbound TCP traffic to that port through the host panel or firewall. On a home connection, port forwarding may also be necessary. A shared hosting allocation must belong to your instance.
- Restart and check for a successful listener startup. “Address already in use” usually means another service has the port; a binding error can mean the configured address is not assigned to the machine.
MinecraftIP initially suggests port 8192, but your host's allocation is the value that matters. Do not replace an allocated port with 8192 simply because a guide uses it as an example.
Choose the matching protocol and credentials
| Protocol | What to enter | Common mistake |
|---|---|---|
| NuVotifier v2 | The shared token from the NuVotifier configuration for the service shown in your listing form, or its applicable default token. | Pasting an RSA public key into the token field. |
| Classic Votifier v1 | The contents of the receiver's public key file. | Using a private key or selecting v2 while supplying a v1 key. |
Use v2 when your receiver supports it. Treat its token as a secret: enter it only in trusted administration forms, keep it out of public screenshots, and rotate it if exposed. For v1, the listing needs the public key, never the private key.
In your server listing's vote-reward settings, enter the externally reachable host, the allocated port, the selected protocol and its corresponding credential. Save the form. Match the service name displayed there to your listener's vote-site configuration; do not assume every listing website uses the same name.
Test delivery and rewards separately
Open the MinecraftIP Votifier tester with the same connection details and a test username. Watch the server console while sending one notification. A transport success is a useful checkpoint, but the final check is whether the correct player receives exactly the intended reward.
- Confirm that the receiver logs the vote with the expected username and service name.
- Confirm that the reward listener recognizes that service and runs its configured action.
- Check the player's inventory or balance. Keep the initial reward simple so you can identify it unambiguously.
- Repeat with the player offline if your listener supports queued rewards, then join and check delivery. Do not promise offline rewards until this test passes.
- Submit a normal vote through the listing and verify the complete path once. Record the result and remove any temporary test rewards.
Find the failed step
| Symptom | Check next |
|---|---|
| Connection times out | Public host, TCP firewall rule, host allocation and routing. A working game connection does not prove the vote port is reachable. |
| Connection refused | Whether the receiver is running and listening on that port. Recheck the startup log. |
| Authentication fails | Protocol selection, token or public key, and the service-specific token configuration. |
| Vote arrives but no reward | Listener installation, service-name matching, reward conditions, command errors and username handling. |
| Rewards arrive twice | Duplicate listeners, overlapping reward rules or multiple proxy forwarding paths. |
For proxy networks, decide where a vote enters
Draw the route before configuring forwarding: listing website → public receiver → intended backend → reward listener. Use the NuVotifier documentation for your proxy and forwarding method. Decide whether a reward belongs on one survival server, the player's current server or a shared network balance. Those are different policies and should not happen accidentally.
Test with a player in the lobby, on a backend and offline. Check that switching servers does not award the same vote again. If rewards use a shared database, include a restart and reconnection in your test plan. Keep a short record of the port, receiving instance and forwarding destination so a later migration does not break voting silently.
Common questions
Does a successful vote on MinecraftIP guarantee an in-game reward?
No. Recording a vote and notifying the server are separate operations. The server's receiver and reward configuration must also work. If a notification fails, check the delivery error and server logs before changing reward amounts.
Can I reuse my Minecraft server address?
The hostname may be the same, but the vote listener still needs its own reachable port. On hosted networks the voting endpoint may be a different address supplied by the host.
What should I give voters?
Start with a modest, predictable benefit that fits your economy, such as a small supply bundle or cosmetic progress. State the reward and any claim conditions clearly. Track the total currency introduced over a week before increasing it.
Building the rest of your server setup? Read the plugin planning and testing guide before adding more dependencies.