Skip to content

DaisyVotes — Overview

DaisyVotes is a premium voting and vote-party plugin for modern Paper servers. It pairs a polished pastel candle dashboard with a full engagement loop — a vote points economy and shop, a daily reward wheel, streaks with milestone rewards, server-wide vote parties, top-voter leaderboards, Discord webhooks, and a complete PlaceholderAPI expansion — all backed by an async SQLite database that needs zero setup.

It ships with vanilla-safe defaults: a brand-new server with no economy or crate plugin still gets a complete, working voting experience out of the box. Every piece of text uses MiniMessage, and every config file is plain YAML.

Candle Dashboard

A themable /vote GUI where each site is a candle — lit when ready, dimmed on cooldown. Configure layout, items, and links in menus.yml.

Vote Points & Shop

New in 2.0 Earn points per vote and spend them in /vote shop, with per-item costs, daily limits, and optional permissions.

Daily Reward Wheel

New in 2.0 Vote every site in a day to earn a spin on a weighted wheel, with optional broadcasts for rare prizes.

Streaks & Freezes

Daily streaks with a grace window, milestone rewards at 3/7/14/30/60/100 days, and earnable freezes that protect a missed day.

Vote Parties

Server-wide goals with three reward modes, progress broadcasts, a countdown title, and a boss bar.

Top Voters

New in 2.0 Daily / weekly / monthly / all-time leaderboards plus automatic Top 3 awards each period.

Discord Webhooks

New in 2.0 Post styled embeds on votes, parties, streak milestones, and rare wheel wins — no bot required.

PlaceholderAPI

A full %daisyvotes_*% expansion for HUDs, scoreboards, and holograms — votes, streaks, points, party progress, and ranks.

Built-in Receiver

New in 2.0 Receives votes itself (Votifier v1/v2) — no NuVotifier needed. Imports your existing setup automatically.

Cross-Server

New in 2.0 Run a whole network off one shared database, with optional Redis for instant cross-server delivery and parties.

The default dashboard is a six-row menu with five vote-site candles, each opening its vote link on click. Everything here — slots, materials, names, and lore — is configurable in menus.yml.

Screenshot placeholder Drop a real in-game capture here
The /vote dashboard in-game
RequirementDetails
Server softwarePaper 1.21+ (declares api-version: 1.21). Spigot is not supported; Paper or a Paper fork is required.
Java21 or newer.
Vote receiverBuilt in. DaisyVotes ships its own vote receiver (Votifier v1/v2) — NuVotifier is not required. It listens on a port you open (default 8192).
NuVotifierOptional. Only if you’d rather keep it (bridge mode); DaisyVotes imports its config automatically.
PlaceholderAPIOptional. Only needed for %daisyvotes_*% placeholders. Everything else works without it.
StorageSQLite (default, zero setup), or MySQL/MariaDB for a multi-server network.
FoliaNot supported.

On first start, DaisyVotes generates its YAML config files plus its database in plugins/DaisyVotes/:

  • Directoryplugins/DaisyVotes/
    • config.yml Main settings — visuals, engagement, wheel, points, parties, Discord, messages
    • receiver.yml Built-in vote receiver — port, tokens, keys
    • menus.yml Vote sites and GUI layout
    • rewards.yml Every reward: per-vote, first vote, streaks, party, wheel, milestones, cumulative
    • shop.yml Vote points shop entries
    • storage.yml Storage backend (SQLite by default)
    • network.yml Cross-server (Redis) — off by default
    • an SQLite database file, created automatically by Sculk Data

Each file is documented in detail:

  1. A player votes on a server list. The list sends the vote to DaisyVotes’ built-in receiver.
  2. DaisyVotes matches the vote to a configured site, drops duplicates, and processes it asynchronously.
  3. It updates the player’s counts, streak, points, and the server vote-party progress, then grants rewards (queuing them if the player is offline).
  4. It checks the daily wheel set, fires Discord embeds, plays effects, and broadcasts as configured.

See Voting & Anti-Fraud for the full lifecycle, or head to Installation to get started.