#GetXPos / SetXPos are not working properly.

1 messages · Page 1 of 1 (latest)

tepid rock
#

SetXPos and GetXPos don't seem to be using the same axis of where they are based from. This leads to issues when trying to save an old custominfo position, and setting it as the new position.

Expected behavior:

  1. Use SetXPos on a custominfo to 0.5
  2. GetXPos on same custominfo returns 0.5

Actual behavior:

  1. Using SetXPos on a custominfo to 0.5 (Moves custominfo to 0.4)
  2. GetXPos on same custominfo returns 0.4

I can send a map showcasing this bug through dms.

lyric jasperBOT
#
Thank you for reporting a bug

Please make sure your report contains all required information to quickly reproduce this issue!
If you see this and noticed a similar problem, feel free to provide additional information.

#
⬜ Open
near meteor
#

Thanks for the detailed report 👍

lyric jasperBOT
#
🟦 Fixed - Pending Release