Only tested in SMP.
What I expected to happen was...:
Running against an anvil (actually to jump on it 😃)
What actually happened was...:
I was pushed back and forward while running forward.
Steps to Reproduce:
1. Place an anvil (in front of a wall)
2. run against it.
3. Be pushed back. (Looks laggy and a bit like suffocating in the anvil).
Explanation of the bug in this video: http://www.youtube.com/watch?v=y1kon5Wax8I&feature=youtu.be
Related issues
duplicates
is duplicated by
MC-1888
When walking into a anvil character or screen spazing out
MC-2263
Anvil: Cannot strafe along the front or run diagonally against
MC-2560
Walking though anvils
MC-2890
Walking into anvil
MC-3978
Anvil - hitbox/collision problem
MC-4850
Anvil on half slab
MC-4898
Glitchy Anvil hitbox
MC-5257
Anvil
MC-7281
Hitbox of an anvil is different between the server and the client
MC-7468
Anvil colision bug while flying/falling
MC-7629
Hitboxes of blocks with orientation dependend placement are broken.
MC-10076
Walking around anvil edges
MC-17386
Anvil bug: When you go to close to anvil, it's kinda sticks u to it.
MC-25541
Able to walk through non-parallel anvils!
MC-26000
Walk through anvil
MC-30924
anvil collision box error
MC-36424
Anvils/chest(any non-block entity) collision server-check bugs(Netty?)
MC-47359
Anvil clipping bug
MC-55327
Players and mobs can clip through anvils by "rubbing" against them
MC-58498
Anvils are glitchy
MC-66595
Anvils are glitchy
MC-70934
Walking between two anvils causes you to get inside of them.
MC-72226
Possible to walk IN anvils
MC-72495
Anvil Door
MC-79300
Walking through anvils
Attachments
Comments
migrated
migrated
Tested in Multiplayer there (1.4.3 pre-release)
Bug comfirmed : collision bug when running into the anvil (little knockback)
collision bug when : force walking into the anvil, then moving left or right -> being stuck with a spazzing knock back until we stop moving in that direction
Solo mode : seems to have no bug with collision.
migrated
Same thing happens for me on my Linux server with an OSX and Windows client. (1.4.3 Pre-release)
migrated
This will also happen in 1.4.4 pre-release.
Comfirmed.
kumasasa
Confirmed in Multiplayer, not happening in Singleplayer
migrated
I have seen this bug when walking into any non-solid block. Fences and doors can do the same thing.
migrated
I also have this problem, you'll start vibrate when walking into the long sides of them. So you can't pass by it walking against the long sides of them.
migrated
Confirmed in snapshot: 13w07a Multi-player.
shufboyardee
1.5 as well.
migrated
I believe I have found a serious issue related to this bug. A quick search through the issue tracker revealed my worst fears: Anvils can be decorporealized at will. I have uploaded a series of four images describing the process.
migrated
Confirmed in 1.5 release and snapshot 13w11a.
migrated
Confirmed in 1.5.1 tough
migrated
Confirmed in 1.5.1, just tried it out on my flat world.
migrated
I think this is caused by unsynced width of anvil block in singleplayer and server files. Thus, playing in SP is ok, but server thinks that anvil is wider than client knows, pushing player back when updating his position. So the fix would probably be changing anvil's hitbox in server files.
migrated
This needs to be updated for 1.6.2 as it is still an issue.
migrated
Anvil and chest have exactly same hitbox bug.
Confirmed in 1.6.2 both with anvil and a chest.
migrated
Still happens in 1.7.2. Just make a simple cube hitbox like the old fence had.
migrated
Verified still happens on 1.7.4.
shufboyardee
does this still happen in SMP in the 1.8 snapshots?
kumasasa
in 14w08a the push back effect is gone, but can still walk through anvils as shown in the screenshots, but that's maybe another issue.
migrated
The four screenshots I originally posted are invalid. The real cause is looking at an anvil facing the other direction, not turning. The hitboxes of all anvils is set to the last one you looked at. The same thing happens with double chests, but the difference isn't big enough to let you pass through completely, which if I'm not mistaken, makes this issue a duplicate.
Sonicwave
Still an issue in 1.8.1-pre2.
migrated
Still happening in 1.8.2-pre1
migrated
Why is this not a duplicate of MC-1635?
migrated
I believe this is a duplicate of MC-1635.