Welcome to the Hangar Open Beta. Please report any issue you encounter on GitHub!
1.4.3 - 2026-05-05
Added
- Chamber pause state. Registered chambers can now be paused via
/tcp pause <name>or the new toggle in the Chamber Detail GUI. Pausing preserves the full DB record — no history, stats, or vault data is lost — but suspends all active behavior: automatic resets stop scheduling, protection events skip the chamber, vault interactions are blocked with achamber-is-pausedmessage, and player/mob tracking is silenced. Resume at any time with/tcp resume <name>or the GUI toggle. - Auto-pause on destruction. New
protection.auto-pause-on-destruction: falseopt-in (disabled by default). When enabled, a MONITOR-priority break observer counts vault and trial spawner destructions inside a chamber; once the count reachesprotection.auto-pause-threshold(default6), the chamber auto-pauses and ops withtcp.discovery.notifypermission are notified. Counter resets on every pause/resume transition and on chamber reset, so a resumed chamber always starts fresh. - New permission
tcp.admin.pause(default op) — required to use/tcp pauseand/tcp resume.
Config additions
protection.auto-pause-on-destruction(defaultfalse) — master switch for the automatic pause on critical-block destruction.protection.auto-pause-threshold(default6) — how many combined vault + trial spawner destructions inside a chamber trigger the auto-pause. Minimum effective value is1. A low value (1-2) catches individual mischief; the default (6) targets systematic demolition. Resets on every pause/resume cycle and on chamber reset.
Localization
- New flat keys:
chamber-paused,chamber-resumed,chamber-already-paused,chamber-not-paused,chamber-is-paused,chamber-auto-paused(with{chamber},{block},{count}placeholders),info-paused,help-pause,help-resume,usage-pause,usage-resume. - New GUI keys under
gui.chamber-detail:pause-toggle-name,pause-toggle-lore-active,pause-toggle-lore-paused.
Information
| Published on | May 6, 2026 |
|---|---|
| Downloads | 0 |
Platforms
Paper (1.21.1-26.1.2)