Content generated with AI — it may contain mistakes.

Special items

Stat trackers

Trackers that count kills, blocks, arrows, damage or fish on any item: the eight bundled ones, how players apply them, exactly what each stat counts, the tracker file, and removing or resetting them.

A stat tracker is an item — the applier — that a player clicks onto a sword, pickaxe, bow or rod. From then on that item counts something, and shows it in a section added to its lore:

Kill Tracker:
 ▎ Kills » 1,284
 ▎ Last victims »
 ▎   Notch
 ▎   Steve
 ▎   Alex

Trackers work on vanilla items and special items alike, and one item can carry several.

Bundled trackers

IdCountsFits
kills_trackerPlayer kills, with the last 3 victimsSwords, axes, tridents, maces
hunter_killsPlayer kills, with the last 3 victimsBows, crossbows
mobs_killedMobs killedSwords, axes, tridents, bows, crossbows
damage_dealtDamage dealt, in heartsSwords, axes, tridents, bows, crossbows
arrows_shotArrows shotBows, crossbows
blocks_minedBlocks mined, area swings includedPickaxes, axes, shovels, hoes
farmer_planterCrops planted from the stackWheat, carrot, potato, beetroot, nether wart, pumpkin, melon and cocoa seeds
fisher_trackerCatchesFishing rods

Applying one

Get an applier

/specialsadmin give stattrack kills_tracker Steve, or the Trackers screen of /specialsadmin (a click gives you one).

Click it onto the item

Pick the applier up and click it onto the item in any inventory. One applier is used.

ResultMessage
Applied; the count starts at 0"Applied KILL TRACKER."
The item is not on the tracker's list"KILL TRACKER does not fit this item."
The item already has it"This item already carries KILL TRACKER."

Appliers cannot be placed as blocks. Clicking onto a stack, as farmer_planter does with seeds, tracks the whole stack, which then no longer stacks with plain seeds.

What each stat counts

The count always goes to the item in the hand at that moment, and only for events no other plugin cancelled.

StatCounts
KILLSA player killed by the holder: the item in the main hand when the victim dies. The victim's name is kept.
MOBS_KILLEDAny other living entity killed by the holder: the item in the main hand.
BLOCKS_MINEDBlocks broken with the item, blocks broken inside an ExyliaMines mine, and every extra block a tool feature breaks.
BLOCKS_PLACEDBlocks placed from the item. Blocks a tool places — tilling, planting, buckets — do not count.
ARROWS_SHOTShots from the bow or crossbow.
DAMAGE_DEALTMelee damage dealt with the item, and damage of arrows shot from a held bow or crossbow, rounded, at least 1 per hit.
FISH_CAUGHTEvery catch — fish, junk and treasure.
Kills go to the main hand at the moment of death

hunter_kills promises ranged kills, but a kill counts for whatever is in the main hand when the victim dies: a melee kill while holding the bow counts on the bow, an arrow kill after switching to a sword counts on the sword, and a bow in the off hand never counts. A thrown trident's damage never counts for damage_dealt; only melee trident hits do.

The tracker file

Trackers live in plugins/ExyliaSpecials/lang/<language>/trackers/, one per file, and are reloaded with /specialsadmin reload.

id: kills_tracker
stat: KILLS
applier:
  material: NETHER_STAR
  name: '{primary}&lKILL TRACKER'
  display-name: '{primary}KILL TRACKER'
  lore: [...]
  glow: true
  max-stack-size: 16
lore:
  - '{secondary}Kill Tracker:'
  - ' {letters_black}▎ {letters}Kills {letters_black}» {info}%value%'
  - ' {letters_black}▎   {highlight}%kill_1%'
whitelist: ['*_SWORD', '*_AXE', TRIDENT, MACE]
max-kills-shown: 3
KeyWhat it does
idLowercase letters, digits, ., _ and -. Defaults to the file name.
statRequired: KILLS, MOBS_KILLED, BLOCKS_MINED, BLOCKS_PLACED, ARROWS_SHOT, DAMAGE_DEALT or FISH_CAUGHT.
applierRequired: the applier item, in ExyliaLib's item format. Its display-name is how messages call the tracker.
loreThe section added to the tracked item. %value% is the count with thousands separators.
whitelistMaterials it fits; * is a wildcard. Empty fits anything.
max-kills-shownKILLS only, default 3: how many victims %kill_1%, %kill_2%... show, newest first. A missing one shows —.

A %kill_N% above max-kills-shown stays as written.

Sections stack in the order the trackers were applied, under the item's own lore. On a vanilla item the original lore is kept; removing its last tracker gives it back as it was.

Removing and resetting

Both act on the item in the player's main hand:

/specialsadmin stattrack remove kills_tracker Steve
/specialsadmin stattrack reset all Steve

remove takes the tracker off; reset sets its count to 0. all acts on every tracker on the item. Resetting a KILLS tracker clears the victims as well. Both need exyliaspecials.admin.stattrack.manage.

remove only accepts trackers that still have a file. Counts left on an item by a tracker whose file is gone are cleared with all.

Reading a count

%exyliaspecials_stattrack_<tracker>% is the count on the viewer's main-hand item, empty when it has none. See Placeholders.

Something missing on this page? Tell us on Discord