Bukkit

In reply to Falastar:

 Hello, thank you for the report. I believe I know which part of code causes this warning (originally as a debug message) and I'll try to work on correcting this this weekend

[there are some concerns about information from early class init before the logger is available - but I should be able to defer that information until load]

This message or the cause should not impact plugin behavior but it definitely is poor form on my part and I'll strive to fix this in the next version

EDIT: Issue where you can track progress of this when there is progress to report. https://github.com/crashdemons/PlayerHeads/issues/87

In reply to lapstle:

 Well, if they have playerheads.canbehead and playerheads.canlosehead permissions, they should be able to drop a head.

I would check what the droprate (config option is just "droprate") is for your playerheads.  (1.0 is 100%) - excluding any setting that would block it like requireitem.

Another consideration is whether you have any other plugins that would impact item drops or heads (incl custom items).  If there is a plugin that could be blocking drops, you may want to change the "antideathchest" config option which will spawn the drop outside of the user's normal drops.

Remember to /ph config reload if you change the config file - otherwise please modify the config through the /ph config ___ set commands.

Can you post your config, which playerheads permissions you gave to users, and if there are other relevant plugins?

Also if it is not too much trouble, which permissions plugin do you use?

Thank you.

In reply to heybangsie:

 Sorry, that feature is not supported by the plugin at this time. It is possible for someone to add this behavior through a third-party plugin though by intercepting head drops

In reply to ravendefro:

 If you have access to the config files, you will need to edit the lang.properties file in the PlayerHeads configuration folder (plugins/PlayerHeads/lang.properties)

The entries you're looking for are BEHEAD_GENERIC, BEHEAD_OTHER, and BEHEAD_SELF.

If you want to add colors to the messages, I think you can just type the formatting code for it, using an ampersand in front (like &c for light red).

You will need to save the file, and the changes will not be applied until a server restart, I believe.

Let me know if that works.

In reply to rw_loothill:

 If heads are dropping 100% of the time, then the users receiving constant drops are most likely receiving the "playerheads.alwaysbeheadmob" permission.  You will need to negate or deny this permission to the relevant user groups through your Permissions plugin (like LuckPerms).

These permissions are actually defined to be denied by the plugin by default but certain permissions plugins or selection of permissions can cause them to be received anyway)

Also, if you are using the "star" (* or playerheads.*) wildcard permissions, you could remove those and explicitly define which permissions you want to give instead. 

If you happen to use JPerms and you have Op or a wildcard permission, there is an incompatibility because that plugin gives all subpermissions regardless of plugin-defined permissions and no further support will be provided for that plugin.

In reply to alplayz_everything:

 Hi! you can change the droprate of a player's heads by using the command /ph config set droprate 0.45

(you can alternatively change this in the config.yml if you use the /ph config reload command.)

this will change the droprate for players, if you want to set the droprate for a mob, the names of the config (mobnameheredroprate) can be found here

https://dev.bukkit.org/projects/player-heads/pages/configuration-4x

Keep in mind if you have playerheads.* permission or are op you might receive 100% droprate until you deny the playerheads.alwaysbehead permission.

Let me know if you have any other issues.

In reply to gonzalo20o0:

 you would need to deny the playerheads.clickinfo permission in your permissions.yml or permissions plugin.  In some plugins you can set the permission to Deny, some other you have to give the permission with a minus sign in front to negate it instead of denying

In reply to gonzalo20o0:

 I would recommend adding a plugin like LuckPerms (or at your preference: GroupManager or PermissionsEx).  Then you can use /lp group default permission set playerheads.clickinfo false  or the equivalent which sets the permission to deny for everyone (everyone is in the default group for LP).   There are also user-specific permissions commands if necessary.

A permissions plugin will make it easier to manage permissions from plugins without needing to edit the YML and adds the ability to assign people to permission "groups" for users like staff or VIP.

Permissions are a fairly standard feature for modifying many different plugins behavior, so a permissions plugin is almost a must these days.

In reply to LastChip:

 I don't have this behavior on our server or tests.

  I would recommend checking that you used /lp group groupname permission set playerheads.alwaysbehead deny - then you can look for possible other problems:

/lp check usernamehere playerheads.alwaysbehead  will tell you if a player receives the permission (collectively from their personal permissions, their groups, etc).

/lp group groupname permission check playerheads.alwaysbehead will tell you if the group has the permission

/lp group groupname permission checkinherits playerheads.alwaysbehead will tell you if the group inherits that permission from elsewhere.

Luckperms groups also have "weights" which mean higher-weighted groups override permissions from lower-weighted ones, if you have any other groups.

Finally, using the star permission "playerheads.*" or "*" is strongly not recommended and instead you should give specific command permissions.

If you're still unable to identify the source of the permission, please send the groups the user has, the permissions for the groups, and your PlayerHeads config and I will try to identify/reproduce your problem. (pastebin.com is preferred for posting long text).

In reply to Beaushangles:

 If you scroll down you'll see I've answered this question a few times.

You need to deny the playerheads.alwaysbehead and playerheads.alwaysbeheadmob permission in your plugin or permissions.yml.  How you do this depends on whether and which permissions plugin you use (I recommend LuckPerms).

Why does this happen? Well, it honestly shouldn't, because I have these permissions set to be denied by default, even for ops (in recent releases).  So this is usually due to overzealous permissions plugins, the use of the playerheads.* permission, or an outdated version of PlayerHeads.

Some questions that will help reduce my own hair-pulling:

 Which permissions plugin do you use, if any? which exact PlayerHeads version are you using? Which server /version are you using?

Thank you

EDIT: I'm unable to reproduce this issue on 1.8 or 1.16.5 servers with either v4.7.0 (three years old) up to v5.2.15 (newest alpha) without a permissions plugin - neither regular players nor ops received 100% droprates / alwaysbehead.  So I'm thinking this must be either playerheads.* permission or the specific permissions plugin.