Tags
Creators
Details
1.14.7
Compatibility
Changes
Added
-
/sign cutnow shows the unexpected differences when another plugin overrides the line removals.
Fixed
- When using
/sign setor/sign clear, sign text modifications made by other plugins (viaSignChangeEvent) were not detected due to a state tracking bug. This bug did not affect/sign ui.
Under the Hood
-
Removed the Dagger 2 dependency injection framework in favor of simpler manual dependency wiring.
This reduces the plugin JAR size by ~98KB (~38%) while maintaining the same separation of concerns through explicit service containers (
SignEditPluginServices,SubcommandContext). -
Added compile-time annotation processing for
@SignSubcommandInfoto validate subcommand metadata and improve tab completion accuracy with argument hints. -
Unified all
SignEditInteractionconstructors to acceptSubcommandContext, reducing boilerplate through a shared abstract base class with convenience accessors for common services.
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:HrAzdmMz"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ylgRcIHr:HrAzdmMz"
}

