Rewards and votes

Rewards

A reward is a database row built entirely from /rewardsadmin: some items, some commands, a type that says how often it may be taken, and an optional permission. There is no rewards file. /rewards opens the list, and a player takes a reward from there.

It differs from a kit in its type: a reward can reset on the calendar and keep a streak for a player who comes back.

Types

Daily, weekly and monthly are worked out from the clock, not scheduled: a player who logs in after a week away is simply in a new period, and a server that was off over a reset needs no catch-up. Max claims still applies to every type but Once, as a lifetime total per player; -1 is unlimited.

Streaks

Every claim writes a streak:

• Daily, weekly, monthly — the streak goes up when the last claim was in the period just before this one, and starts again at 1 otherwise.
• Interval — it goes up when the last claim was within two intervals. On a 24-hour interval, missing a day breaks it.
• Once — always 1.

The list and the preview show the streak the last claim wrote. A broken streak keeps showing its old number until the next claim resets it to 1.

Claiming

A claim is checked in this order: switched off, missing the reward's permission, used up, still waiting. Only a reward that passes all four is handed over.

• Items go through the plugin's delivery: what does not fit is kept and handed over on the player's next join, never dropped.
• Commands run from the console unless a line starts with player:, console:, player-proxy: or console-proxy:. %player% and %player_name% are both filled in.
• The claim counts towards the rewards.claimed stat counter.

exyliasurvivalcore.rewards.bypass ignores the wait and the claim limit. It never skips the reward's own permission or a disabled reward.

The player screens

modules/rewards/menus/list.yml draws each reward in one of four templates — item_template (ready), cooldown_template, used_template and locked_template — so what a locked reward looks like, and whether it can be clicked, is decided in the file. Left-click claims, right-click previews.

modules/rewards/menus/preview.yml shows the items as themselves, the claim button in slot 8 drawn by the same states plus disabled_template, and a Bonuses item listing the reward's named commands. It names three and adds labels.more for the rest; a command without a name is never shown. A reward with no items and no commands does not open a preview at all.

Both files are yours to edit. The buttons are survivalcore:reward_open_list, survivalcore:reward_claim <id> and survivalcore:reward_preview <id>; none of them checks exyliasurvivalcore.rewards, so a reward button bound elsewhere works for anyone.

Building a reward

/rewardsadmin opens menus/admin/rewards_admin_list.yml: every reward, enabled or not, with Create reward. Left-click edits, right-click deletes after a confirmation. The edit screen, menus/admin/reward_admin_edit.yml, has one button per field:

Clone copies everything into a new id and Preview opens the player's preview. Both admin files are regenerated from the jar on every start and every reload; edit the two player files instead.

Commands

Every one of them is player-only. reset and resetall take offline players.

Settings

modules/rewards/config.yml:

labels.ready, unlimited, none, more, once, interval (with %time%), daily, weekly and monthly are the words the screens fill in for a wait that is over, an unlimited count, an empty field and the type.

Placeholders

A reward id with underscores is read whole.

The cooldown placeholder writes Ready itself; labels.ready does not reach it.

Votes

Votes arrive through NuVotifier or the original Votifier, found by either plugin name the tick after the server enables. Without either, the log says so and votes only arrive through /voteadmin fake.

modules/votes/votes.yml holds the sites, what a vote pays, the streak rewards and the vote party's rewards. It is yours to edit; keys a later version adds appear on their own, and /sc reload re-reads it.

What a vote goes through

1. Stored. The vote is saved under an id worked out from the site, the name and the site's timestamp, so the same vote forwarded to several servers lands on one row. A name that is not 1–32 letters, digits, _, . or * is dropped silently.
2. Announced. Every server tells its own players once, to those with vote-announcements on in /settings.
3. Paid, once. The server the player is on takes the row, and only one server can. A player who is offline is paid the next time they join any server, however many votes are waiting, oldest first.
4. Counted for the party. A second table keeps the vote for the party, offline players included.

The announcement and the instant payment travel on ExyliaLib's votes channel. On one server that needs nothing. On a network it needs Redis and a shared database: without Redis a server only hears the votes it received, and a vote for a player on another server waits for their next join.

Each payment counts the votes.total counter, a votes.<site> counter (the site name lower-cased, anything that is not a letter, digit or _ turned into _) and the votes.best_streak personal best.

votes.yml

sites:
  minecraft-mp:
    name: '{primary}&lMINECRAFT-MP'
    url: 'https://minecraft-mp.com/server/000000/vote/'
    icon: PAPER
 
vote:
  money: 30
  rewards: []
  message: '… Thanks for voting on %service%! +%money% · Streak » %streak%'
 
streaks:
  '3':  { money: 60,  rewards: [], message: '…' }
  '7':  { money: 150, rewards: [], message: '…' }
  '30': { money: 750, rewards: [], message: '…' }
 
party:
  money: 20
  rewards: []
  message: '… Vote party reward » +%money%'
  commands:
    - 'boostersadmin global money 1.5 30m'

Every paying block takes the same three keys:

• money — paid in the default currency and multiplied by money boosters for votes (see Economy). Needs an economy; without one it pays nothing.
• rewards — an Exylia reward list.
• message — sent once the block is paid; empty for none. %player% and %money% everywhere, and %service%, %streak% and %total% in vote and streaks.

The sites replace the placeholder URLs you ship with. Clicking one in /vote closes the menu and sends the link to chat.

Streaks

A day is a calendar day in settings.timezone, from midnight: votes have no reset hour. A vote the day after the last one extends the streak, a second vote the same day leaves it alone, and a day without a vote starts it over. %exyliasurvivalcore_votes_streak% already reads 0 once a whole day has passed with no vote.

The vote party

Every vote, from any server, counts towards one network-wide party. After each vote, every server shows its players a boss bar with the count for party.bossbar-seconds. When the count reaches party.target, the first server to take the party's token starts it: everyone online everywhere is paid the party block, party.commands run once, the count starts again from zero, and players with vote-announcements on are told.

party.target: 0 turns counting towards a party off. /voteadmin party still starts one.

Reminders

A player who has not voted today is reminded three seconds after joining, when remind-on-join is on, and every reminder-minutes while online.

Settings

modules/votes/config.yml:

Commands

Both admin subcommands run from the console. The screen is modules/votes/menus/vote.yml; its buttons are survivalcore:votes_open and survivalcore:votes_link <site>.

Placeholders

A player's own numbers read 0 until their row has loaded on join.

Reward lists

votes.yml's rewards and seasons.yml's prizes are ExyliaLib reward lists. A bare string is a console command; a map names its type.

rewards:
  - 'eco give %player_name% 500'
  - type: ECONOMY
    value: '750'
  - type: ITEM
    itemSnapshot: DIAMOND
    itemAmount: 4
    chance: 25.0

Any of them also takes chance, permission, and minAmount with maxAmount for a range. An entry with an unknown type is reported in the log and skipped; the rest of the list is still given.