Bukkit

@DELETEDSTARKO

I've tested this just now using Version 0.312 and I simply can not reproduce this. What are your targets for the Skull in question and what is the skull type. The only way a skull could ever target ALL players is if player was used as the enemy type.
/sk add enemy player

If you then put:
/sk add friend player JohnDoe
That same skull would ignore JohnDoe but still target ALL other players. This was also tested under v312 moments ago and it functions as expected.

if all players are targeted then player must have been used as the target:
/sk edit - to select the skull
/sk rem enemy player - would remove ALL players as the target for that skull.

If there are no targets set on the skull then it is impossible for the skull to target anything. In fact the entire logic block for targeting is skipped for a skull in that state. Also, Crazed and Devious are incapable of targeting players even if a skull bow is used.

Right click the skull in question and view the book it provided. There will be a list of the targets that it will use when attacking.

What it sounds like is you have used a command globally and ALL your owned skulls were updated with player as an enemy. If you want to edit a specific skull you need to use the /sk edit command and right click a skull. Or if you already have a skull set up then you can get the skull book from that skull and go around clicking the skulls you want to set up with that book in hand.

Links: SkullBooks Global Commands

@HookManJack

Yes but a golem now wont be a target either yet it too can become mad. And I agree those are passive and should not be a target. However, a Enderman is neutral too unless you look at it without a pumpkin on, and so is a pig zombie. Yet they are a target and I would assume you agree they should be. So in those corner cases I defer to bukkit class inheritance. For a wolf it inherits from Animals, so its classed as passive. If it inherited from Monster then it would be hostile and therefor a target. Crazed and Devious are dumb skulls they were never meant to differentiate that much. If you want exacting targets thats what Master and Wizards are for ;)

I've always planned Crazed and Devious to be cheap turrets for use when you want quick defenses. The real workhorse is always going to be a Master skull with the Wizard in a support role.

Anyway, glad you like it, I'm sure when the next alpha gets approved you'll get a kick out of the new stuff too :)

@DELETEDSTARKO

You haven't really said what permissions plugin you use. I am therefor not sure if your particular permissions supports supernodes. IE the infamous " * " permission. So it could be possible that you need to use
skullturret.target."mob"
"mob" being each mob you want to be allowed to target.
Exampe:
skullturret.target.pig
Do note that the entire permissions node must be in lowercase.

That's pretty much all I can offer. I don't really specialize in permissions, the API is designed so that I don't need to know how every permissions plugin works. I just need to follow the standards provided. Bukkit sorts out the details.

@HookManJack

Yep, I've added a check for NPCs now too, which includes villagers. Thank you for the heads up.

@HookManJack

Kind of vague... I'm assuming you mean Crazed and Devious skulls. In that instance yes Golems are targets... Just something I've overlooked in targeting mobs. Since I only check if a mob is classified as an animal or a monster. But they are neither, much like a bat or a squid which I have to specifically test for.

Anyway, I've put a check in for alpha 3. This is not a critical issue though. So, I wont be making a special version just to fix this. If something major comes along I'll just include a fix for this along with whatever fix I need to do that is critical.

@Malachi21

That is a known bug and is fixed in v312 but the latest alpha available still has that bug and I wont have another alpha ready for a while.

@jhicks32917

will it be possible to select the max duration a turret is active before breaking/ deactivating

So basically a temporary turret? I suppose that may be possible in the future.

will it be possible to change how much damage each turret does

Thats already in the config for skull types in general. See damage_mod portion of the config.

spawn a turret via command and either the turret auto target the nearest aggressive mob

ready made turrets via command is a possibility also but pretty far down on the priority list

allow the player to mark valid targets using a bow & arrow

Already available via the skull bow item

it would be nice if turrets could be deployed with a preset amount of ammunition

Ammo chests are an option already but preset ammo amounts built into the turret are not. Its also possible in a future version.

I'll take the ideas under advisement. Right now I'm trying to figure out how to allow skulls to be damaged. Which will be the major feature of the next version if I can manage to get it working right.

Any additional requests will have to wait for some future time.

@DELETEDSTARKO

I have to use permissions to test any part of the plugin, so thats under constant testing. Here is what I'm using for my testing right now: (copied straight from my permissions.yml file)

    - skullturret.create
    - skullturret.edit
    - skullturret.addplayer
    - skullturret.remplayer
    - skullturret.listallplayer
    - skullturret.listplayer
    - skullturret.give
    - skullturret.skin
    - skullturret.debug
    - skullturret.changeammo
    - skullturret.reload
    - skullturret.destruct
    - skullturret.target.*
    - skullturret.multiskullupdate

I am currently using permissionsEx 1.19.6 (probably not the latest version but it works for my devserver) anyway, that wont really matter since I use bukkit calls for permissions tests. Everything seems to be working correctly on my end.

If you want to see error message for Permissions put the plugin into DEBUG = 2 in the config. Then build a skull or do things with the plugin in game. Commands and such.