Links
Tags
Creators
Details
All versions
1.2.0
Release
AddHeads 1.2.07 months ago 486
Compatibility
Minecraft: Java Edition
1.21.9–1.21.11
Platforms
Paper
Purpur
Spigot
Changes
1.2.0
- Added automatic native
TABAPI integration. IfTABis installed and player-list heads are enabled, AddHeads now switches to the built-inTABcompatibility path automatically with no extra AddHeads-side toggle. - Fixed player-list head rendering with
TABwhentablist-name-formattingis enabled, so heads now render correctly together withTABprefixes, suffixes, colors, and other tab formatting options. - Preserved external tab formatting more reliably so AddHeads prepends the head without wiping colors, prefixes, or suffixes from supported player-list plugins.
- Applied the same tab head settings to the
TABintegration path, including correct skin loading from cache, tab head shadow handling, and configurable spacing after the head. - Synchronized
TABcomponent settings with AddHeads tab settings by forcing the compatible parser mode and matchingTABhead-shadow behavior to AddHeads' tab shadow option. - Kept viewer-based tab head rendering through ProtocolLib for the standard compatibility path, so
/hd toggletabcontrols which heads the viewer sees instead of changing one global player-list name for everyone. - Reapplied tab heads after joins, cache refresh cycles,
TABplayer-load events, andTABreload events so formatted names and heads recover correctly after refreshes. - Confirmed compatibility with
CMI,QuickBoardX, andPowerBoardthrough the standard packet / scoreboard compatibility path, with no extra AddHeads-side integration toggle required. - Included a broad set of tab compatibility fixes and stability improvements across the built-in player-list path and the native
TABpath.
Optional dependencies
Any compatible version
Any compatible version
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:SCilJQz4:2vNkbz6b"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:SCilJQz4:2vNkbz6b"
}

