---
title: "Votifier Setup: Vote Rewards and Voting Sites | ZCS"
description: "Set up Votifier and a vote listener so players get rewards when they vote, with tests for ports, tokens and server lists."
url: "https://www.zcraftstudios.com/blog/votifier-vote-rewards-setup"
updated: "2026-10-20T07:16:50.972429+00:00"
source: "ZCraft Studios"
---

> Site index for AI agents: https://www.zcraftstudios.com/llms.txt (full reference: https://www.zcraftstudios.com/llms-full.txt). Every page is available as Markdown by adding `.md` to its URL or sending `Accept: text/markdown`.

1. [Home](https://www.zcraftstudios.com/)
2. [Blog](https://www.zcraftstudios.com/blog)
3. Votifier Setup: Vote Rewards and Voting Sites

[ All posts](https://www.zcraftstudios.com/blog)

# Votifier Setup: Vote Rewards and Voting Sites

ZCraft StudiosOct 3, 2026Updated Oct 20, 2026

Set up Votifier and a vote listener so players get rewards when they vote, with tests for ports, tokens and server lists.

## In this guide

- [Register the Server on a Voting Site](#register-the-server-on-a-voting-site)
- [Install Votifier](#install-votifier)
- [Opening the Votifier Port](#opening-the-votifier-port)
- [Rewarding Votes](#rewarding-votes)
- [Handling Offline Votes](#handling-offline-votes)
- [Vote Streaks and Milestones](#vote-streaks-and-milestones)
- [Verifying Votes Are Actually Working](#verifying-votes-are-actually-working)
- [What to Actually Reward](#what-to-actually-reward)
- [Putting this into practice](#putting-this-into-practice)
- [Reward delivery checks](#reward-delivery-checks)
- [Trace each stage of a missing reward](#trace-each-stage-of-a-missing-reward)
- [Official documentation and links](#official-documentation-and-links)
- [Debug votes that never turn into rewards](#debug-votes-that-never-turn-into-rewards)

## Setting Up Votifier and Vote Rewards

_A vote on a server-list site doesn't reach the server on its own. Votifier is the bridge that turns an external vote into an in-game reward._

Server-list sites (like a Minecraft server listing site) let players vote for a server, which can boost its visibility and ranking on that site. Votifier receives those votes and triggers an in-game event other plugins can react to, typically by giving a reward.

## Register the Server on a Voting Site

Before Votifier does anything, the server needs to actually be listed on a voting site, with a generated public key pair specific to that listing. The voting site uses this key to send authenticated vote notifications to the server.

## Install Votifier

[NuVotifierReceive server-list votes and forward them to reward plugins.On GitHub ](https://github.com/NuVotifier/NuVotifier)

Download NuVotifier from the project linked above. Check the supported Minecraft version, server platform, Java requirement and dependencies for the selected release.

1. Back up the server files and any plugin database.
2. Stop the server before changing JAR files. Put the compatible plugin build and its required dependencies in the correct plugin folder.
3. Start the server and read the startup log. Resolve missing dependencies or version errors before editing the generated configuration.
4. Stop the server, make one small configuration change, then restart and test it with a non-operator account.

Confirm NuVotifier loads after a clean restart. Test the feature you need with an ordinary player account before adding optional integrations.

## Opening the Votifier Port

Votifier listens on its own port (commonly `8192`, though configurable):

```
sudo ufw allow 8192/tcp
```

This port needs to be reachable from the voting site's servers specifically. If votes aren't registering, this is the first thing worth checking.

## Rewarding Votes

Votifier itself only receives and broadcasts the vote event. A separate rewards plugin (or a Skript script listening for the vote event) handles actually giving something to the player:

```
on vote:
    give player 1 of vote_pouch
    send "&aThanks for voting! Check your inventory." to player
```

## Handling Offline Votes

A player might vote while offline. Most vote-reward setups queue the reward and deliver it on the player's next join, rather than requiring the player to be online at the exact moment they vote. This is usually handled automatically by whichever rewards plugin processes the vote event.

## Vote Streaks and Milestones

Many servers reward consecutive daily voting (a "vote streak") with escalating rewards, encouraging players to vote regularly rather than once and never again. This requires tracking vote history per player, which most dedicated vote-rewards plugins handle natively rather than needing custom tracking built from scratch.

## Verifying Votes Are Actually Working

Testing an end-to-end vote (actually voting on the listing site, not just simulating the event) before launch confirms the public key, port, and reward pipeline are all correctly connected. A misconfigured key is a common reason votes silently fail to register despite everything else looking correctly set up.

## What to Actually Reward

A pouch-based reward (see the dedicated pouches guide) is a common choice for vote rewards specifically, since it gives players something tangible and tradeable rather than a flat currency deposit. ZCraft Studios' **[Deluxe Pouches Config](https://www.zcraftstudios.com/products)** includes tiers that work well repurposed as vote-reward pouches if that's the direction a server wants to take.

## Putting this into practice

A policy or gameplay change is only useful if players experience it consistently. Write a small rollout plan: what changes, who owns it, how it will be explained to the community, and when staff will review its effect.

### A practical rollout checklist

- \[ \] Describe the problem in one sentence before proposing a solution.
- \[ \] Choose one measurable sign of improvement, such as fewer repeat support tickets or better new-player completion.
- \[ \] Test the change with staff and a small group of players first.
- \[ \] Document rules, exceptions, and how decisions are reviewed.
- \[ \] Announce any player-facing change clearly before enabling it.
- \[ \] Revisit the result after a reasonable period and adjust if needed.

Avoid changing multiple systems simultaneously: it becomes harder to tell which change helped and which created a problem.

## Reward delivery checks

Test the full path from a legitimate vote event to the in-game reward. Check offline delivery, duplicate events, player-name handling and console errors. Publish any cooldowns and ensure repeated or forged events cannot grant unlimited rewards. Refer to the installed vote-receiver plugin's official documentation for supported test methods.

## Trace each stage of a missing reward

Separate receiving a vote from delivering its reward. Check the listener log for the test event, then inspect the plugin responsible for the reward. If the vote is recorded but the item is absent, opening another network port will not fix delivery. Use a known test player and preserve the event time. Review whether your system queues rewards for offline accounts and how players claim that queue after returning.

Decide how repeated or delayed events are handled before changing reward values. A network retry should not necessarily create a second reward. Test two deliveries representing the same event where your chosen tools offer a supported way to do so. Publish eligibility and daily limits in player help. Keep staff recovery steps clear about how to confirm a claim before granting a replacement, so support does not become another source of duplicate currency or items.

### Troubleshooting paths

- No vote event: inspect listener credentials, service configuration and reachability.
- Event exists but no reward: inspect delivery and offline storage.
- Duplicate reward: review event and claim handling before increasing limits.

\*

## Official documentation and links

- [Official project repository](https://github.com/NuVotifier/NuVotifier)
- [Minecraft Server Reward Systems That Don't Feel Pay-to-Win](https://www.zcraftstudios.com/blog/minecraft-server-reward-systems-fair)

## Debug votes that never turn into rewards

Identify whether the failure is between the voting website and the vote receiver, or between the receiver and the reward command. First look for a received-vote event in logs, then confirm the player name or identity and inspect the configured reward action. Do not blindly repeat live rewards while testing.

If a voting site only supports a particular integration protocol, confirm its documentation and the version your receiver actually implements. Test against a supported provider or official test facility.

## Continue reading

- [Minecraft Playtime Rewards Without AFK Farming](https://www.zcraftstudios.com/blog/minecraft-server-playtime-rewards-design)
- [Pouch Currency and Rewards System Setup Guide](https://www.zcraftstudios.com/blog/minecraft-currency-pouches-setup)

[ Previous guide Setting Up Jobs Reborn for Player Professions](https://www.zcraftstudios.com/blog/jobs-reborn-professions-setup)[ Next guide Setting Up ItemsAdder for Custom Items and Blocks](https://www.zcraftstudios.com/blog/itemsadder-custom-items-blocks-setup)