Skeletons with no AI spawning naturally

I've seen this in 15w44a.
I did not need to fight any skeletons, just after a day or so a skeleton would spawn and just stands there until I reload the game. I can hit it once, after that I cannot touch it anymore

Can you inspect the NBT data of the skeleton (for example by using the command below) and provide the result here?

/entitydata @e[type=Skeleton,c=1] {}

I did the command and everythings normal

Confirmed.

@unknown: Do you have a reliable way to reproduce?

I just in the world getting around. 🙂
It seems little chance of reproduction.

• crash-reports

I've had this happen - not with a skeleton trap though, just a regular skeleton.

Haven't had much time to play lately but I did just jump into spectator mode to see if I could see anything.
No mineshafts or spawners anywhere near the village and everything else seems fine.
I did place a ton of torches around the village and the no ai skeletons stopped spawning.
I'll remove the torches when I get time and see if they reappear.

I definitely see it in normal survival mode without doing anything related. Just after a few nights (1-3) I see a skeleton or 2 standing in sunlight without moving. Ideally you should be on a big open area. I tried it on a world created with 15w43c, playing the latest snapshot 15w44a (I have no idea, if it matters, when you created the world)

Happens in my world as well on a multiplayer server running 15w43c. Restarting the server gets rid of them, but otherwise they won't despawn.

Added a screen shot of the entity data of a no ai skeleton.
Looks normal to me.

Reproduceable -
Started a standard superflat in 15w44b in creative mode using "hello" as the seed (if that matters) and let it sit there while doing nothing for about 40 minutes.
I then flew around and found 2 no ai skeletons.

at lest 15w44b and latter.

Apparently a failed normal monster spawn.

Stands still with bow pointing down and with no reactions.

Each glitched skeleton can be hit just once.
For sure after 1st hit it is like they are in spectator mode.
Have yet to test before 1st hit.
Will ignore all environmental effects

Immune to full sunlight or stand in block of lava and will takes no damage.

Moved more than 16 chunks away then return and glitched skeletons were gone.

Confirmed in fresh 45a world.

[s]Still seeing these appearing in 15w46a. I have been leaving the game running through the night and there are three or four of these skeletons sitting out in my yard./s

I retract my last statement. It was in a world created in an earlier snapshot. I ran an extended test in a fresh world and let many skeletons spawn naturally but none were bugged.

I saw this in worlds created in 15w46a. Have not tried w47 yet.

I have seen this in 15w47a today

Eric Dewey, what version was your world created in?

Reaver - the world was created in w47a iirc

I just found a bugged skeleton.
Active snapshot: 15w47b
World generated in: 15w46a
Chunks generated in: 15w46a

Screenshot attached.

Saw this today in a world generated in 15w47b. Note that switching to peaceful does not make the skeleton go away. Logging out and back in does cause the skeleton to disappear.

Confirmed for 15w47c

No AI Skeleton can only be killed by blast attack.
I probably know how to easy reproduce this issue / BUG.

@@unknown:

I probably know how to reproduce this issue / BUG.

...how?!

Reproduce video:
https://www.youtube.com/watch?v=UgiTzg2jr_A

I think this BUG is because the MC-93136
But the skeleton did not successfully death.

That is a tangential effect of the bug. These bugged skeletons can spawn on any difficulty, perhaps even peaceful. They might simply be more noticeable on peaceful because every hostile mob that isn't bugged gets instantly deleted while the bugged skeletons are not deleted by peaceful mode's automatic mob deletion cycle.

No AI Skeleton death will be repeated death animation.
Link: MC-93136

Confirmed on a world generated in 15w47c.

The skeleton spawning is spawning client side when it should be spawning server side. It is like a client side slime bug. That is the reason because the skeleton doesn't do stuff and doesn't surn during day. Skeletons with no AI can still burn because that is on their onUpdate code not being blocked by the NoAI tag.

I noted they can be hit twice if you switch from sword to axe. On another occasion i was able to kill one with a creeper explosion after hitting it once.
EDIT: This happened in multiplayer and both of us could see the affected mobs.

i experience the same problem of skeletons bug

I first noticed it when messing around with spider spawners I made. TONS OF THEM SPAWN!!! They also appear in my mob farm.

Confirmed for

• 15w49b With the method provided in the video, the difficulty does not matter, it must however be at least one where monsters can spawn. I assume that the isDead field is set to true, however the entity is not removed from the entity list (if something like this exists).

