Your cart is empty
Looks like the spiders padded through here. Pick a plugin and it will show up here. Continue shoppingPhoenix Holograms supports PlaceholderAPI. Below are the placeholders the plugin registers, and the ones you can use inside a hologram.
<id> is the hologram's id.
| Placeholder | Description |
|---|---|
%phoenixholograms_count% |
How many holograms the server has, leaving out those other plugins make through the API. |
%phoenixholograms_page_<id>% |
The page the player sees on that hologram, from 1. 0 when the hologram does not exist or the player is offline. |
%phoenixholograms_pages_<id>% |
How many pages that hologram has. |
Available in text lines, hover texts, head lines, leaderboard formats, and the input and value of a line condition.
| Placeholders | Description |
|---|---|
| %player% | The name of the player looking at it. |
| %page% | The page the player sees, from 1. |
| %pages% | How many pages the hologram has. |
| %hologram% | The hologram's id. |
Every PlaceholderAPI placeholder works too, filled in for each player on their own. They refresh every Update Interval.
Tokens in curly brackets are filled in before the placeholders, so an animation frame can hold a placeholder. See Animations.
| Token | Shows |
|---|---|
{anim:<name>} |
The current frame of an animation. |
{countdown:<date>} |
The time left until a date. |
{date:<pattern>} |
The current date or time. |
{lang:<key>} |
A text in the player's own game language. See Per-Player Language. |
{online:<server>,<server>} |
Players online on those servers, added up. |
{max:<server>,<server>} |
Their player slots, added up. |
{motd:<server>} |
The server's MOTD on one line. |
{status:<server>} |
Online or Offline, worded in the translation file. |
The server tokens need no PlaceholderAPI or proxy plugin. The plugin pings each server in the Servers list itself, so any server reachable from this one works, behind a proxy or not. A server that does not answer counts as offline with 0 players. A server name missing from the list leaves the token as typed.
{lang:<key>} is filled from the texts section of the translation files, one file per language such as translations.en.yml or translations.de.yml. Keys can be nested, as rules.title. Each player gets the file matching their game language, so a German client reads translations.de.yml, then the plugin's own language, then English. A key found nowhere is left as typed. Texts may hold placeholders and tokens. Run /pholo reload after editing the files.
en:
texts:
welcome: "&eWelcome to the server!"
rules:
title: "&6&lRules"
Every PlaceholderAPI placeholder works in [MESSAGE], [COMMAND], [ACTION_BAR] and [TITLE] actions. %player% works in [COMMAND] even without PlaceholderAPI.
Your guide to the docs
Ask me anything about our plugins. I know these docs inside out, check the latest versions and changelogs, and can read your server logs.
Try asking
Your cart is empty
Looks like the spiders padded through here. Pick a plugin and it will show up here. Continue shopping