Enderman renders as holding the block (during death animation), even though he already dropped the block
Recently,
Endermen have been coded to drop the block they are holding when killed. But they still render as if they are holding the block when they die (even though the block has already been dropped as an item).
What is expected:
Endermens' hand is empty when they die/drop the block.
What happens:
Endermens' hand is still holding the block though the block has been dropped as an item.
Note
This all happens when an enderman dies.
Created Issue:
Enderman Renders as holding the block (during death animation), even though he already dropped the block
Recently,
Endermen have been coded to drop the block they are holding when killed. But they still render as if they are holding the block when they die (even though the block has already been dropped as an item).What is expected:
Endermens' hand is empty when they die/drop the block.What happens:
Endermens' hand is still holding the block though the block has been dropped as an item.Note
This all happens when an enderman dies.
relates to
EndermanRenders as holding the block (during death animation), even though he already dropped the blockEnderman renders as holding the block (during death animation), even though he already dropped the block
Relates to MCPE-30144
The bug
MC-135164 was not fully fixed. It is indeed fixed for other mobs holding items, however it is not fixed for endermen holding blocks. If you kill an enderman, it still holds the block during the death animation even though the enderman just dropped it, leading to visiual duplication. Endermen hold actual blocks, not items, that’s probably why it isn’t fixed for them. Also relates to MCPE-30144.
How to reproduce:
/summon enderman ~ ~ ~ {CanPickUpLoot:1b,Health:1f,carriedBlockState:{Name:"minecraft:dirt"}}- Hit it to kill it
You still see how it holds the dirt block, even though the enderman already dropped it.


Confirmed on Windows 10 1.2.8.0.
Thank you for your report!
However, this issue has been closed as Working as Intended.
This can also be observed in the Java edition. If you would like to make a suggestion you might like to follow a link below.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Feedback – 📖 Game Wiki
Just because a bug is also present in the Java Edition doesn't make it any less of a bug?
The Java Edition ticket is
MC-135164Reopened for review.
Finally I was able to capture this! It took so long! Exists in 1.14.60.
Thank you for your report!
However, this issue has been temporarily closed as Awaiting Response
Is this still an issue in the latest version?
If it is, please be sure to include steps to reproduce the problem:
If your ticket does not look like the example given here, then it's likely to be closed as incomplete.
This ticket will automatically reopen when you reply.
Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki
Still an issue in 1.16.210.54 Beta.
Thank you for your report!
However, this issue has been temporarily closed as Awaiting Response
Is this still an issue in the latest version? If so, please add a comment or update the affected version field.
To make your bug report as effective as possible, please try and include the following steps to reproduce the problem:
If your ticket does not look like the example given here, then it's likely to be closed as incomplete.
This ticket will automatically reopen when you reply.
Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki
Still a problem