Confirm this, running 15w47c. in addition, I noticed something: they can only be hit once, but if you hit them with an OP enchanted one-shoting weapon, they do die normally. after they have been hit once though, if they are not dead no amount of enchantments make a difference.

I'm playing the latest snapshot 15w49b and this still happens. Strangely enough, I have also only seen this happen in a plains biome, however there is usually not a village in immediate view, preferably tending to spawn near the original and bed spawns.

Just like described, however, these skeletons spawn with seemingly little to no AI. They do not make idle sounds, won't move or attack, can only be struck the first time, and will only respond with striking noises (the new sound effect when you strike something) subsequent times.

That is very strange. Wonder why... so weird. You can use the /kill command. If the command worked, then run it whenever you see it.

This also happens when spider jockeys are about to spawn. Rarely spider jockeys CAN SPAWN!!! This can also happen if there are skeleton or spider spawners.

So that is why. I tried that and you can remove them by relogging. So they are removed.

Confirmed for 15w50a

I found one spawned in a acacia biome too.

Confirmed in 15w51b.
Oh darn. So that guy's going to respawn every night?

So far I've found there's three ways to kill them:
1. Relogging
2. Moving 16 chunks away, then moving back
3. Using /kill @e[type=Skeleton]
Hope this helps to get rid of them until this is noticed.

Confirmed.
Sometimes you can even hit it once, but then it just stands there.

2. Moving 16 chunks away, then moving back.

It's your render distance, turn it to 2 chunks then turn it back.

Found many of these. Confirmed.

Fixed? I have not been able to reproduce this in a world created in and played in 16w02a (both in a couple hours of normal survival, as well as some attempt-to-reproduce-it via night-time superflat cycling of /difficulty).

No new duplicates either. Anybody else able to confirm fix?

Confirmed for 16w02a.

Les, was the world created prior to 16w02a or in 16w02a?

World created in 16w02a

Confirmed not fixed for 16w03a, world created in 16w03a.

It's still happening in 16w04a. I wait through the night in my shelter, come out, and 3 skeletons were standing around in broad daylight frozen in place. I could attack them once and then nothing. They won't even fall if the block under them is removed.

Edit: I'm on Windows 10 x64 using the latest version of Java.

My Wolf tried to attack a ghost Skeleton and had to lead it away with a lead to get it to stop.

Can you confirm this is still happening in 16w04a with a fresh world ?
There was some bugs in the ridding code that might have been the source of this bug and it has been solved as of 16w04a.

I can confirm that this is still happening in snapshot 16w04a, in a world created in said snapshot.

I can confirm this with a new world for 16w04a as well

Confirmed in a new 16w04a world.

Is this still a problem in 16w05a?

Confirmed for 16w05a

confirmed for 16w05b

Confirmed for 16w04a

@unknown: 16w04a is outdated.

Confirmed still happens in snapshot 16w06a, world created in same.

It should also be stated that you can usually hit these skeletons once or twice, then they become unhittable. Also, if you remove the blocks below them, they just float there.

Just had it happen in 16w06a, skeleton disappeared after I closed and re-opened the world.

added screenshot of dogs confused by the no-AI skeleton - essentially stuck there until a world reload.

Are you sure it has NoAI:1b? I'm not sure, as I think they're just just spawning on the client and not the server...

By the way, use a Smite V axe. It kills them! 😃
At least in 15w50a!

They spawn on the server, every player sees them, all mobs see them, wolfs try to kill them, iron golems attack them, and snow golems defend you from them.
If it was on the client side, none of these would would be there

Just seen this in 16w07b, on my own private SMP dedicated server. (16w07b on both client and server).

I approached the skeleton from behind and it didn't move as I approached it. I struck it once with my sword, it didn't move, and I can't hit it again. It's just standing idle in my world, with arms slightly waving. I disconnected from the server, and reconnected, and the frozen skeleton was still there, after connecting again, I still couldn't hit it again.

I've tried hitting it with everything in my inventory, and have dropped water, but the skeleton isn't affected. If I attempt to remove blocks from below it, the skeleton just floats in the same place.

I am seeing bugged-out skeletons as well. They are all over my world. Its a brand new 16w07b world. Not only do they just stand there but they don't burn in sunlight either. I can hit them and they register a hit one time and then they don't register hits any more either. I can't kill them. Ugh.

I see a 1.9 pre-release is out and this bug is not on the fixed list. Will this be fixed before next week??? I got these frozen skeletons all over the place.

Is this bug really fixed? Please someone confirm sth.