# PlaceholderAPI Support

PixelRTPPool features an official, built-in hook into [PlaceholderAPI](https://placeholderapi.com/). You do not need to download a separate eCloud expansion; simply having PlaceholderAPI installed on your server will automatically register our placeholders.

## Available Placeholders

| Placeholder | Output | Description |
|-------------|--------|-------------|
| `%pixelrtppool_cooldown%` | Integer | Returns the remaining time (in seconds) before the player is permitted to use an RTP pool again. Returns `0` if they have no active cooldown. |
| `%pixelrtppool_countdown%` | Integer | Returns the remaining time (in seconds) on an active teleport sequence. Returns `0` if they are not currently standing in a pool. |
| `%pixelrtppool_region%` | String | Returns the name of the WorldGuard region the player is currently waiting in. Returns `None` if they are not in a pool. |

## Usage Examples

### 1. Scoreboards (e.g., TAB)
You can embed these placeholders directly into your scoreboard configuration so players know exactly when they are ready to teleport again.

```yaml
lines:
  - "&eRTP Cooldown: &f%pixelrtppool_cooldown%s"
```

### 2. ActionBars / Holograms
Use `%pixelrtppool_countdown%` on a floating hologram above your spawn pool to create a dynamic visual of the queue status!

### 3. Chat Plugins
Players with specific permissions could theoretically check their status by typing commands parsed by other placeholder-aware plugins. 

## Troubleshooting PAPI
If placeholders are not rendering (displaying literally as `%pixelrtppool_cooldown%`):
1. Ensure PlaceholderAPI is actually installed and loaded.
2. Check your server console on startup. PixelRTPPool should log `<green>✔ PlaceholderAPI Hooked`.
3. Verify that the plugin you are injecting the placeholder into (e.g., a scoreboard plugin) has PlaceholderAPI support enabled in its own configuration.

---
[🏡 Home](Home.md) | [📖 Read Next: Performance](Performance.md)