Tags
Creators
Details
1.7.0
Compatibility
Changes
Added
-
Sign-translation: multi-key support.
detectnow accepts a list of translation keys viakeys: [...]in addition to the singlekey. Any one of the listed keys being resolved by the client is treated as a hit — useful for mods that ship several keybinds (Xaero, Litematica, JEI…) or where key names differ across mod versions.MyMod: detect: keys: - "key.mymod.a" - "key.mymod.b" punishment: action: KICK reason: "..." The old key: "..." form still works — 100% config-compatible.
Improved
- Sign-translation support probe now tells you WHY it's disabled. Previously the console just said "current server/API does not support it"; now it names the exact class or method that's missing, e.g.
▎ Sign translation detection unavailable: missing method org.bukkit.entity.Player#openVirtualSign(Position, Side) (Paper API too old; sign-translation needs Player#openVirtualSign, which was added in Paper 1.21.5 and does not exist on 1.21.4 or earlier; Spigot and some Paper forks like Purpur/Pufferfish/Leaves may also lack it).
- Makes it obvious whether you just need to update Paper, or whether you're on Spigot / a Paper fork that doesn't expose the sign API yet.
Docs
- config.yml now explains up-front that forbiddenList matches plugin-channel names, not mod display names, and points users to sign-translation.mods for client-only mods that never register a plugin channel. Multiple people were hitting this footgun.
- Added a commented-out Xaero example showing multi-key config.
Compatibility
- No breaking changes. Existing configs continue to load untouched.
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:Z7Zlnljn:A6lBziYR"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Z7Zlnljn:A6lBziYR"
}

