You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I execute a command such as /playsound beacon.activate @a 1 2 3 1 1
the resulting play_sound packet send by the server has completely different coordinates, after taking a look at some packets, I believe I have found the difference between the two
/playsound command coordinates
play_sound packet coordinates
1 2 3
12 16 28
1.5 2.5 3.5
12 20 28
0 0 0
4 0 4
1 1 1
12 8 12
0.5 0.5 0.5
4 4 4
0.5 0 0.5
4 0 4
0.25 0 0.25
2 0 2
0.125 0 0.125
1 0 1
0.1 0 0.1
0 0 0
0.124 0 0.124
0 0 0
this leads me to believe that normal coordinates are being converted as so:
If coordinate is whole number +.5 (except for Y)
Multiply coordinate by 8
Round down
Why does this happen?
Also, for some entity data packet that I have, the difference appears to be different:
It's not a problem with minecraft-data, it's a problem with the official packets. The exact reason for the creation of this feature is beyond my knowledge.
When I execute a command such as
/playsound beacon.activate @a 1 2 3 1 1
the resulting play_sound packet send by the server has completely different coordinates, after taking a look at some packets, I believe I have found the difference between the two
this leads me to believe that normal coordinates are being converted as so:
Why does this happen?
Also, for some entity data packet that I have, the difference appears to be different:
Note: the level_sound_event packet does give the correct coordinates
The text was updated successfully, but these errors were encountered: