Every ExyliaSurvivalCore placeholder, group by group, written in the PlaceholderAPI form for scoreboards, holograms and chat.
Page 18 of 383 min read
Every placeholder below is written in full, and clicking one copies it. They need PlaceholderAPI, then work in any plugin that reads it: scoreboards, holograms, tab lists and chat.
The prefix is exyliasurvivalcore, so a home count is %exyliasurvivalcore_homes_count%. The shorter survivalcore prefix is gone: %survivalcore_homes_count% no longer resolves.
A disabled module registers no placeholders
A module turned off in config.yml registers nothing, so its placeholders stay on screen exactly as you wrote them. Turn the module on and reload to bring them back.
Durations are written in full, such as 1h 5m 3s, unless a row says they are short. Words such as Ready, Now and — are the module's own wording and follow the server language. Placeholders of the plugins that took modules over (economy, market, rewards, combat, protections, crates, mines) are on those plugins' pages.
The player at that place on the leaderboard of a stat, or a dash when nobody holds it. The position comes first: `%exyliasurvivalcore_stats_top_name_1_kills%`.
Their value, formatted. The position comes first: `%exyliasurvivalcore_stats_top_value_1_kills%`.
128
<stat> is a key from modules/stats/stats.yml. The shipped keys are kills, deaths, kdr, best_kill_streak, current_streak, duels_won, balance, bounties_claimed, bounties_earned, votes_total, votes_best_streak, market_sold, market_earned, blocks_mined, farming_harvested, crates_opened, missions_completed, mobs_killed and playtime. Several are filled by counters that other plugins keep; a stat nobody counts shows 0.
<key> in stats_counter_ is a counter key such as crates.opened. It does not have to be declared in stats.yml: a counter exists as soon as something counts it.
Stat ids are not the streak placeholder names
%exyliasurvivalcore_stats_streak% and %exyliasurvivalcore_stats_best_streak% read the counters directly and work. They are not stat ids: inside stats_value_, stats_rank_ and stats_top_* the ids are current_streak and best_kill_streak. So %exyliasurvivalcore_stats_value_streak% answers the unknown word and %exyliasurvivalcore_stats_value_current_streak% works. current_streak ships with leaderboard: false, so its top rows answer with a dash by design.
The position comes first in the leaderboard placeholders, because a stat id may contain underscores and a position may not:
Whether scheduled command announcements reach them
—
%exyliasurvivalcore_settings_tpa_requests%
Whether teleport requests reach them
—
%exyliasurvivalcore_settings_tpa_auto_accept%
Whether a request is accepted without asking
—
%exyliasurvivalcore_settings_tpa_confirm%
Whether sending a request asks for a confirmation
—
%exyliasurvivalcore_settings_protection_messages%
Protection messages; only applies when ExyliaProtections is installed
—
%exyliasurvivalcore_settings_raid_announcements%
Raid announcements; only applies when ExyliaProtections is installed
—
One name per preference, each answering true or false. Every setting is on until the player turns it off. The names are the setting ids with dashes turned into underscores. The three tpa_ ones read straight through to the TPA module, so a player never has two answers to one question.
The reader's money multiplier, their own boosters and the global ones together — `1`, `1.5`, `2.25`
1.5
%exyliasurvivalcore_boosters_xp%
The same for experience
1
%exyliasurvivalcore_boosters_drops%
The same for drops
—
%exyliasurvivalcore_boosters_active%
The reader's boosters running right now
1
%exyliasurvivalcore_boosters_stored%
The reader's boosters kept but not started yet
2
%exyliasurvivalcore_boosters_global_money%
The money multiplier of the global boosters alone
—
%exyliasurvivalcore_boosters_global_xp%
The same for experience
—
%exyliasurvivalcore_boosters_global_drops%
The same for drops
—
%exyliasurvivalcore_boosters_global_left%
Time left on the first running global booster, or `—`
1h 5m 3s
The global_ ones ask for no viewer. Every running booster of that type counts, and they combine by the module's stacking rule, capped at its maximum multiplier.