Tags
Creators
Details
1.14.0-beta6
Compatibility
Changes
Pre-Release Notes
Since Previous Pre-Release
- When using
compatibility.edit-validation: Extra, SignEdit for Bukkit could have submitted anullrather than an air block for the block next to floating wall hanging signs, causing other plugins to fail to handle theBlockPlaceEvent. Although not possible in normal Minecraft, SignEdit for Bukkit now simulates hanging wall hanging signs in the air for validation purposes. - Hopefully improved the machine translations of the wax-related locale strings
Known Issues
- When using the Spigot server,
/sign uiedits are not registered due to a bug (SPIGOT-7391). Either switch to PaperMC or use/sign setas a workaround. - The new locale strings relating to waxed signs have not been proofread for the locales
de,nl,zh-CN,zh-TW, andzh-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 waxand/sign unwaxcommands and permissions to apply and remove honeycomb wax from signs, respectively - New locale strings:
wax_removed– Completed/sign unwaxactionwax_applied– Completed/sign waxactionbypass_wax_before– Warning before a/signtext change that wax will be removedbypass_wax_after– Warning after a/signtext change that wax was reappliedbypass_wax_cannot_rewax– Warning after a/signtext change that wax was not reapplied because the player lacks permission to/sign waxunwax_sign–/sign unwaxpending action descriptionwax_sign–/sign waxpending action descriptionforbidden_waxed_sign_edit– Error when attempting to edit a waxed sign without permission to run/sign unwax
Changed
- The documentation of
/sign undoand/sign redohas 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)
-
java.lang.IllegalArgumentException: Invalid page number (1)when usingcompatibility.sign-ui: EditableBookand 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 - Decreased the right-click event handling priority to the lowest level to avoid interfering with other plugins that handle right-click events on signs
- 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 undoand/sign redo- Started pulling
org.bukkit.entity.Playerout 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-rc-2
- Added JDK toolchain resolver plugin to download Java 1.8
- Skip ProGuard for development builds
- Eliminated the dependency on
commons-lang:commons-lang
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:ylgRcIHr:W9x1XGcS"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ylgRcIHr:W9x1XGcS"
}

