Bukkit

In reply to InsaneGames_:

 v5.2.8 (from the Files tab) includes the new heads for Hoglin, Zoglin, Strider, and Piglin.
 However it was made before 1.16 released, and support for Zombified Piglins does not work correctly in that version. (that specific head doesnt drop)

I have uploaded v5.2.9 this morning to correct the issue, but it is still pending moderator review which sometimes takes quite a while. 

Basic tests with all of the new heads seemed to work correctly on 1.8, 1.12.2, 1.13.2, 1.15.2, 1.16.1 (including mob drops).  Since there were no changes to heads other than Zombified Piglin (PigZombie), I would expect everything except that to function on v5.2.8

Keep in mind both of these are Beta versions and could contain issues not seen in 5.2.5.

In reply to ThE_WiZ76:

 A head drop chance roll occurs on each valid kill, and a head will drop if the roll is above within the droprate defined in your PlayerHeads configuration, but for players it can be further limited somewhat by the deathspam settings (which were added to ease chat spam and player head farming) - however these are not intended to track extremely long periods and will not track death times across server restarts. 

(Note: if you have playerheads.* permission, you may get 100% droprates. To prevent this, either do not give the star permission, or negate permissions for playerheads.alwaysbehead and playerheads.alwaysbeheadmob)

Preventing collection of 'more than X heads' would need some extensive logging of all dropped heads and is not supported in-house.

If you want to limit heads collected, I would recommend lowering the head droprates (probabilities) [in the configuration file] for the entities your are interested in as the easiest way.

However, if you're able to create a plugin and you prefer to limit head drop numbers rather than droprates, there is a PlayerHeads API.  If you listen for HeadDrop events, your plugin has the ability to collect information on drops and cancel them from occuring.  If you listen to HeadRoll events, you are able to modify droprates with your own logic.

Thank you for your interest in PlayerHeads.

In reply to etcroot:

 You can deny the playerheads.clickinfo permission for the group(s) you don't want to see the message. 

As for how, you have a couple options: permissions.yml is managed by bukkit and will work, but a permissions plugin like LuckPerms etc is generally recommended for most users for easier configuration.

 This is mentioned at the end of FAQ entry #3 as well.

Note: if you've given a group playerheads.* it probably gave clickinfo by default.

In reply to bl4ck5t0rm:

 No - it's possible to implement, but it will break the ability to use heads in trading (vanilla villager summons or Shopkeepers) since those require all item tags to match.  I'm not sure that's really worth it.

EDIT: fixed yes/no - yes it's possible to add, no it's not an option currently.

In reply to lelesape12:

 heads drop 100% at any chance if you are Opped or have playerheads.* or playerheads.alwaysbeheadmob permissions.

you would need to deop, and/or deny those permissions specifically (as mentioned in FAQ entry #9) using your permissions plugin or permissions.yml (if you have other permission that included them)

Changing witherskeletonbehavior to vanilla or block (or setting witherskeletondroprate to -1) will also prevent PH from creating drops entirely.  The ignore setting rarely allows for duplicate drops, but this is more noticable when you have permissions to always get drops.  If you choose vanilla, Minecraft itself will manage the drops at a rate of 2.5%.

PS: Choosing replace disables vanilla drops and only allows PH drops with configurable rates (although you would still need to fix your permissions to prevent 100% drops).

In reply to FlipperWolf26:

#1 -  Because of changes to Minecraft and Spigot (I think in 1.13), plugin commands no longer support selectors by default. Each plugin would need to implement all of the selectors themself to do this. There are a few plugins that add rough replacement support, but none of them are perfect. 

If anyone wants to implement a dirty workaround with full selector support I can imagine being able to send / capture a vanilla tellraw command's resolved selector recipients - but there are some obvious drawbacks to the approach.  There may be also an NMS method for resolving selectors, but that introduces version dependence.

Until there's a good answer for this issue, I don't see this being easy to add.

Ref: SPIGOT-4295, manual selection, NMS selection, plugin to add basic support, another plugin.

#2 - This is more feasible, but it is not a feature yet (#59) although some work needs to be done to make sure the profile information (texture, owner) of the head can be set properly on the block in all versions. there also wasn't much development on this feature because it's not requested very often...  If I manage to get time I can look at how difficult this is to add, but it may be a while.