DaisyVotes — Troubleshooting & FAQ
Start with the doctor
Section titled “Start with the doctor”Before anything else, run:
/daisyvotes doctor # full setup check/daisyvotes doctor network # also probes each vote-page URLIt prints a ✔/⚠/✘ checklist with a fix hint for each item — the built-in receiver (listening, protocols, tokens), any NuVotifier import, Redis network, your sites and links, the wheel, vote security, rewards, the database, and PlaceholderAPI. Most problems are diagnosed here in seconds.
Common problems
Section titled “Common problems”| Symptom | Likely cause | Fix |
|---|---|---|
| No votes at all | The receiver isn’t listening. | /daisyvotes receiver status / doctor. Set receiver.yml enabled: true, mode: Embedded, and make sure the port is free. |
testvote works, real votes don’t | The vote site can’t reach your receiver. | Verify the host, port, and token/public key on the site, and that the port is open in your firewall and forwarded to the server. |
| Votes rejected (bad token) | The site’s token/key doesn’t match receiver.yml. | Re-create it with /daisyvotes receiver token create <site> (or publickey for v1) and paste it into the site. |
| Some sites credit, one doesn’t | That site’s service name isn’t in service-aliases. | Add the exact service name the list sends to that site in menus.yml. |
| Votes rejected as “unknown service” | Strict mode + a missing alias. | Add the alias, or (less secure) set sites.require-configured-site: false. |
| Duplicate votes ignored | The duplicate window dropped a replay. | Expected. Lower or disable sites.duplicate-window-seconds if needed. |
| Wheel never gives a spin | The player hasn’t voted on required-sites distinct sites, or the count is higher than your site list. | Vote every site, or align wheel.required-sites with your configured sites. |
| Wheel resets at the wrong time | wheel.reset-zone is invalid or not your zone. | Use server or a valid IANA id like Europe/Berlin. |
| No points earned | Points are disabled. | Set points.enabled: true and a per-vote value. |
| Placeholders show blank | PlaceholderAPI isn’t installed/hooked. | Install PlaceholderAPI; doctor confirms the hook. Values also cache ~10s. |
| Shop says “can’t buy that yet” | The entry has a permission the player lacks. | Grant the permission or clear the entry’s permission. |
| Discord embeds not posting | Discord disabled or a bad webhook URL. | Set discord.enabled: true and a valid webhook-url, then /daisyvotes reload. |
| Reward command does nothing | The command targets a plugin you don’t have. | Match Command rewards to your plugins; doctor warns about likely-missing ones. |
Do I need NuVotifier?
No. DaisyVotes has its own built-in vote receiver (Votifier v1/v2). If you already run NuVotifier, DaisyVotes imports its port, tokens, and keys automatically on first start — then you can remove it (or keep it and set mode: NuVotifierBridge in receiver.yml).
Do I need an economy or crate plugin?
No. The defaults are vanilla-safe (items and messages). Add Command rewards only when you want to grant money, keys, or ranks from your own plugins.
Where do I paste my license key?
You don’t. BuiltByBit downloads embed it automatically and fill the license: section after the first start. See Installation.
Do config changes need a restart?
No — run /daisyvotes reload and DaisyVotes rebuilds its services with the new values.
Does it support Spigot or Folia? No. DaisyVotes targets Paper 1.21+ on Java 21+, and Folia is not supported.
Can players vote while offline?
Yes — rewards are queued and claimed with /vote claim on next join. See Reminders & Offline Rewards.
How do I reset all data?
Stop the server and delete the database file in plugins/DaisyVotes/. See Storage & Data — back it up first.