DaisyVotes — Quick Start

Already installed? This page gets you to a confirmed, working vote as fast as possible.

The fastest path

1. Run the doctor. It checks the whole setup and tells you exactly what (if anything) to fix:

   /daisyvotes doctor

2. Fix any ✘ (and ideally ⚠) items. Each line includes a one-line hint. The most common first-run items are placeholder vote URLs and the receiver port not being open or forwarded.

3. Simulate a vote to confirm rewards land:

   /daisyvotes testvote <yourname>

   With no site argument, testvote simulates a vote on every configured site at once — so it also completes the daily wheel set, letting you test /vote spin immediately.

4. Open the dashboard and try the menus:

   /vote          # the candle dashboard
   /vote stats    # your stats
   /vote top      # the leaderboard
   /vote shop     # spend vote points

Reading the doctor output

/daisyvotes doctor prints a checklist. Here’s a typical fresh-install result, before you’ve replaced the example URLs:

━━━━━━ Setup Doctor ━━━━━━
✔ Vote receiver — Embedded receiver listening on 0.0.0.0:8192.
✔ Receiver protocol — v2 token + v1 RSA
⚠ Receiver protocol v1 — Legacy RSA protocol is enabled for compatibility.
   Prefer Votifier/NuVotifier v2 tokens on voting websites when available.
✔ Receiver security — 1 token(s), duplicate window 10s, rate limit enabled.
✔ Receiver migration — No legacy NuVotifier config detected.
✔ Redis network — Disabled. Single-server mode is active.
✔ Vote sites — 5 site(s) configured.
⚠ Site links — Placeholder vote URLs: minecraftservers, planetminecraft, minecraftmp, topg, bestservers.
   Replace each url in menus.yml with your server's real vote page.
✔ Daily wheel — Spin after voting 5 of 5 site(s).
✔ Vote security — Strict mode: only configured sites are accepted. Duplicate window: 10s.
✔ Rewards config — 24 reward action(s), no validation issues.
✔ Reward commands — No command rewards configured; defaults are vanilla-safe.
✔ Database — Write/read/delete probe succeeded.
✔ PlaceholderAPI — Hooked — %daisyvotes_*% placeholders are live.
✔ Features — reminders, offline rewards, wheel, discord (off), effects, vote shop, bstats
⚠ No blockers, 2 warning(s) worth a look.

Symbol	Meaning
✔	Pass — nothing to do.
⚠	Warning — works, but worth a look (e.g. example URLs still in place).
✘	Fail — a blocker; votes won’t work correctly until it’s fixed.

Tip

Run /daisyvotes doctor network to additionally send a request to each vote-page URL and report whether it’s reachable. This takes a few seconds.

What the doctor checks

• Vote receiver is enabled and listening, with its protocols and token/key security.
• Receiver migration — whether an old NuVotifier config was found and imported.
• Redis network — connected, or disabled for single-server mode.
• Vote sites exist, have unique ids and slots, and don’t still use example URLs.
• Daily wheel — whether wheel.requiredSites matches your configured site count, and the reset zone is valid.
• Vote security — strict vs. lenient mode and the duplicate window.
• Rewards validate and any command rewards reference plugins you likely have.
• Database can be written, read, and deleted.
• PlaceholderAPI is hooked (optional).
• A feature summary of what’s currently on or off.

Seeing no votes from real sites?

If testvote works but real votes never arrive, the problem is almost always the connection between the vote site and your receiver — the port isn’t open/forwarded, the token or public key on the site doesn’t match, or a service name that doesn’t match a site’s service-aliases. Head to Troubleshooting.

Next steps

Configuration Tune visuals, engagement, the wheel, points, parties, and more.

Rewards Make the rewards yours — items, commands, messages, and chances.

Commands & Permissions Every command and permission node.