When you interrupt a zombie while they are attempting to break down a door, the "cracked" effect remains even if the door is later removed. This issue doesn't always occur.
What I expected to happen was...:
After killing or interrupting a zombie attempting to break down a door, the damage indicator or "cracked" effect should disappear.
What actually happened was...:
Instead, the damage indicator or "cracked" effect sometimes remain behind, even if the door is removed. It just seems to float in the air.
Steps to Reproduce:
1. Find a village and wait for zombies to try and break down any door.
2. Stop the zombie or kill the zombie.
3. The "cracked" effect on the door is still showing when it shouldn't, even if the door is removed.
Screenshots:
[media]Screenshots courtesy of the Minecraft Wiki
Linked issues
is duplicated by 15
MC-203
"In-destroying" animation bloc
Resolved
MC-1575
When a zombie hits a door and kill the zombie, the door is half broken, and if you break it in creative, the crack is in the air
Resolved
MC-1943
when a zombie is destroying a door and you break it for him, the breaking animation floats in mid air.
Resolved
MC-2398
When you kill a zombie breaking down a door, the crack remains
Resolved
MC-4814
block cracks when two people mine it
Resolved
Attachments
Comments 11
Same here!! i happen to live in a village in my co-op server and every night zombies siege us and we get the cracked door effect...I figured if u restart ur game (single player) or if u restart ur sever(multiplayer) it is fixed 😃
Another bug related to this... mojang.atlassian.net/browse/MC-203
The first ticket on a bug tracker serves many purposes. Generally a very visible ticket is created so it can trap all subsequent tickets (see the dupes linked). As well, it helps test the system as it goes live. Plus, it allows an easy place to collect information about the ticket.
Thank you for your question Rhys.
On top of what TnT already said:
I made this ticket to serve as an example of the kind of tickets we want, despite knowing this bug had already been fixed by us. Note how I direct people to this ticket in our "Writing useful bug reports" guide.
I experienced this bug in 1.3.2 as well. Although I did have a few mods installed. So they may have been the culprit.