All versions
1.1-rls
Release
Finally Fixed2 months ago 124
Uploaded by
Compatibility
Minecraft: Java Edition
26.2
26.1.x
1.21.x
1.20.x
1.19.x
1.18.x
1.17.x
1.16.x
1.15.x
1.14.x
1.13.x
1.12.x
1.11.x
1.10.x
1.9.x
1.8.x
Platforms
Bukkit
Folia
Paper
Purpur
Spigot
Changes
Added
lastRankStylehelper — extracts the last full style segment (color + format codes like§6§l) from a rank, used to make the player-name segment indisplayNameinherit the rank's formatting
Changed
- Chat format handling (modern versions) —
%rank%/%name%combinations are now unified into%1$s(which expands to displayName already containing rank + name), eliminating prefix duplication and%xxx%residue applyScoreboard—setColornow receives the §-translated rank (rankColored) instead of the raw&string, soTeam#setColoractually appliesapplyDisplayName— player-name segment now carries the rank's trailing style (color + bold) vialastRankStyle, so the name in system messages / chat follows the rank formatting
Fixed
UnknownFormatConversionExceptionon chat (Conversion = '§'/'&') —setFormatinternally runsString.format, which chokes on leftover%rank%/%name%placeholders; all rank/name placeholders are now replaced with%1$s/%2$sbefore callingsetFormat, so it no longer throws- System messages (death / tp) showing white player names — the root cause was
lastRankColorreceiving the raw&-form rank (which only scans§), returningnulland silently skippingTeam#setColor; now receives the §-translated rank, so the name color in death/tp messages correctly inherits the rank color (color only, not bold — asetColorlimitation on modern versions) applyDisplayNamename segment white — the last rank style (color + format) is now appended before the player name, so the name inherits the rank formatting
Removed
- (nothing)
Optional dependencies
Any compatible version
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:og7SQTbp:B7uMeGYy"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:og7SQTbp:B7uMeGYy"
}

