2.1.3
Compatibility
Required content
Changes
Fix: nicknames no longer render as the literal placeholder text (e.g. %styled-nicknames:display_name%) on Fabric / PB4.
The server PB4 integration now builds its parse input with PB4's LiteralNode instead of reflecting Text.literal(String). Under intermediary mappings Text.literal and Text.translatable are indistinguishable static String->Text methods, so the old shape-based lookup could non-deterministically pick translatable and turn the placeholder into an unresolved translation key. LiteralNode + Placeholders.parseText(TextNode, PlaceholderContext) is deterministic and mapping / loader / version agnostic.
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:kcWnKtP9:x81LbqJB"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:kcWnKtP9:x81LbqJB"
}


