Tags
Creators
Details
7.0.11
Compatibility
Changes
dcdaf4e feat: functional placeholders and %headsplus_next_level%/%headsplus_next_level_xp% - Thatsmusic99
0ac2671 fix: null pointer exception on copying - Thatsmusic99
1339d4d chore(deps): update - Thatsmusic99
1a1a626 fix: NPE in placeholders when reaching the maximum level - Thatsmusic99
8cd45d7 fix: use of apache commons lang - Thatsmusic99
7f3307b fix: removing imports may actually be a good idea - Thatsmusic99
a882aa7 feat: add command triggers when heads are dropped - Thatsmusic99
70a2b88 fix: only grab UUIDs in forceSetProfile when the username is valid - Thatsmusic99
959a176 fix: translate colour codes in inventory titles - Thatsmusic99
ceb9b9a fix: heads in /sellhead looping when using /hp reload - Thatsmusic99
c95ab4e fix: lore not being added to sellable heads - Thatsmusic99
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:5BNpeqz1:sWG4R3E3"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:5BNpeqz1:sWG4R3E3"
}
