v1.14.0 (2023-07-17)
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 (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:
unwax_sign
–/sign unwax
pending action descriptionwax_sign
–/sign wax
pending action descriptionwax_removed
– Completed/sign unwax
actionwax_applied
– Completed/sign wax
actionbypass_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.
Fixed
-
Failure and error when editing hanging signs and wall hanging signs from Minecraft 1.20 when using
compatibility.edit-validation: Extra
(#34) -
Workaround for a Spigot 1.20 bug where using the stable API to have a player open a sign does not make the sign editable (SPIGOT-7391)
-
Error
java.lang.IllegalArgumentException: Invalid page number (1)
when usingcompatibility.sign-ui: EditableBook
and saving a blank book
Under the Hood
- Tacked on some adapters to make the plugin compatible with Bukkit 1.20
org.bukkit.block.sign.SignSide
- Increased the right-click event handling priority to the highest level to avoid interfering with other plugins that take over right-click events on signs (#36)
- Permission processing moved from
SignCommand.permitted(Player, String)
toInteractionCommand.isPermitted()
SignText.signChanged()
renamed toSignText.signTextChanged()
as part of clarification that only text changes count in/sign undo
and/sign redo
- Started pulling
org.bukkit.entity.Player
out of constructor injections, as various classes are being used in wider scopes. - Gradle 9.0 compatibility:
- Replaced Gradle 8.2 deprecations with recommended replacements
- Updated Gradle to version 8.2.1
- Added JDK toolchain resolver plugin to download Java 1.8
- Skip ProGuard for development builds
- Eliminated the dependency on
commons-lang:commons-lang