DaisyVotes — Customising the Vote Menu

Everything here lives in menus.yml. Vote Sites & Menus is the field-by-field reference for that file — this page is the questions people actually run into, in the order they hit them.

”I deleted my vote sites and they came back”

menus.yml is append-merged: on every start, DaisyVotes checks your file for keys it doesn’t have and adds them back with their shipped defaults and comments. It never removes or reorders anything you wrote — but that also means a key that’s missing entirely looks, to that check, exactly like a key an older version of the plugin never had. Delete every entry under sites: and the sites: key itself is gone from the file, so the next start treats it as one it forgot to add and refills it with the five example sites.

The fix is to empty the list, not delete the key:

menus.yml

vote-menu:
  sites: []

sites: [] is still a sites: key — present, and deliberately empty — so nothing restores it. This is the same rule behind every “my config reverted” surprise in DaisyVotes: an upgrade only ever adds a key that is missing outright, and an empty list, an empty string, or false all still count as present.

Caution

Do not point a real site’s Votifier config at a slot that no longer exists as a workaround for wanting it gone — the vote still needs a matching entry to land against. Remove the entry (or empty the list) and remove the listing from that site’s own panel instead.

Running with just one vote site

Keep exactly one entry under sites: and reload. Nothing else is required — you get a working candle with its cooldown display, its service-aliases matching, and any per-site reward or point override you’ve set for it, the same as any of the five shipped examples:

menus.yml

vote-menu:
  sites:
    - id: "minecraftservers"
      slot: 20
      display-name: "<gradient:#FFC8DD:#BDE0FE>Minecraft Servers</gradient>"
      url: "https://minecraftservers.org/vote/example"
      service-aliases:
        - "Minecraft Servers"
        - "minecraftservers.org"
      item:
        material: "pink_candle"

The shipped default has five sites because that’s a reasonable starting set, not a requirement — a single listing is a completely ordinary setup. The slot doesn’t need to be 20 either; any free slot on the dashboard works.

If you use the daily wheel

wheel.required-sites (in config.yml) clamps to however many sites you actually have, so a single-site server’s players earn a spin for voting on the one site they can.

See Site fields for everything an entry can carry — reward-title, reward-summary, per-site cooldown, and voted-item.

Hiding or removing a button

This is about the buttons under vote-menu.buttons — stats, wheel, top-voters, claim, party, streak, milestone, close, shop, rewards — not the site candles above, which are removed by editing the sites: list itself.

menus.yml

vote-menu:
  buttons:
    milestone:
      enabled: false

menus.yml

vote-menu:
  buttons:
    milestone:
      slot: -1

Both take the button off the dashboard, and today they do it the same way: the renderer skips a button if either enabled is false or slot is negative, and /daisyvotes doctor excludes a button from its slot-collision check under the same condition. There’s currently no behavioural difference between the two — pick whichever reads more clearly in your file. enabled: false says “I don’t want this button” outright; slot: -1 reads more like “not placed right now.”

The claim icon still shows a bundle’s contents

The claim button’s empty state (inactive-item) ships as a bundle, and a bundle draws its own “Empty” tooltip on top of whatever name and lore you give it. The shipped default already turns that off:

menus.yml (shipped default)

vote-menu:
  buttons:
    claim:
      inactive-item:
        material: "bundle"
        hide-vanilla-tooltip: true
        name: "<gradient:#FFF1C1:#CDEAC0>Claim Rewards</gradient>"
        lore:
          - "<#B8C0CC>Nothing waiting right now."

If the tooltip has come back, it’s almost always because the inactive-item block was rewritten — to change the lore, the material, or anything else — without carrying hide-vanilla-tooltip: true along with it. A field a YAML mapping doesn’t mention decodes to that field’s own default, and hide-vanilla-tooltip defaults to false, not to whatever the shipped example happened to set it to. Add the line back, or drop it entirely if you’ve changed material away from a container item (a diamond or a nether star has no contents to hide).

hide-vanilla-tooltip isn’t specific to this button — it’s a field on every item descriptor in menus.yml, and works the same way anywhere a material is a shulker box, bundle, or anything else with vanilla tooltip lines you don’t want.

Full %daisyvotes_*% placeholder reference

These are PlaceholderAPI placeholders (%…%) — for scoreboards, holograms, and tab lists. They are a different system from the <…> placeholders used inside vote-menu.buttons and site item blocks (documented on Vote Sites & Menus): the <…> ones need no other plugin and are the simpler choice inside DaisyVotes’ own menus.

A %daisyvotes_*% placeholder does work in a menu now, but you don't need it there

As of 2.8.0, DaisyVotes resolves other plugins’ %placeholders% inside its own configs — see Other plugins’ placeholders inside DaisyVotes. That means pasting %daisyvotes_total_votes% into a button’s name or lore now round-trips through PlaceholderAPI and prints a number, where it used to print nothing. It’s slower than and behaves differently from the equivalent <total_votes> in the table on Vote Sites & Menus — the %…% value comes back escaped, so use the <…> placeholder for anything already offered there.

Easy to mistype

It’s %daisyvotes_daily_votes% — daily, not “daisy”. %daisyvotes_daisy_votes% is aliased to it, so the misspelling still works.

Placeholder	Value
%daisyvotes_total_votes%	Lifetime votes
%daisyvotes_season_votes%	Votes since the last /daisyvotes season reset — never rolled on a calendar
%daisyvotes_daily_votes%	Votes today
%daisyvotes_weekly_votes%	Votes this week
%daisyvotes_monthly_votes%	Votes this month
%daisyvotes_current_streak%	Current streak
%daisyvotes_best_streak%	Best streak ever
%daisyvotes_points%	Current vote-point balance
%daisyvotes_lifetime_points%	Total points ever earned
%daisyvotes_current_votes%	Votes toward the next vote party
%daisyvotes_party_required%	Votes needed for a party
%daisyvotes_votes_remaining%	Votes left to trigger the party
%daisyvotes_party_percent%	Party progress, 0–100
%daisyvotes_top_<scope>_<n>_name%	Name of rank <n> in <scope>
%daisyvotes_top_<scope>_<n>_votes%	Vote count of rank <n> in <scope>

<scope> is daily, weekly, monthly, or alltime; <n> runs from 1 to stats.leaderboard-limit (default 10). Anything not in this list — including anything under %daisyvotes_*% that isn’t shown here — is not a real placeholder.

Placeholders The same reference with usage notes and caching behaviour.

---

Vote Sites & Menus Every field on a site and a button, and the full item descriptor.