VGRAVES
Placeholders
VGraves includes a PlaceholderAPI expansion for server-side placeholders. These placeholders expose grave counts, ticket data, and usage limits so you can reuse VGraves values in scoreboards, chat, menus, holograms, and other plugins.
Available PlaceholderAPI Placeholders
| Placeholder | What it returns |
|---|---|
%vgraves_maxgraves% | The configured maximum grave count from settings.max_saves. |
%vgraves_mygraves% | The player's current saved grave count from the grave manager. |
%vgraves_tickets% | The player's current ticket amount. |
%vgraves_ticket_limit_used% | How many ticket-based reclaims the player has already used. |
%vgraves_purchase_limit_used% | How many paid/currency reclaims the player has already used. |
%vgraves_ticket_limit_max% | The configured maximum ticket reclaim usage, or the language-defined infinite string if unlimited. |
%vgraves_purchase_limit_max% | The configured maximum paid reclaim usage, or the language-defined infinite string if unlimited. |
Special Behavior
- If
limitation.maximum_ticket_usageis below0,%vgraves_ticket_limit_max%does not return a number. It first tries the language keyinfinite-use, and falls back toâžif that key is missing. - If
limitation.maximum_buy_usageis below0,%vgraves_purchase_limit_max%behaves the same way. - Unknown placeholder names return an empty string.
limitation:
maximum_buy_usage: -1
maximum_ticket_usage: -1With this setup, the two *_limit_max placeholders will usually render the language message for unlimited use instead of a numeric value.
Practical Examples
Scoreboard line
Show how many tickets a player currently owns.
&bTickets: &f%vgraves_tickets%Usage overview
Display current usage against the configured maximum.
&ePaid claims: &f%vgraves_purchase_limit_used%&7/&f%vgraves_purchase_limit_max%
&eTicket claims: &f%vgraves_ticket_limit_used%&7/&f%vgraves_ticket_limit_max%Menu or hologram text
Show the current grave count next to the configured cap.
&6Your graves: &f%vgraves_mygraves%&7/&f%vgraves_maxgraves%Important Notes
The code comment above the expansion mentions values like {id}, {created}, {expires}, {xp}, {death-location}, {price}, and {currency}. Those are not implemented in this PlaceholderAPI expansion method.
Based on the current code, the real PlaceholderAPI expansion only exposes the seven %vgraves_...% placeholders listed on this page. The commented brace-style tokens appear to belong to other runtime text replacement logic, not this expansion class.