Placeholders - SnTempBlocks Docs

All placeholders require PlaceholderAPI and use the %sntempblocks_ prefix.

There are two families. The plain ones answer about the zone the viewer is standing in right now, which is what a scoreboard or an action bar wants. The ones ending in a zone id name a zone explicitly, which is what a hologram at the arena entrance wants. One placeholder, %sntempblocks_bypass%, is about the viewer rather than any zone.

The viewer's own zone

Placeholder	Description
`%sntempblocks_zone%`	Id of the zone the viewer is standing in
`%sntempblocks_mode%`	Its engine, as a word: `Per block` or `Interval`
`%sntempblocks_tracked%`	Blocks currently tracked in that zone
`%sntempblocks_next_wipe%`	Time left until that zone's next wipe, formatted
`%sntempblocks_next_wipe_seconds%`	The same, as a bare number of seconds

A named zone

Placeholder	Description
`%sntempblocks_tracked_<zone>%`	Blocks currently tracked in that zone
`%sntempblocks_next_wipe_<zone>%`	Time left until that zone's next wipe, formatted
`%sntempblocks_next_wipe_seconds_<zone>%`	The same, as a bare number of seconds

Replace <zone> with the zone id, which is the key you wrote under zones: in zones.yml. For a zone called pvp-arena that is %sntempblocks_next_wipe_pvp-arena%.

The viewer's own bypass

Placeholder	Description
`%sntempblocks_bypass%`	`Enabled` or `Disabled`, the viewer's own `/tempblocks bypass` state

This one answers everywhere, not only inside a zone, which makes it useful on a staff scoreboard or action bar as a reminder that the switch is still on. An offline viewer reads as Disabled, which is the literal truth: the toggle is session state and logging out drops it.

What they return when there is no answer

Nothing here invents a number.

Situation	Output
The viewer is standing in no zone	`None`, except `%sntempblocks_tracked%`, which returns `0`
The zone id names no loaded zone	`Unknown`
The zone runs on `PER_BLOCK`	`n/a` for both next-wipe placeholders

%sntempblocks_tracked% is the one exception because it is consumed as a number: a scoreboard line, a comparison, a menu that sorts on it. A word there would break every one of those.

A PER_BLOCK zone has no single next-wipe instant, because every block carries its own deadline. Returning n/a is why a countdown never ticks down to a wipe that will not happen.

next_wipe_seconds returns n/a rather than a number on a PER_BLOCK zone or an unknown zone. If another plugin does arithmetic on that value, make sure it tolerates a non-numeric result.

Every one of these words, Enabled and Disabled included, is a language value under status: in your messages file, so you can restyle or translate them once and every command and placeholder follows. Their colours are rendered before the value leaves, so a hologram shows Interval, not the raw &#8354f2Interval.

Holograms, menus and scoreboards

Every placeholder on this page answers from any thread, so it works in plugins that refresh their text asynchronously. DecentHolograms, DeluxeMenus with an update-interval, and the common scoreboard plugins all do exactly that.

The values behind them are republished on the plugin's expiry sweep, whose cadence is limits.check-interval-ticks in config.yml (10 ticks, half a second, by default). Two things follow from that:

Countdowns are always exact. next_wipe and next_wipe_seconds are computed against the clock at the moment they are read, not at the moment they were published, so they tick down correctly no matter how often your hologram refreshes.
Counts and the viewer's zone can be up to one sweep behind. Walking into a zone updates %sntempblocks_zone% within half a second, and a block placed right now is counted by %sntempblocks_tracked% within the same half second. Lowering check-interval-ticks tightens both, at the usual CPU cost.

Versions before 1.1.1 answered only on the main thread, which PlaceholderAPI reads as "this expansion does not handle that placeholder". On those versions a hologram showed the value on its first frame and the literal %sntempblocks_next_wipe_arena% on every refresh after it, while /papi parse kept working. If you are seeing that, update.