Content generated with AI — it may contain mistakes.

Reference

Placeholders

Every placeholder the plugin answers, in the PlaceholderAPI form and the short form Exylia files read, and what each returns.

How the name is written

The placeholders are registered through ExyliaLib as one group, playervaults. PlaceholderAPI reaches them by putting the plugin in front, so a scoreboard, a hologram or a tab plugin asks for:

%exyliaplayervaults_playervaults_unlocked%

That is the form this page documents. Inside an Exylia plugin's own files — menus, messages, another Exylia plugin's scoreboard — the registered name also stands on its own: %playervaults_unlocked%.

No expansion needs downloading. Without PlaceholderAPI installed only the Exylia form works.

Placeholders

PlaceholderReturns
%exyliaplayervaults_playervaults_unlocked%How many vaults the viewer may open: their rank's plus the ones they bought, under max-amount.
%exyliaplayervaults_playervaults_max%vaults.max-amount, the most anybody may have.
%exyliaplayervaults_playervaults_bought%How many vaults the viewer bought.
%exyliaplayervaults_playervaults_rows%How many rows each of the viewer's vaults has, 1 to 6.
%exyliaplayervaults_playervaults_next_price%What the next vault costs, formatted in the purchase currency: $7,500.00. Empty when purchases are off or the viewer cannot buy another.

Every one but max is about the player reading it, so it needs a viewer. They all read memory and never ask the database on the thread that renders them. The bought count is read when a player joins, so for a moment after joining bought reads 0.

Inside the plugin's own screens

The vault list and the history screen have values of their own, such as %vault_used% or %snapshot_when%. They are listed on Configuration.

Something missing on this page? Tell us on Discord