Uploaded image for project: 'Minecraft: Java Edition'
  1. Minecraft: Java Edition
  2. MC-58512

Multiplayer: Entity Rendering weird while using player heads / spawned mobs with player heads

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Minecraft 14w30c
    • Minecraft 14w25b, Minecraft 14w26c, Minecraft 14w28b, Minecraft 14w30b
    • None
    • Confirmed

      In Multiplayer, spawning a Zombie with custom head, such as with the command:

      /summon Zombie ~ ~ ~ {Equipment:[{},{},{},{},{Damage:3,id:397,tag:{SkullOwner:Dinnerbone}}]}
      

      will result in surrounding entities being rendered incorrectly, and will rotate and move about the Zombie (when it moves).
      Any 'SkullOwner' (real player or fake) will have this result. Spawning a zombie without the tag on the skull will spawn a normal zombie (with a Steve head) with no issues.
      The presence of other equipment on the zombie has no effect, and none of them seem to appear on the mob (including the skull).

      Also, if you deal damage to the 'glitched' zombie, it will cause your screen to turn red, similar to the death screen. This will stick with the player until their client is restarted, or they deal damage to another mob (other than the glitched zombie).

      To test this yourself:
      -Spawn a zombie wearing custom player head in an area with other entities and signs around.
      -Hit the zombie.
      -Hit another mob to resolve the red screen.

      If anybody else could confirm I am not crazy and this is an issue, that would be great.

      Thanks

        1. 2014-06-29_10.05.14.png
          400 kB
          Kumasasa
        2. 2014-06-29_10.05.52.png
          262 kB
          Kumasasa
        3. 2014-07-14_20.27.25.png
          700 kB
          J
        4. 2014-07-14_20.27.40.png
          403 kB
          J

            searge [Mojang] Searge (Michael Stoyke)
            justanotherjoe1 Adrian S
            Votes:
            5 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved:
              CHK: