vote-party
Server-wide vote party — global counter, rewards, network sharing.
A vote party is a server-wide reward triggered when a global vote counter crosses a threshold. Every vote from every player counts toward the same number, and when it reaches the goal, the configured reward pool fires for every online player at once.
The party progress GUI — global counter, percentage, and contributors.
Quick example
vote-party:
enabled: true
threshold: 100
broadcast: "<#FF9D5E>VOTE PARTY! <white>The server hit 100 votes — everyone gets a prize!</>"
rewards:
- type: command
value: "give %player% diamond 5"
- type: money
amount: 2500
- type: message
value: "<#FFD700>You earned a vote-party reward!</>"
- type: firework
power: 2
effects:
- type: BALL_LARGE
colors: ["#4DA6E8", "#FFD700", "#FF9D5E"]
flicker: true
trail: trueWhen the global counter hits 100, the broadcast fires, every online player runs through the rewards pool, and the counter is reset to 0 to start counting toward the next party.
Reference
| Key | Type | Default | Notes |
|---|---|---|---|
enabled | boolean | true | Master switch. |
threshold | int | 100 | Number of votes required to trigger a party. |
broadcast | string | MiniMessage line sent to every online player when the party fires. | |
rewards | list | Reward pool — same shape as vote-rewards.yml. | |
reset-on-restart | boolean | false | If true, the global counter is wiped on every plugin start. Almost never what you want. |
Picking a threshold
The right number depends entirely on your server's average daily vote count. A good rule of thumb:
| Average daily votes | Suggested threshold | Roughly fires every… |
|---|---|---|
| 20 | 50 | ~2.5 days |
| 50 | 150 | ~3 days |
| 100 | 250 | ~2.5 days |
| 250 | 500 | ~2 days |
| 500 | 1000 | ~2 days |
Aim for a party every 2–4 days. Less than that and parties feel constant and lose their punch; more than that and players never actually get to experience one.
Network-shared parties
If you have mysql.server-id set across multiple servers, the
vote-party counter is intentionally still shared. A vote on
Survival contributes to the same counter as a vote on Skyblock, and
when the threshold fires, every online player on every backend
gets the reward.
This is what makes vote parties feel like a community event across a network instead of a per-server stat. If you'd rather each backend have its own party, run separate databases — there's no per-server party config.
The counter is persisted to the database after every increment, so
it survives restarts and crashes. The only way to lose progress is
to set reset-on-restart: true (don't) or to manually run
/voteplus party reset.