Player Heads
Ever PVP someone or PVE a mob and get no good loot? Feel like you deserve a trophy for your victory? Want a simpler alternative to bigger plugins that implement everything but the kitchen sink? Then PlayerHeads is right for you! You can now lop off enemies heads in battle, and mount it on a pole for all to fear, wear your opponent's face as a mask like camouflage, or just collect all of the mob heads.
Installation
Place PlayerHeads.jar in your plugins folder, on server start the configuration will be generated. Remember to remove any outdated playerheads jars when adding the new one.
If you can't be bothered to read the rest of this page, then just watch this video by Awesome_Soul:
Portuguese (Português) video: http://youtu.be/OqhI_oIGPWo
German (Deutsch) video: http://youtu.be/ijEws5yjo6Y
Try It
Server: aztecmc.org (rare drops are enabled for mob and player-heads)
Website: aztecmc.org
Documentation
Notes
- PlayerHeads is now translatable! Edit "lang.properties" to whatever phrases you desire.
- lang files will change between releases, when updating be sure to delete the old file if you haven't edited it.
- If you've given people the * permission node, they will get 100% drop rates. If you don't want this to happen, deny (or add negative) nodes for the following: playerheads.alwaysbehead and playerheads.alwaysbeheadmob
- If you want to disable head drops in a specific world, use your permission plugin to deny (or add negative) nodes for the following in that world: playerheads.canbehead and playerheads.canbeheadmob
- If you have any problem using "lang_[language]_[country]_[variant].properties" for any reason, just use the file name "lang.properties" to override messages.
- Spawn mob heads with the following names: #creeper #zombie #skeleton #wither #spider #enderman #enderdragon ... (any many more!)
Known issues
- Renamed heads (with an anvil) don't stay renamed after placing, mining, dropping them.
- If for any reason your mob heads loose their name, you can get it back by placing and mining it.
- If you use the BountyHunters plugin and you have enabled head drops for bounties as well as player head drops from PlayerHeads, both will be dropped - for now, you should disable one or the other. Alternative solutions are being looked at.
- If you use JPerms, users with Op or playerheads.* permission will receive playerheads.alwaysbehead[mob] permissions and have 100% droprate since PlayerHeads permissions nodes are ignored. It's recommended to use another permissions plugin if this is a concern (LuckPerms, PermissionsEX, GroupManager).
Dev Builds
Development builds of this project can be acquired at the provided continuous integration servers. These builds have not been approved by the BukkitDev staff. Use them at your own risk.
https://ci.meme.tips/job/PlayerHeads (upstream)/ (selected major changes only)
https://ci.meme.tips/job/PlayerHeads-5.x/ (rapid changes and work-in-progress)
Sourcecode / API documentation
We've included the entire sourcecode via github:
https://github.com/meiskam/PlayerHeads
Third-party plugin-developers can view the PlayerHeads API documentation at the following link: https://crashdemons.github.io/PlayerHeads/
Server Support
Current versions of the plugin have been tested as compatible on the following server environments:
- Spigot/Paper 1.8-1.18.2 (Use PlayerHeads 5.20.2 or lower; READ NOTE)
- Spigot/Paper 1.19-1.20.4
Server environments that are known to be incompatible:
- Glowstone 1.12 (only partial support is available in PlayerHeads 5.20.2 and lower)
Support should exist for any modern bukkit server with access to authlib which is needed to set textures.
Legacy version notes:
- 5.x drops support for older usernamed-based mobheads (3.x), fixing some longstanding issues with spawn commands; uses vanilla and texured heads exclusively (4.x)
- 4.x introduces new, more reliable support for head textures, more configuration options, updated mobs, and more consistent permission behavior and will continue to receive updates in the future - some older configurations may be incompatible (see the changelog and Configuration page). This version automatically upgrades 3.x heads to 4.x when breaking or dropping heads.
- 3.x maintains the original behavior of the plugin with username-based mobheads, but head skins may be less reliable over time and support has been discontinued.
Legacy version documentation: changelog, configuration, permissions.
A found a game breaking bug... I did a short <30 second video that I will PM you a link to.
Very nice plugin! We are having some fun with it on our server!
So far I have setup a 'Wall of Shame' of all our banned players heads :D
Would it be possible to make the Name Display with a right click instead? So when people are in creative they can still see the name without breaking the head. thanks!
Players are duping heads by placing them in WG regionsw
Just a report on the heads, If you place a head to water it turns in to a wither head. Any ideas that could this get fixed? players might start griefing places with them...
Players without the behead mob permission are still removing heads from mobs.
To everyone wondering about block protection: I'm not going to write in special case configs or options for specific plugins which are using the wrong priority, it would be as simple as changing 1 word in any of these plugins for them to come into compliance with the APIs recommendations.
That being said, Minecraft 1.4.3 fixes the bug that this problem centers around, and I will be able to remove an entire event which fixes player heads to be dropped with their name intact (instead of Steve). The config "hookbreak" controls this event and turns it off if set to false, I've tested on my server with WorldGuard and hookbreak: false, and the heads were protected for people without permission.
@rasnyderiii
Strange, it works fine for me, hop on IRC and we can hash out why it won't work for you.
For some reason these aren't recognized as blocks with the Precious Stones plugin. :/
@meiskam
I'm also VERY interested in this, anyone figure out a way to rig any protections to work? I run Factions and WorldGuard. I would love to see protection with Factions because you potentially raid someone to get your head back.
I also run ChestShop and it looks like you can create a shop with the heads and sell them, lol.. awesome. Best plugin EVAR!
"Otherwise just turn "hookbreak" to false" Heads are still able to be broken.
Forgive me, this plugin is fantastic and thank you for your work! But just hook into WG with a config option to allow it priority. WG has enough to deal with and is a core plugin.
@lolitsthad
Update CB, should fix that.
@Demonlover11
First off, pigs don't drop their head and second off if you want a specific mob to not drop it's head, then just set the droprate of that mob to 0. Regarding the bug, what version are you running? To my knowledge this has already been fixed.
@imaapseudonym
I suggest asking sk89q to use event priorities correctly in his worldguard plugin, then the heads would be protected. Otherwise just turn "hookbreak" to false.
Any way to make worldguard protect the heads like it does the rest of the region?
I use the precious stones plugin for players to have personal area protection. Add - '397' to the precious stones config under the unbreakable blocks line. Now any head placed within someones protection stone field will be protected. Heads outside of the field can still be broken by other people.
@EncryptedCurse
I suggest you report it to the factions plugin. General land protection is supposed to be run at EventPriority.LOWEST, which they are not running at.
@meiskam
Could you try to make it work with Faction's land protection, or should I report it to them?
could i request a console command to give a player ingame a player head?
e.g. "/ph <playername> spawn <playername>"
Thanks
Hey meiskam, me and my group, K4G, made a video showing off your awesome plugin! It would be great if you would put it up on the main page, this is, if you like it of course :D. Link: http://www.youtube.com/watch?v=U4ewTMvPdGI
Thanks.
@EncryptedCurse
Because of a bug in minecraft, I've had to add extra checks to make sure the name of the head persists after mining a placed block. Supposedly this is fixed in 1.4.3 so the fix will no longer be necessary. If you want to disabled this feature, feel free to set the config "hookbreak" to false.
As far as saying these heads can't be protected by some other protection plugin, that would be completely false. If your protection plugin uses event priorities properly these heads would be protected just fine.
Apparently heads spawned through this plugin aren't and can't be protected by any other plugin (Factions, for example). Could you look into this? I really can't have heads around the spawn when they're grief-able.