Links
Tags
Creators
Details
Licensed MIT
Published 2 months ago
Updated 2 months ago
All versions
2.0.0+mc1.21.1
Release
BetterChatHeads (1.21-1.21.1) v2.0.02 months ago 37
Compatibility
Minecraft: Java Edition
1.21–1.21.1
Platform
Fabric
Supported environments
Client-side
Changes
Better Chat Heads v2.0.0 Changelog
Major Upgrade
- Reworked the mod into a bigger v2.0.0 release
- Improved overall multiplayer reliability for player head rendering
- Cleaned up the in-game config experience and release metadata
Added
- Smart Skin Sync+
- Live Skin Swap
- Per-Server Profiles
- Server Learning Cache
- Better support for rank-heavy and custom-formatted server chat
- More polished config layout and visual styling
Improved
- Username and sender matching across more server formats
- Skin fallback recovery for players that do not resolve immediately
- Handling for separators such as >>, », ->, ➟, and similar formats
- Duplicate chat merge handling so repeated messages keep original color styling
- 720p config layout handling and smaller-screen UI spacing
- Overall chat presentation and release polish
Fixed
- Some users showing default Steve/Alex heads instead of real skins
- Missing heads in certain lobby and gamemode chat formats
- Spam-repeat merged messages losing original colors
- Several server-format edge cases that broke sender recognition
- UI overlap and footer collisions in the config screen
Removed
- Tablist upgrade path
- Tab heads and tab accent ring features
- Head click copy-name feature
- Head shape feature
- Experimental styling paths that were not reliable enough for release
Release Notes
- This version is focused on chat-first rendering, not tablist features
- The mod remains client-side only
- Separate compatibility branches may be used for different 1.21.x minor versions
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:HuMu096l:l2Bv0VqC"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:HuMu096l:l2Bv0VqC"
}

