Tags
Creators
Details
All versions
3.2.0+spigot
Release
HeadBlocks 3.2.0 (Spigot)2 months ago 65
Uploaded by
Compatibility
Minecraft: Java Edition
26.2
26.1.x
1.21.x
1.20.x
Platforms
Bukkit
Spigot
Changes
HeadBlocks v3.2.0
What's New
✨ New Features
- Added Folia support.
- The plugin now ships as two jars. Paper, Purpur and Folia servers use
HeadBlocks-<version>.jar; Spigot servers useHeadBlocks-<version>-spigot.jar(SpigotMC).
🚀 Improvements
- Added support for Minecraft 26.2.
- Headblocks paper jar is now a native Paper plugin (
paper-plugin.yml), which gives it an isolated classloader and an explicit dependency declaration. The Spigot jar is unchanged.
🐛 Bug Fixes
- Fixed a per-head reward loading error after
/hb reload. - Fixed hunt files not being rewritten when heads were removed in bulk, which made removed heads reappear after a restart. Hunt files are now written atomically.
- Fixed a head rotation task leaking on every
/hb move, which made moved heads spin twice as fast. - Fixed heads in an unloaded world scheduling a rotation task that errored on every tick.
- Fixed holograms failing to spawn on 1.20.5 and later, which flooded the console with
NoSuchMethodErroronce per head. - Fixed particle names being rejected on 1.20.5 and later, where Minecraft renamed them (
REDSTONEbecameDUST, and so on). Both spellings are now accepted on every supported version, and an unknown name no longer spams the console.
Thank you for using HeadBlocks ❤️
If you find a bug or have a question, don't hesitate to :
- open an issue in Github
- or in the Discord
- or in the Spigot discussion
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:bpD0tpKu:gfCtJcFc"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:bpD0tpKu:gfCtJcFc"
}

