Combat

Kill rewards

Every kill can pay, and consecutive kills build a streak. Both are written in modules/kill-rewards/rewards.yml.

on-kill:
  money: 3
  commands: []
  killer:   { chat: "", actionbar: "", title: "", sound: "" }
  victim:   { chat: "", actionbar: "", title: "", sound: "" }
  server-broadcast: ""
streak-milestones:
  '3':  { … }
  '5':  { … }
  '10': { … }
streak-end:
  min-streak: 3
  commands: []
  killer: { … }
  victim: { … }
  server-broadcast: ""

%killer%, %victim%, %streak% and %victim_streak% are available throughout. Commands take a console: or player: prefix.

money pays the killer in the default currency, multiplied by money boosters for kill-rewards (see Economy), and %money% is what was paid, after boosters. It works in on-kill, in every streak milestone and in streak-end. The shipped on-kill pays 3 this way, where it used to run eco give %killer% 50.

settings.worlds is a whitelist — empty means every world. settings.streak-reset-on-logout decides whether a streak survives a disconnect.

/killrewardsadmin reset <player> and /killrewardsadmin resetbest <player> (alias /kra, node exyliasurvivalcore.killrewards.admin) clear a player's current or best streak, whether they are online or not. Both streaks live in memory, so a restart clears them as well. The stats module's best_kill_streak is a separate, stored value and is not touched.

Bounties

/bounty place <player> <amount> puts money on a head. Whoever kills that player collects it. Several players can contribute to the same head, and /bounty lists the open ones with their contributions.

Administrators get /bountyadmin add, remove and clear.

Another plugin can refuse a claim through BountyClaimEvent, which is asked before any money moves: a refused claim leaves every bounty on the victim for the next kill. See API.

Statistics

Two kinds of number reach the stats screen. The stats module keeps four PvP values of its own — kills, deaths, best streak and current streak — and every module keeps counters of what its players do: blocks mined, crates opened, warps taken. modules/stats/stats.yml decides which of them are shown and ranked.

The shipped file is deliberately short — the stats players compete on:

stats:
  kills:              { type: INTERNAL, format: NUMBER,  leaderboard: true, … }
  deaths:             { type: INTERNAL, format: NUMBER,  leaderboard: true, … }
  kdr:                { type: COMPUTED, format: DECIMAL, formula: KILLS_PER_DEATH }
  best_kill_streak:   { type: INTERNAL, format: NUMBER,  leaderboard: true, … }
  current_streak:     { type: INTERNAL, format: NUMBER,  leaderboard: false, … }
  duels_won:          { type: COUNTER,  counter: 'duels.wins',         format: NUMBER }
  balance:            { type: VAULT,    format: MONEY }
  bounties_claimed:   { type: COUNTER,  counter: 'bounties.claimed',   format: NUMBER }
  bounties_earned:    { type: COUNTER,  counter: 'bounties.earned',    format: MONEY }
  votes_total:        { type: COUNTER,  counter: 'votes.total',        format: NUMBER }
  votes_best_streak:  { type: COUNTER,  counter: 'votes.best_streak',  format: NUMBER }
  market_sold:        { type: COUNTER,  counter: 'market.sold',        format: NUMBER }
  market_earned:      { type: COUNTER,  counter: 'market.earned',      format: MONEY }
  blocks_mined:       { type: COUNTER,  counter: 'mines.blocks',       format: NUMBER }
  farming_harvested:  { type: COUNTER,  counter: 'farming.harvested',  format: NUMBER }
  crates_opened:      { type: COUNTER,  counter: 'crates.opened',      format: NUMBER }
  missions_completed: { type: COUNTER,  counter: 'missions.completed', format: NUMBER }
  mobs_killed:        { type: COUNTER,  counter: 'kills.mobs',         format: NUMBER }
  playtime:           { type: PAPI,     format: TIME, placeholder: "%exyliasurvivalcore_playtime_millis%" }

Every entry ships enabled: true, and every one except current_streak is ranked.

format is NUMBER, DECIMAL, MONEY or TIME. leaderboard: false keeps a stat off the boards while still showing it on the profile.

A reload reschedules all three timers with the new values.

Counters

A counter exists the moment a module counts it; nothing has to be declared. %exyliasurvivalcore_stats_counter_<key>% reads any counter by its key, as a plain number, whether or not stats.yml lists it — %exyliasurvivalcore_stats_counter_mines.blocks%, for instance. A COUNTER block is only what puts it on the stats screen and gives it a leaderboard. Missions and seasons read the same counters: see Missions and seasons.

Keys are lower-cased, and one longer than 100 characters is ignored rather than cut short. Money counters — .earned, .spent — add whole units. votes.best_streak is a best, not a sum: it keeps the highest streak seen. The list in the shipped stats.yml header covers most of these but not all; this table follows the code.

Counting happens in memory. Changed counters are written every counter-flush-interval seconds, when a player leaves and on shutdown, so a crash can lose at most that interval. While the stats module is off nothing is counted, and what would have been is not kept for later.

Death

The death module is three settings.

The death broadcast is one of the seven that respect a player's /settings preferences.

When the graves module makes a grave, the drops go into it first and the death module finds nothing left to scatter.

Graves

A player who dies leaves a grave where they fell: a player head with their face on it, floating text with a countdown, and everything they dropped inside. One click on the head — left or right, main hand — collects all of it. There is no window onto a grave.

The module is on by default. Its settings are in modules/graves/config.yml.

%protection% reads "Anybody can open it", "Only the owner can open it", or "Protected » " followed by the time left; the three lines are hologram-open, hologram-protected and hologram-protected-for in the graves section of messages.yml. The countdowns tick every second, and expired graves are swept on the same timer.

When a grave is made

• Not when the world keeps inventories, not in a blacklisted world, and not when there is nothing to keep — no items and no experience.
• The head goes in the block the player died in when it is air, water, lava, grass, fern, snow or seagrass; otherwise the first such block up to six above. With no room at all there is no grave and the drops fall as they would have.
• The block the head replaced is put back when the grave goes.
• If the grave cannot be stored, its items and experience drop on the spot instead.

A grave cannot be broken, and explosions and pistons leave it alone.

Collecting

The owner can always open their grave. During protection, so can the killer when killer-can-loot is on; anybody else is told whose grave it is and how long until it opens. Once protection is over, anyone can take it — the owner's message says "Grave collected", anyone else's says they looted it.

Items go into the collector's inventory. What does not fit is kept in ExyliaLib's pending-reward table and handed over the next time they join. The experience is given with the items.

Two players clicking the same grave in the same tick, or a grave expiring while it is being opened, get exactly one winner: taking a grave is deleting its row, and only whoever removed it gets the items.

/graves

/graves (alias /grave, node exyliasurvivalcore.graves) lists a player's own graves in modules/graves/menus/graves.yml: where each one is, what is inside, how long ago they died, how long it has left and who may open it. A player with none is told so and no menu opens. With allow-teleport on, clicking a grave charges teleport-cost and takes them to it; with a cost above 0 and no economy available, the teleport is refused. The menu can also be opened with the survivalcore:graves_open action.

When several servers share one database, a grave is loaded only on the server it was made on.