What I expected to happen was: The spider would stay up against the ceiling.
What actually happened was: The spider appeared to drift down and could not be hit.
The spider starts to track the player and climbs up the wall. After the spider climbs up to the ceiling, it will sometimes seem to drift down while frozen, but it is not able to be attacked or moved through an opening in the wall. It will then snap back to its original position against the ceiling, and the process randomly repeats.
This only occurs when the player cannot directly see the spot against the ceiling where the spider is supposed to be.
To reproduce:
1. Build the wall seen in the photo, with a lip (acting as a ceiling) on one side.
2. Stand on the side without the lip.
3. On the other side the doorway, spawn a spider.
4. Attack it to make it track you.
5. When it moves down from the lip, attempt to hit it.
Linked issues
is duplicated by 4
relates to 3
Attachments
Comments 15
Yep. I can confirm this bug, same here.
But i think, in 1.4.2 it is a bit better than in 1.3.2.
I experienced this bug a lot in my SSP World in 1.3.2 ^^
Still an issue in 1.7.2, creating lots of frustration and futile button-mashing whenever encountering spiders. Can't test for 1.7.4 cuz it's so broken I just can't stand to use it anymore.
Cannot reproduce in 1.10.2. The spider walks around the wall (in the screenshot), and if I trap it in a box with 1-wide holes, the issue still doesn't occur.
Resolved? Give me a break. Break some bookshelves in a stronghold that has a lot of cobwebs. That'll reproduce it. If that still doesn't work, do it in a Java Realm.
I could, but with my Internet speeds that grain of "proof" would be online after 3 times as much effort as anybody else who can break bookshelves in a stronghold room. Anybody who has Minecraft and is reading this - I dare you to slow down the ping slightly and throw items just on the edge of cobwebs. The game seems to think that items are simultaneously on and not on cobwebs and tries to make up for its embarrassing confusion.
That's not what this report is about, you're talking about MC-4. And yes, that one still exists and is already confirmed for every version imaginable. And before you comment there: No, it will probably not be fixed soon, because the only good solutions found so far create more data to be sent and therefore make bad connections worse.
Isn't this due to the client not receiving mob updates from the emulated server so assuming it has fallen? This bug similarly affects other mobs with wandering through fences and such!