Bukkit

In reply to graymold9:

 how are you changing the setting? with the config command (/ph config set cowdroprate 1.0) or editing the file?

if you are editing the file directly, did you use the /ph config reload command to load the new settings after saving the file?

if you've changed the rates ingame or used the config reload command then a rate of 1 should always drop a head (assuming nothing weird like negative lootingrate) if you have the playerheads.canbehead/canbeheadmob permission and other self-imposed restrictions (pkonly/mobpkonly, requireitem).

If you still can't get a head to drop then it may be more likely another plugin (like arena, keepinv, or protection plugins) is cancelling the successful drops, in which case youu may need to change the antideathchest setting.

EDIT: does a lower level of looting work? I'm not sure if 30,000 is valid.

Thanks

In reply to pinakeeg:

 If there's any lag then it should be related to the server loading Player's heads (based on usernames) which would happen with other plugins also (eg: the same user's head generated with /skull username using Essentials).   This shouldn't be an issue if you don't have something causing problems with skin caching, username/uuid resolution or connecting to mojang servers (like if you have the server in offline-mode).

PlayerHeads doesn't even do anything during heads being placed or listen for heads being placed - heads being placed and their texture/account information being updated is something the server does itself.

In this case there may be no other solution than to set dropboringplayerheads: true which prevents new heads for Players from having an account or username attached to them - which should eliminate any delay, but unfortunately it will cause player's heads to all appear as Steve/Alex.

In reply to Ninjamaster4427:

 Which plugin version did looting last work in for you?
  What kind of droprates for mobs do you use? (an example, cowdroprate / piglinbrutedroprate)

  What other kinds of plugins do you use on the server and which version of Spigot/Paper/etc do you use?

As an aside, you've defined players to have a droprate of 100%, that will not be affected by looting to provide more than one head.

Thank you, this will help with attempting to reproduce the issue.

In reply to MithrandirMage:

 Please post logs from when PlayerHeads loads during the start of the server.

 Are there other ".properties" files in your PlayerHeads folder?

If your server locale is different, it may be preferring another file.

I'll try to reproduce the issue and investigate this weekend (I'm very busy with work at the moment), but it's more likely to be a file conflict issue. (preferring a different file, or unable to access the file provided, etc)

If you provide your lang.properties file, that would also be helpful to debugging the issue.

In reply to MithrandirMage:

 I tested today and I wasn't able to reproduce your problems - I used Paper 128 and PlayerHeads 5.2.9.

When I used your .properties file and restarted the server - head names and messages were translated how you have configured them.

I used /playerheads spawn __Mithrandir__ , I also tried with zombie (*see note) and cow.

So I'm not sure why you would have issues, but there are some possible causes:

• the lang.properties file must have that exact name and live at <Spigot or Paper Directory>/plugins/PlayerHeads/lang.properties path exactly on your server.  You probably already confirmed this is correct, but I want to be clear again.
• Check what the text encoding of your lang.properties file is. The one I got from your Gist is regular ANSI text, but if your own is UTF-8 or something else (especially if it has a BOM at the beginning from editing in Windows), it may be breaking Java's ability to read the file, although this normally shouldn't be an issue.
• If you run your own server, make sure Java has permission to read the lang.properties file.  Especially on linux systems, creating a file from another user or with a bad chmod value can lead to the file being inaccessible.
• Are there any other warnings or error in the server log while using the plugin?
• Try redownloading PlayerHeads, or even try PlayerHeads 5.2.10. There should be no major behavioral changes from 5.2.9, but this will ensure you have a fresh JAR.

(*Note: the name of default vanilla heads (Zombie, Skeleton, WitherSkeleton, Dragon) is not translated by this plugin because a name is not set - it is determined by client language settings. Third-party heads like Cow, Husk, and Player drops are handled by the plugin.)

In reply to Forge_User_10250485:

 if you are Op or you have given yourself the playerheads.* (or playerheads.alwaysbehead / playerheads.alwaysbeheadmob) permission - then your rate will be 100% for staff with those permissions.

To fix it, you will need to negate (or deny, depending on your permissions configuration) the two permissions I mentioned lastly above.

(or don't give the star permission at all)

This is also mentioned in FAQ Entry #9.

Thanks.

In reply to Forge_User_06324517:

 the droprate for the player is just called droprate for legacy reasons.

if you're not getting headdrops when dying to mobs or natural death, make sure that the pkonly setting isn't on (it is on by default) - this setting makes it so heads only drop from deaths caused by a player.

keep in mind to drop a head you also need the playerheads.canlosehead permission (on by default).

In reply to venqueuev:

 This plugin does not provide detection range benefits; I think that line of text was originally written in a more literal sense (although it was before I came onto the project).
It is possible for a plugin developer who wants to add this feature to check the head the player is wearing using the PlayerHeads-api though.

In reply to kyles120:

 having you tried changing the antideathchest setting in the config?