The hitbox of some blocks (chests, anvils) are not correctly registered and you can get stuck, or at least trigger a client/server desync while walking/jumping into sides of those blocks.
Steps to reproduce changed with the updates, but the glitch still exists. Here is a detailed explanation :
http://www.youtube.com/watch?v=y1kon5Wax8I
Steps to reproduce :
Place 2 double chests
Walk in the corner and slowly look at the other chest while walking
https://www.youtube.com/watch?v=p-8G_R8tLr4
Related issues
is duplicated by
relates to
Attachments
Comments


You can reproduce the problem by looking at the near side of the chest, walking forward until you're touching it, then looking at the far side of the chest and moving forward. If you look at the far side while you are first walking forward, you'll notice that when you look at the near side you can actually walk forward a bit more.
You can also walk through them by arranging them like
##
#O
where # is a chest and O is you, walking into the corner, and looking back and forth between the chests in the corner. It's easier if the chests are eye level, and just as possible with them stacked two high.
This also works in survival, and can be used to reproduce MC-1749.

The Minecraft Team could fix this real easy. Instead of render update --> set global block bounds, get collision box --> return global block bounds change it to get collision box --> return changed block bounds.
Just change the global block bounds to a block bounds for each bock.

Happens to me but i dont mind



It's because both things happen The first reporter reported both the "stuck" part and the jerky movement part while the second one only reported the "stuttering" movement which happens when pressing movement keys. When this happens you are actually stuck because normally when pressing a movement key you should be able to move.

A different but similar issue is happening in the 1.5 pre where I can just walk into the chest I'm going to post a scene shot of me doing this. The method I took to achieve this is as follows
Place two double chests on top of one another.
Place a sign one the front of the two chests.
Place a dog at a angle
walk into sign side keeping crossbar on the dog
Result is shown by screenshot

My screenshots

Can confirm in 13w11a, not personnaly happened with me, but with my dogs... Added two screenshots with my dogs stuck... They're stuck in chests when sitting, when standing they can walk out of them. Anvil in my toolbar was between chests, maybe it happened because anvil was there. idk. =D

i have even seen mobs getting stuck in chests. even on youtube, i found a cat getting stuck inside a chest

Very annoying bug indeed ๐
Please fix it Mojang.

Is this still a concern in the current Minecraft version 1.6.4 / Launcher version 1.2.5 ? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.

Still in 1.7.2

Still in 1.7.4

Seems much reduced in 14w02c but still partially reproducible with anvils.

http://www.youtube.com/watch?v=p-8G_R8tLr4
I have made a video showin how to consistently recreate this issue.
First you start walking against the chest,
then you look at any chest, you should start jittering,
then look away from the chest, you should have gone through
Tested in 14w04b

Still confirmed for 14w19a

Still affects 1.7.10 & 14w26c, but the glitch is now rarely triggered by the player. Updated steps to reproduce.

Still exists in 14w27b.

Still exists in 14w28b.

Still exists in 14w29b.

Still exists in 14w31a.

Still exists in 14w32a.

Still exists in 14w34b.

Still exists in 14w34d.

still exists in 1.8

Still exists in 1.8.1.

Why is this only marked as โrelates to MC-73302โ? It should be closed as duplicate.

Fenhl, this one talks about broken hitboxes. That one talks about mobs glitching through blocks.

No, Fenhl is right. MC-73302 is about a bad piece of code which causes this and a lot of other bugs.

@Sonic The 'broken hitbox' this ticket is stating is basically same thing as MC-73302

This one has more votes though and is 2 years older (making it easier/more "importance" for Mojang to see). Perhaps copy parts of that description to this one? (since that one is rather long)

Still exists in 1.8.2 pre1.

Still exists in 1.8.3.

Still exists in 1.8.4.

I found a solid way to reproduce this and at least a starting point to look for the bug(s).
Walk up to a side of a double chest. Carefully tune your up/down viewing angle.
When angle is between 90 and 31.1, the hitbox starts at X.238 (โ3.8/16)
When angle is between -90 and 29.9, the hitbox starts at X.300 (=4.8/16)
When angle is between 29.9 and 31.1, you get stuck as the client and server disagree
Of course, when already at X.238, looking in any angle above 31.1 gets you stuck.
Sometimes, when the angle is between -90 and 27.1, the hitbox starts at X.238. I don't know what causes this. As soon as you get stuck, the hitbox resets to 0.300 for those angles.
With this, I suspect there are at least thrree bugs contributing to this:
Hitbox size typo in one of the two places where it's defined,
Angle-dependency that shouldn't exist,
The client/server disagreement.
I suggest not immediate fixing the first bug (if is's correct), because that would mask the other bugs.

@@unknown Try not to edit comments that much, it sends an email to everyone who's following this issue.

Still exists in 1.8.5.

Affects 1.8.8.

Still exists in 15w36c.

Still exists on 15w37a.