Tags
Creators
Details
1.13.8
Compatibility
Changes
Fixed
-
The German (
de) locale pluralized 0 incorrectly in thehistory_havestring.Credit to @phpwutz
-
A minor typo in the file that gets deployed to
./plugins/SignEdit/locales/README.txt -
A race condition that assumed that a block is still a sign when using
compatibility.edit-validation: Extra(#33)
Changed
-
If the file modification time of
./plugins/SignEdit/config.ymlis not changed, the configuration will no longer be reloaded. (#29)This means that merely changing the file's ownership or permissions will not trigger the configuration reload anymore.
Under the Hood
- Updated copyright year 2023
- Restructured
SignSubcommandinheritance to make more sense - Replaced constructor injection of
ChatCommswith a factory to avoid nesting assisted dependency injections - Extracted line selection parsing to new class
LineSelectorParserto improve separation of concerns - Gradle has been updated from version 7.3.1 to version 8.1-rc-2.
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:78ptek3a"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ylgRcIHr:78ptek3a"
}

