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

Packet 26 (EXP orb entity spawn) send/receive disparity

    • Icon: Bug Bug
    • Resolution: Duplicate
    • None
    • Minecraft 1.4.7, (8)
      Minecraft 1.5, Minecraft 1.5.1, Minecraft 1.5.2, Minecraft 1.6.2, Minecraft 13w38a, Minecraft 13w38b, Minecraft 13w38c, Minecraft 1.8
    • Community Consensus

      Packet 26, EXP orb spawn, sends the position of the exp orb multiplied by 32. However, the client receives it and does not divide the position by 32, meaning the server must send an entity teleport packet to the client to correct the exp orb's position.

      I suggest each of these packet classes have getters to ensure that the correct position is being used, rather than keeping the 'encoding' of the position inside the packet class then having the 'decoding' inexplicably take place elsewhere.

      This was found when attempting to debug a related issue, that when joining another person's server I was unable to target certain mobs and minecarts until they moved into another chunk (that is: I believe the issue to be with a modification they have made to their server software, but despite this I do not think the client should react in such a way).

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

          Packet 26 (EXP orb entity spawn) send/receive disparity

            • Icon: Bug Bug
            • Resolution: Duplicate
            • None
            • Minecraft 1.4.7, (8)
              Minecraft 1.5, Minecraft 1.5.1, Minecraft 1.5.2, Minecraft 1.6.2, Minecraft 13w38a, Minecraft 13w38b, Minecraft 13w38c, Minecraft 1.8
            • Community Consensus

              Packet 26, EXP orb spawn, sends the position of the exp orb multiplied by 32. However, the client receives it and does not divide the position by 32, meaning the server must send an entity teleport packet to the client to correct the exp orb's position.

              I suggest each of these packet classes have getters to ensure that the correct position is being used, rather than keeping the 'encoding' of the position inside the packet class then having the 'decoding' inexplicably take place elsewhere.

              This was found when attempting to debug a related issue, that when joining another person's server I was unable to target certain mobs and minecarts until they moved into another chunk (that is: I believe the issue to be with a modification they have made to their server software, but despite this I do not think the client should react in such a way).

                    Unassigned Unassigned
                    score_under score
                    Votes:
                    10 Vote for this issue
                    Watchers:
                    6 Start watching this issue

                      Created:
                      Updated:
                      Resolved:
                      CHK:

                        Unassigned Unassigned
                        score_under score
                        Votes:
                        10 Vote for this issue
                        Watchers:
                        6 Start watching this issue

                          Created:
                          Updated:
                          Resolved:
                          CHK: