Tags
Creators
Details
Licensed GPL-3.0-only
Published 2 months ago
Updated last week
All versions
2.2.0
Release
rGoldenHeads 2.2.02 weeks ago 62
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
- Crafting. Four recipes ship in the new
recipes:section:- Golden Head: a player head surrounded by 8 gold ingots.
- Instant Golden Head: the same grid, off by default; enable it instead of the Golden Head recipe if you prefer instant heads.
- Light Apple: an apple with 4 gold ingots in a plus makes a normal golden apple. Optionally renamed, e.g. "Light Golden Apple".
- Enchanted Golden Apple: a golden apple surrounded by 8 gold blocks makes the vanilla Notch apple.
- Every recipe is configurable: result (your items or any vanilla item), amount, shape,
shaped or shapeless, ingredient lists, item tags, your own items as ingredients, and an
optional permission. Recipes reload live with
/rgoldenheads reload. - Recipe book: recipes are unlocked on join and are click-to-craft (
recipe-book.unlock-on-join). Crafters work too. - Player head drops (
player-heads.drop-on-death, off by default): a dying player drops their own skinned head.only-player-killslimits it to PvP kills. - Recipe config is validated like items: duplicate grids, collisions with vanilla recipes, unknown ingredients and unmapped shape characters are logged with their config path.
Changed
- Your items can't be mistaken for their plain material in rGoldenHeads recipes: a Custom Golden Apple is not a golden apple and a Golden Head is not a golden carrot.
config-versionis now2. Existing configs keep working unchanged: until you copy the newplayer-heads,recipe-bookandrecipessections from the default config, heads don't drop and no recipes are added. The startup warning tells you so.
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:QZ0IQmYD"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:n4TUPak0:QZ0IQmYD"
}

