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
There is no issue with that - they are raw values, which are essentially only meaningful as a hex/bit pattern. The resolved values will map as expected.
for instance, those values in your screenshot decode to (20.98374, 21.0252), which in game is then truncated at one decimal to (20.9, 21.0) - exactly the location you specified
When the value of RawX and RawY are technically supposed to go into the negative, instead, since they are interpreted as uints, the value shoots up:
Steps to reproduce:
/e <pos>
and log the value of the produced MapLinkPayloadIs this a bug?
This was previously attempted to be fixed by #84.
The text was updated successfully, but these errors were encountered: