-
Bug
-
Resolution: Fixed
-
Minecraft 1.8.8, Minecraft 15w44b, Minecraft 15w45a, Minecraft 16w35a, Minecraft 16w39c, Minecraft 1.11.2, Minecraft 17w06a, Minecraft 1.12, Minecraft 1.12.2, Minecraft 1.13-pre1, Minecraft 1.13-pre2, Minecraft 1.13-pre3, Minecraft 1.13-pre5, Minecraft 1.13, Minecraft 18w30b, Minecraft 18w31a, Minecraft 18w32a, Minecraft 18w33a, Minecraft 1.13.1-pre1, Minecraft 1.13.1, Minecraft 1.13.2, Minecraft 19w03c, Minecraft 19w04b, Minecraft 1.14 Pre-Release 2, Minecraft 1.14 Pre-Release 3, 1.15.2, 20w07a, 20w11a, 20w20b, 20w21a, 1.16 Pre-release 2, 20w46a, 21w03a, 1.16.5, 21w05b, 21w06a, 21w07a, 21w08b, 1.17.1, 1.18.1, 22w03a, 1.18.2, 22w11a, 22w12a, 1.19, 1.19.2, 22w42a
-
Confirmed
-
Commands, Mob behaviour
-
Low
The bug
Basically, if you summon a mob with a DeathTime tag under 20, everything works fine. The mob will disappear as soon as it hits 20 (it increments every tick). Example command for this:
/summon zombie ~ ~1 ~ {Health:0,DeathTime:19}
But, if you summon a mob with a DeathTime tag of 20 or more, the mob goes through the entire death animation, but that's not all. The world thinks the mob is still there even if the client doesn't think so. So you can't place blocks where the mobs were and they seem to be unloaded or something. Relogging causes them to reappear and go through the death animation again, but still exist. I don't know how to actually get rid of these "corrupt" mobs. Example command to trigger this (beware that there's not any confirmed method to get these mobs out of your world, so make a new one just in case):
/summon zombie ~ ~1 ~ {Health:0,DeathTime:20}
Code analysis
Code analysis by Marcono1234 can be found in this comment.
- is duplicated by
-
- Resolved
-
- Resolved
-
- Resolved
-
- Resolved
- relates to
-
- Open
-
- Resolved