I was on this world on creative mode and I managed to get an exp orb in the void. I expected it to disintegrate, like other entities, but exp orbs don’t.
How to reproduce:
On a flat world, dig a hole until you get to the void.
Summon an exp orb in any way near the hole.
Lure the exp orb into the hole.
When the exp orb is on the block of stone, fly up and break it.
Expected results: The exp orb disintegrates in the void.
Observed results: It doesn’t disintegrate in the void.
Related issues
Attachments
Comments
migrated
GoldenHelmet
I am not able to reproduce this in 1.16.40.
GoldenHelmet
@leo190: based on your recent edit after I resolved this report, what you are experiencing is the same bug as MCPE-11181. When an orb is moving toward you and you move away quickly, the client and server data on the orb's position desync. The orb you see floating in the void is the client-side, rendered orb. If fly down to it from a different direction, you will find that it cannot be picked up. If reload the world, you will find that it no longer appears in the void, and instead it appears wherever the server-side orb was located. The same thing can happen with orbs in lava, where it appears that an orb is not being destroyed by lava.
Since what you're reporting has the same cause as MCPE-11181, there is no need to track it separately. I will, instead, re-resolve this report as a duplicate.
migrated
Ok. So the bug is that the sever side of the orb disappears when a player runs away from it, but the client side remains, which is the part you can see? And is the client side the thing that moves? I still don’t get how this is a duplicate of MCPE-11181.
GoldenHelmet
The client-side orb moves toward you faster than the server-side orb (maybe b/c there's a delay in the server updating the player's position, MCPE-65094) and they desync. The client-side orb can't be destroyed in the void for the same reason it can't be picked up and hovers around you: the server locates the orb at a different place so it doesn't call or confirm the function for those events.
Again, try relogging while looking at a client-side orb that's in the void. When you relog, you should find that the orb no longer appears in the void but instead reappears wherever the server thought it was located.
migrated
Ok.