[MC-11601] Packet 26 (EXP orb entity spawn) send/receive disparity Created: 12/Mar/13 Updated: 14/Feb/16 Resolved: 14/Feb/16 |
|
| Status: | Resolved |
| Project: | Minecraft: Java Edition |
| Component/s: | None |
| Affects Version/s: | Minecraft 1.4.7, Minecraft 1.5, Minecraft 1.5.1, Minecraft 1.5.2, Minecraft 1.6.2, Minecraft 13w38a, Minecraft 13w38b, Minecraft 13w38c, Minecraft 1.8 |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | score | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 10 |
| Labels: | entity, experience, packets | ||
| Issue Links: |
|
||||||||||||||||
| CHK: | |||||||||||||||||
| Confirmation Status: | Community Consensus | ||||||||||||||||
| Description |
|
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). |
| Comments |
| Comment by williewillus [ 13/Feb/16 ] |
|
This was fixed a long time ago... yup |
| Comment by Marcono1234 [ 12/Feb/16 ] |
|
Can very likely not confirm for 16w06a In 16w06a the net.minecraft.client.network.NetHandlerPlayClient is bkq.class and net.minecraft.network.play.server.S11PacketSpawnExperienceOrb is fk.class. While there is still no conversion back, it looks as if the coordinates are also not multiplied with 32.0D anymore. |
| Comment by Emoluvjd2 [ 11/Feb/16 ] |
|
Does this affect the most recent snapshot? |
| Comment by williewillus [ 02/Sep/14 ] |
|
Affects all versions up to and including release 1.8 |
| Comment by Deleted account [ 25/May/14 ] |
|
Is this still a concern in the current Minecraft version 14w21b / Launcher version 1.4.4 or later? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases. |
| Comment by Deleted account [ 23/Mar/14 ] |
|
Is this still a concern in the current Minecraft version 14w11b / Launcher version *1.3.11 or later? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases. |
| Comment by Talven81 [ 26/Nov/13 ] |
|
Is this still a concern in the current Minecraft version 1.7.4 / Launcher version 1.3.8 or later? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases. |
| Comment by williewillus [ 23/Sep/13 ] |
|
Still affects all current versions (13w38c and beyond) |
| Comment by score [ 12/Mar/13 ] |
|
As far as I'm aware It is frankly dumb luck that XP orbs (usually) aren't invisible for the first second after spawning: the only reason the position is corrected clientside so fast is because there's a special exception given in the entity tracker stating that all entities which have only just changed velocity should be updated to all clients as fast as possible. |
| Comment by Anon Ymus [ 12/Mar/13 ] |
|
Cause of |