Voting your players come back for

Receives its own votes. No NuVotifier, no database setup, every menu yours to configure.

Install in five minutes Read the config reference

/vote opens a dashboard, not a list of links. A lit candle is a site the player can vote on now; a dimmed one is on cooldown, with the time remaining on it. Every slot, material, name and line of text in that menu comes from menus.yml, including the buttons that aren’t candles.

Start here

Install Drop in the JAR, point your vote sites at it, confirm with /daisyvotes doctor.

Set up your vote sites Service aliases decide whether a vote is accepted. This is the page people skip and shouldn't.

Common setups Crate keys for voting, monthly top-voter prizes, per-world restrictions, with config you can paste.

Decide the rewards Vote, streak, party, wheel, milestone and cumulative rewards, with vanilla-safe defaults.

Upgrading Coming from 2.0 or 2.5? Read this before replacing the JAR.

What it does that others don’t

It receives its own votes. Votifier v1 and v2, built in. NuVotifier is not required, and if you already run it your port, tokens and RSA keys are imported on first start, so your vote sites need no changes. Keep NuVotifier if you’d rather; there’s a bridge mode.

Every menu is configuration, not code. Move a button, change its material, rewrite its lore, or delete it with enabled: false. Buttons carry a second item for their quiet state, so “no spins left” can look different from “spin ready”.

Per-site cooldowns that match reality. Vote sites don’t agree: some allow another vote eight hours later, others reset at midnight in their own timezone. At 23:00 a plugin assuming a rolling 24 hours tells your player to wait a day. DaisyVotes tells them one hour.

It is honest about failure. /daisyvotes doctor checks the receiver, your site aliases, reward commands, storage, file permissions and menu layout. On a network it also checks whether your servers can actually see each other. It tells you which one is wrong, and how to fix it.

Reading vote data from your website

The tables are plain SQL and documented: leaderboards, per-player totals, and the full vote log. There is one thing you must get right, and it is not obvious, so it has its own page.