SnTempBlocks changelog

Fixes

• Placeholders now update in holograms and menus. Every %sntempblocks_*% placeholder worked under /papi parse but rendered as a raw %token% in DecentHolograms and DeluxeMenus: the expansion answered null off the main thread, which PlaceholderAPI reads as "this expansion does not handle that placeholder". Both of those refresh asynchronously, so the first frame showed the value and every refresh after it showed the token. The main thread now publishes a snapshot on the expiry sweep and the resolvers read it from any thread, so /papi parse, a hologram and a menu all show exactly the same thing. Countdowns keep the absolute wipe instant, so they stay exact between publishes.
• State words are no longer printed with raw colour codes. %sntempblocks_mode%, %sntempblocks_bypass% and the n/a of a PER_BLOCK zone reached PlaceholderAPI as &#8354f2Interval / &7n/a, because PAPI output never enters SnLib's render pass. They are rendered before they leave now.
• An INTERVAL cycle over an empty zone announces again. Neither the countdown warnings nor the wipe message were sent when the zone had nothing tracked, so the cycle appeared and disappeared depending on whether somebody had placed a block. A cycle always announces now, with a new messages.wipe-done-empty line when there was nothing to remove.

Upgrading

Drop-in. The new messages.wipe-done-empty key is merged into your language file on boot; your existing values and comments are preserved.

Changes

Staff build bypass

/tempblocks bypass switches your own tracking off while you build inside a zone, buckets included. Run it again to switch it back on.

The permission now gates the toggle instead of bypassing on its own. sntempblocks.bypass is replaced by sntempblocks.admin.bypass: holding it means you MAY flip the switch, not that your blocks stop being tracked. Previously any operator was silently unable to place a temporary block at all, which made a zone look broken while testing it.

The toggle lasts for your session and is dropped on logout, so a bypass left on by accident cannot keep filling an arena with permanent blocks. Revoking the permission also ends an active bypass at the next block placed, without waiting for a logout.

Placeholder

• %sntempblocks_bypass% renders the viewer's own state, restyleable under status.enabled / status.disabled in the language file.

Permissions

• Added sntempblocks.admin.bypass (default op, child of sntempblocks.admin).
• Removed sntempblocks.bypass. Grant the new node to anyone who had the old one.

Performance

BlockPlaceEvent now exits on an empty toggle set instead of calling hasPermission for every block placed anywhere on the server.

First stable release.

Player-placed blocks that expire inside WorldGuard zones, bucket liquids and their flow included.

Two engines, per zone

• PER_BLOCK - every block expires on its own timer, with per-material lifetimes and a default.
• INTERVAL - one timer per zone; when it fires, everything tracked there disappears at once, with configurable warnings before it.

What it guarantees

• Nothing is left behind: bucket liquids are tracked together with every block their flow reached, and spread that could not be cleaned up later is cancelled instead of allowed.
• Expiry is real time, so blocks whose lifetime elapsed while the server was down are removed at startup.
• A chunk is never force-loaded to delete a block; the removal waits for the chunk.
• A reload never clears what is already tracked.
• The whole plugin owns exactly two repeating tasks, and every removal batch is capped per tick.

Surface

• /tempblocks list | info <zone> | here | wipe <zone|all> | purge <zone>, plus SnLib's injected reload, help and debug. Aliases /tb, /stb.
• PlaceholderAPI expansion sntempblocks (the viewer's zone, or any named zone).

Requirements: Java 21+, Paper 1.20.x or 1.21.x, SnLib 1.24.0+, WorldGuard 7.0+.

Audited before release (/sn-audit FULL, gate PASSED): two criticals found, fixed and verified, both of which could turn a temporary block permanent - liquid flow overwriting the record of a block it only waterlogs, and the zone-removal policy not running at boot.