Links
Tags
Creators
Details
v1.3
Compatibility
Changes
ColoredSigns2 v1.3 — Security, Configuration & Modernization Update
This major update introduces robust claim protection checks, honeycomb-waxed sign support, fully configurable messages and settings via config.yml, bug fixes for hex formatting, and automated GitHub Actions workflows.
🛡️ Security & Anti-Griefing
- Area & Claim Protection:
/editsignnow triggers nativeSignChangeEventchecks before modifying blocks, ensuring full compatibility with land claim plugins (WorldGuard, GriefPrevention, Towny, Lands) and block loggers (CoreProtect). - Waxed Signs Respect: Permanently locked / honeycomb-waxed signs (
sign.isWaxed()) can no longer be edited unless the player has thecoloredsigns2.bypass.waxedpermission.
🎨 Color & Formatting Fixes
- Hex on Sign Placement: Fixed an issue where
&#RRGGBBhex colors were not parsed when placing signs or editing them in the vanilla sign GUI. - Magic Code Toggle: Added a configuration option to disallow obfuscated/magic text (
&k) on signs.
⚙️ Configuration & Localization
- New
config.yml: Added full configuration support with Adventure MiniMessage message formatting. - Customizable Settings: Easily adjust
max-distance, toggle vanilla GUI color preservation, and toggle tab-completion suggestions. - Admin Reload: Added
/coloredsigns reloadcommand with permissioncoloredsigns2.reloadto reload configuration on the fly.
🤖 CI/CD & Project Polish
- Automated Publishing: Added GitHub Actions workflows for automated verification builds and publishing releases directly to Modrinth.
- Modernized Paper API: Set
api-version: '1.21'for seamless compatibility across Paper 1.21 through 26.x. - Documentation & Licensing: Added official MIT license, concise Modrinth-ready README, and developer guidelines.
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:JdLdvPE7:PnOQbFx5"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:JdLdvPE7:PnOQbFx5"
}

