Aevum • Placeholders

##Introduction

When PlaceholderAPI is installed, Aevum registers the aevum expansion so you can display any stopwatch — and its checkpoints — anywhere placeholders work: scoreboards, tab lists, chat, holograms and more.

INFO

Placeholders resolve against the viewing player's own stopwatch. For a player-scoped stopwatch that's their personal one; for a team-scoped stopwatch it's their team's; for a global stopwatch it's the shared one. Replace <name> with your stopwatch name and <label> with a mark label.

##Stopwatch placeholders

Placeholder	Returns
`%aevum_stopwatch_<name>_time%`	Elapsed time, formatted (`MM:SS` or `HH:MM:SS`).
`%aevum_stopwatch_<name>_seconds%`	Elapsed time in whole seconds.
`%aevum_stopwatch_<name>_status%`	`running`, `paused` or `stopped`.

##Mark (checkpoint) placeholders

Swap in your mark's <label>:

Placeholder	Returns
`%aevum_stopwatch_<name>_mark_<label>%`	Formatted time recorded at the mark.
`%aevum_stopwatch_<name>_mark_<label>_seconds%`	Seconds recorded at the mark.
`%aevum_stopwatch_<name>_mark_<label>_at%`	Epoch milliseconds when the mark was recorded.

##Examples

&7Your run: &f%aevum_stopwatch_run_time% &8(%aevum_stopwatch_run_status%)
&eLap 1: &f%aevum_stopwatch_run_mark_lap1%
&7Lap 1 (seconds): &f%aevum_stopwatch_run_mark_lap1_seconds%

WARNING

If the stopwatch doesn't exist for the viewing player (or the mark isn't found), the placeholder resolves to an empty string rather than an error — handy for conditional scoreboard lines.

##Notes

The expansion identifier is aevum, and it persist()s — it keeps working for offline players where PlaceholderAPI allows.
<name> may contain underscores; Aevum parses the trailing _time / _seconds / _status (or _mark_…) suffix correctly.
Looking for timers? See Timer Placeholders.
Any placeholder you put inside Aevum's own messages.yml and action messages is also resolved through PlaceholderAPI — see config.yml.