Bukkit

@kaitox

Wizard skulls will only shoot with the available splash potions they have and then only with a potion type that will actually do something to the mob it is targeting. You mention zombies and witches. However, you do not mention what potions you are giving the skull to work with.

Zombies can only be harmed using specific potion types. This is a minecraft limitation, so for instance a Zombie can only be harmed using a health potion. Also, wizard skulls will only use arrows if the target has very low health else it will continue to use potions. In addition to that, witches are 85% immune to certain splash potions, this makes a wizard skull a bad choice to this type of mob.

In the very next version I release (32b1) there will be a bit of changes to the wizard skull to buff it and make it a better. No date yet on that release as I'm still working out a new feature. So, just fyi.

Few more things, the more powerful the potion, the more effective the wizard skull is going to be. IE use Splash potion of health II instead of Splash Potion of health... Splash potion of harm is less effective then Splash potion of Harm 2 etc.

Last, the skull will only target things it can see, there is a line of sight drawn directly from the front of the skull at about the skulls eye level. In most cases this means it has no more then 200 degree field of view sometimes less, but no less then 180. Any obstruction directly beside the skull can also block the view of a skull.

Thats about all I can think of.

@RazorX2014

Nothing that I can think of, there isnt anything in the code that will just delete a skull. The death of a skull would remove the skull entirely, meaning you would have a loud boom and just fence posts left.

If the server was reloaded and the database was not committed to disk somehow I can see how the skulls would stop functioning but then all skulls would most likely not work. Not just a few. Also, that sort of error would not be cause by the plugin but by the server. Nothing I could do there.

I asked a bunch of questions, if you want help, TLDR; is not in your best interest.

So, without any more information to go on, best thing to do is replace the skulls and if it happens again try to reliably reproduce what caused it. If you can do that report back to me and we'll go from there.

@RazorX2014

Highly unlikely a plugin would be conflicting, most likely a setup issue.

My help for you is based entirely on how much information you give me.

Things like:

What do you mean by dont work?

They dont patrol? They dont shoot? etc.

What type of skulls are giving you problems?

If they are master or wizard skulls did you accidentally use a command globally and erase their settings?

Get a skullbook from the effected skulls to see if their settings are still there.

Do you have the plugin setup to use ammochests?

Do you have the skulls set to listen to redstone signals?

Is there an obstruction blocking the skulls sight?

(Skulls must be able to see the target or they wont shoot)

except crazed but thats fixed in 32a3

Are you using factions? Towny? vanishnopacket or disguisecraft?

Then there are the usual questions:

What version of the plugin?

What version of craftbukkit?

What permissions plugin?

Is there an error log?

What were you doing when they "stopped working"?

Did you restart the server? :Reload the plugin?

Leave that world? Etc.

@FearFracture4228

No, Ops are considered to have admin permissions and are therefor immune to skullturrets and will never be targeted. Its either Ops or Permissions cant have both.

Permissions info Fourth Bullet Point top of page. Reason being, hasPermissions return true for Ops, and one of the permissions available is skullturret.ignoreme - Will not be targeted by any skull under any circumstance

@xXBondc007Xx Yes there are permissions nodes:

Permissions

skullturret.attack.bow - allows users to attack with bow

skullturret.attack.weapon - allows users to attack with weapons specified in config

skullturret.attack - permissions node for both above permissions

skullturret.repair - allows users to repair skulls with item specified in config

Read the change log for info on additional changes. All this info is detailed there and for each release.

@xXBondc007Xx

Pretty simple really, you just shoot the skull or hit the skull with one of the weapon types you have set up in the config. Hit the skull enough and it will disable and eventually die if not repaired.

The only setup you need is to make sure that the config has the following turned on:

allow_skull_damage: true
allow_damaged_skull_destruct: true
allow_arrow_damage: true

All of the relevant settings are explained in the config so you know what each one does.

@k3kz0r

What version of skullturret are you using?

Just tested this, In the latest Alpha I can reproduce this, amazing how leaving out a simple " ! " can cause the whole thing to blowup :P Not really sure how I missed this, I'm positive it was working when I posted this version... <sigh>

Anyway, I'll put out a fix in a bit, but curse approvals have been taking at least 4 days so it could be a while before you see it.

-=-
Ok, I've posted the fix, now its up to the approval process. Sorry for the problem, alpha 32a3 should fix this.

@linusagren

The latest alpha (v32a2) crazed and devious skulls will no longer target NPC's. Otherwise the latest release only master and wizard skulls can be set to target specific mobs.

@CatchShadowCS

The Max firing range can only be a maximum of 1.0 which is 100% of the MaxRange. That is explained in the config and on the help pages here. If you want a longer firing range set a higher MaxRange in the config then the firing range will become larger too.