Tags
Creators
Details
Licensed GPL-3.0-only
Published 2 months ago
Updated last week
All versions
2.1.0
Release
rGoldenHeads 2.1.02 weeks ago 66
Compatibility
Minecraft: Java Edition
26.3
26.2
26.1.1–26.1.2
1.21.4–1.21.11
Platforms
Folia
Paper
Purpur
Changes
Added
- One jar for Paper 1.21.4 – 26.3 and Folia. Every supported version is booted and checked by an automated smoke test before release. Servers older than 1.21.4 now refuse to load the plugin with a clear message instead of failing halfway through.
- New default Golden Head skin. Heads now pick a skin by name:
head-skin: modern(the new default) orhead-skin: classic(the original look). Add your own underhead-skins:. Existing configs keep their current look; switch with one line. /rgoldenheads give <player|*> <item> [amount], usable from the console so kit and UHC plugins can hand out items. New permissionrgoldenheads.admin.give, deliberately kept out ofrgoldenheads.give.- Update checker. Asks Modrinth once per startup for a newer release that matches your
server version, and tells admins (
rgoldenheads.admin.notify) on join. Disable withupdate-checker.enabled: false. rgoldenheads.adminis now a parent node of.admin.reload,.admin.giveand.admin.notify, so existing admins keep reload and gain the rest.
Changed
animation: TRIDENTworks on every version. Before 1.21.11 the trident animation was calledSPEAR, and the plugin now maps it for you.- Giving items is Folia-safe: inventory changes run on the receiving player's own thread.
Fixed
- Startup no longer logs "Item '...' was added, but its command will not exist until the server restarts" for every item. That line now only appears for items actually added by a reload.
- The
drop-overflow: falsedescription now matches what happens: the items that fit are given, and the rest is discarded.
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:n4TUPak0:2bRXwsOt"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:n4TUPak0:2bRXwsOt"
}

