DaisyVotes — Installation

This guide takes you from a fresh download to a tested, working voting setup in about five minutes. No NuVotifier required — DaisyVotes has its own built-in vote receiver.

Before you start

You’ll need:

A Paper 1.21+ server on Java 21+.
Your server’s vote pages on the server lists you want to support.
A port you can open to the internet for incoming votes (default 8192).

Steps

Add the JAR.

Download DaisyVotes from your BuiltByBit purchase and drop the JAR into your server’s plugins/ folder.

BuiltByBit downloads have your license key embedded — there is nothing to paste. The license: section in config.yml fills itself in after the first successful start. Treat any saved key like a private credential.
Start the server.

Start your Paper server once to generate the config files:
- Directoryplugins/DaisyVotes/
  - config.yml main settings
  - receiver.yml built-in vote receiver (port, tokens, keys)
  - menus.yml vote sites & GUI
  - rewards.yml rewards
  - shop.yml vote points shop
  - storage.yml storage backend
  - network.yml cross-server (Redis) — off by default
Connect your vote sites to the receiver.

The receiver listens on 0.0.0.0:8192 by default. Open that port in your firewall and forward it so vote sites can reach it. In each site’s Votifier settings, enter your server’s host/IP and the port, then give it the credential it asks for:
- Token (v2 / NuVotifier — most sites): use the default token already in receiver.yml under tokens.default — one token works for every site. Per-site tokens are optional; create one only if you want a listing isolated:
  Terminal window
```
/daisyvotes receiver token create minecraftservers   # optional — isolated per-site token
```
- Public key (legacy v1 sites): run /daisyvotes receiver publickey and paste the printed key into the site’s public-key field.
Your rsa.private-key must never leave the server — don’t paste it anywhere. Only the token and the public key go to vote sites.

DaisyVotes already imported your old port, tokens, and keys on first start — your sites keep working. Just confirm with /daisyvotes receiver status, then you can remove NuVotifier.

Set your vote links and service names.

In menus.yml, for each site set its real url and make sure service-aliases includes the exact service name the list sends. The service name is how DaisyVotes matches an incoming vote to a site.

vote-menu:
  sites:
    - id: minecraftservers
      slot: 20
      url: "https://minecraftservers.org/vote/<your-server>"
      service-aliases:
        - "Minecraft Servers"      # ← must match the list's Votifier service name
        - "minecraftservers.org"

See Vote Sites & Menus for the full breakdown.

Tune your rewards.

The defaults in rewards.yml and shop.yml are vanilla-safe (diamonds, emeralds, XP, messages) and work on any server. To grant economy money, crate keys, or ranks, add Command rewards that match your plugins:
rewards.yml (example Command reward)
```
vote-rewards:
  - type: Command
    value: "eco give %player% 500"     # use YOUR economy plugin's command
    display-name: "500 Coins"
```
Full details: Rewards and Vote Points & Shop.
Apply your changes.

Run /daisyvotes reload to load config edits without a restart.
Verify everything.
Terminal window
```
/daisyvotes doctor          # checks the receiver, sites, rewards, storage, and more
/daisyvotes testvote Notch  # simulates a full vote so you can confirm rewards land
```
doctor prints a ✔/⚠/✘ checklist with a fix hint for anything that isn’t right. Add network (/daisyvotes doctor network) to also probe each vote-page URL.

You’re done

Votes now flow straight into DaisyVotes’ receiver, populate the dashboard, grant rewards, and drive streaks, points, the wheel, and parties.

Vote Receiver Everything about the built-in receiver, tokens, and keys.

Quick Start A guided first vote and a tour of the doctor output.

Troubleshooting & FAQ No votes arriving? Start here.