Tags
Creators
Details
1.13.9-beta2
Compatibility
Changes
Pre-Release Notes
Since Previous Pre-Release
- Restored compatibility with Bukkit 1.8.3 through Bukkit 1.12.2
Known Issues
- Waxed signs (i.e. signs with honeycomb applied to them) remain editable with
/signsubcommands. - Edits made with the Minecraft 1.20 native right-mouse click sign edit action on unwaxed signs are not registered by SignEdit for Bukkit. We might not be able to handle these native edits due to SPIGOT-7391.
- When using the Spigot server,
/sign uiedits might not be registered. This might be due to a bug in Spigot'sSignChangeEventhandling. Either switch to PaperMC or use/sign setas a workaround. - When using
/sign uiand 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)
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 - 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
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:jxKSZe9Q"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ylgRcIHr:jxKSZe9Q"
}

