MC-140046When the vindicators are destroying the door, they don't raise their axe and facing the door
When the vindicators are destroying the door, they don't raise their axe and facing the door.
Linked Issues
LowAttachments1
![[Mod] Les3awe](../../../data/avatars/users/79847.png){kind=small}
Created Issue:
When the vindicators are destroying the door, they don't raise their axe and facing the door
When the vindicators are destroying the door, they don't raise their axe and facing the door.
Attachments1
![[Mod] Asteraoth](../../../data/avatars/users/92886.png){kind=small}
![[Mojang] Cory Scheviak](../../../data/avatars/users/92893.png){kind=small}
[Mojang] Cory Scheviakis duplicated by
![[Mojang] Nathan Adams](../../../data/assets/gravatar/dinnerbone.png){kind=small}
![[Mojang] Adrian Östergård](../../../data/assets/gravatar/nighter.jpeg){kind=small}
![[Mod] violine1101](../../../data/avatars/users/92858.png){kind=small}
relates to
relates to
is cloned by
relates to
vindicatorbreakingthedoor.png
Confirmed in 23w33a
Not sure if it's randomly selected which Vindicators just open them and which slowly break them with axes
I can't either because the Vindicators only open doors, and don't even break them
Still in 19w11a
Confirmed in 19w08b
Thank you for your report!
However, this issue is a Duplicate of MC-140046.
If you have additional information, please add it to that report.
Please search before reporting, as it's likely that one exists already.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – 📖 Game Wiki
Clones of MC-140046. Yes, the issue can still be reproduced.
When vindicators decide to break down doors instead of opening them, they do not visually break down a village door as they do not raise their axes (attacking animation).
Illagers can't destroy doors at all, according to
MC-139836.Yellow01, only vindicators can break doors.
Lol, I forgot to read in the comments that vindicators break doors on hard mode.
I can't seem to reproduce this issue.
If someone successfully reproduces this issue, please reply below and the issue will be reopened.
@Jon1337, this is now tracked at MC-182188.