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

De-synchronized, glitchy jockey after spider death

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • None
    • Minecraft 1.4.2
    • None
    • Windows 7, Java 1.7.0_09
    • Unconfirmed

      Two similar but different situations occur depending on whether you're in Survival or Creative.

      Expectation:
      For the jockey to become a regular skeleton upon death of the spider.

      Occurrence:
      Creative:
      After killing the spider the jockey glitches through the floor. His hitbox is still with the model and the arrows come from relatively the same area as well. Once, the model was out of sync about 7 blocks from the hitbox and the arrows shooting.

      Survival:
      After killing the spider the jockey appears to glitch through the floor, but becomes invisible. While testing I saw two skeletons glitched through the ground about 25 blocks away from where the jockey was killed. They were invincible and didn't attack. The skeleton ended up falling into a creeper hole at which point he became visible and attack-able.
      The invisible jockey's arrows were visible and did damage. When testing a spider was hit and the spider attacked the jockey and did damage (the noise was heard).

        1. Glitched skeleton model (survival).png
          235 kB
          Jeremy Dreyer
        2. Jockey floating before glitching (creative).png
          164 kB
          Jeremy Dreyer
        3. Jockey in floor (creative).png
          337 kB
          Jeremy Dreyer
        4. Out of sync skeleton.png
          293 kB
          Jeremy Dreyer
        5. Out of sync skeleton inside ground (creative).png
          343 kB
          Jeremy Dreyer
        6. Spider attacking invisible jockey (survival).png
          191 kB
          Jeremy Dreyer

            Unassigned Unassigned
            dotzo Jeremy Dreyer
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: