v1.14.0-beta7 (2023-07-16) :: Fixed all remaining known Spigot 1.20 compatibility issues
Pre-Release Notes Since Previous Pre-Release
Added a workaround for a Spigot 1.20 bug where having a player open a sign does not make the sign editable (SPIGOT-7391)
Preserve the native honeycomb-on-sign action if the signedit.sign.wax permission is denied.
Locale changes:
wax_removed and wax_applied should just be those and not excessively wordy in what their effects are.
Eliminated bypass_wax_before and bypass_wax_after to prefer only error messages, as users probably don't care if the implicit de/re-waxing is successful.
Reworded bypass_wax_cannot_rewax to make it clear that the wax that was previously on the sign was discarded.
Known Issues
The new locale strings relating to waxed signs have not been proofread for the locales zh-CN, zh-TW, and zh-HK.
Added
Support for Minecraft 1.20 sign sides (front and back)
Support for Minecraft 1.20 honeycomb wax on signs
On Minecraft 1.20+, opening an editable sign (sign without honeycomb wax) by right-click will open a sign editor handled by this plugin.
(Minecraft 1.20+ only) /sign wax and /sign unwax commands and permissions to apply and remove honeycomb wax from signs, respectively
New locale strings:
wax_removed – Completed /sign unwax action
wax_applied – Completed /sign wax action
bypass_wax_cannot_rewax – Warning after a /sign text change that wax was not reapplied because the player lacks permission to /sign wax
forbidden_waxed_sign_edit – Error that a /sign text change was blocked because the target sign is waxed and the player lacks permission to /sign unwax
Changed
The documentation of /sign undo and /sign redo has been clarified to indicate that they affect only the sign text, not the dyes or wax applied to the sign.