v1.14.0-beta3 (2023-07-07) :: Initial support for honeycomb wax on signs
Pre-Release Notes Since Previous Pre-Release
Initial support for waxed signs
SignEdit for Bukkit now takes over the native Minecraft sign editor for unwaxed signs in Minecraft 1.20+.
Fixed sending side data when firing SignChangeEvent in the validation phase
Known Issues
/sign undo and /sign redo treat waxed signs as unwaxed signs.
When using the Spigot server, /sign ui edits might not be registered. This might be due to a bug in Spigot's SignChangeEvent handling. Either switch to PaperMC or use /sign set as a workaround.
When using /sign ui and any existing line begins with a formatting code and there are no other formatting codes on the line, SignEdit for Bukkit may incorrectly say "Sign edit forbidden by policy or other plugin" or "Modified by another plugin". This might be a compatibility issue with PaperMC's mapping of text components to formatting codes.
Added
Support for Minecraft 1.20 sign sides (front and back)
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_before – Warning before a /sign text change that wax will be removed
bypass_wax_after – Warning after a /sign text change that wax was reapplied
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 when attempting to edit a waxed sign without permission to run /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.