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:
- Use SetXPos on a custominfo to 0.5
- GetXPos on same custominfo returns 0.5
Actual behavior:
- Using SetXPos on a custominfo to 0.5 (Moves custominfo to 0.4)
- GetXPos on same custominfo returns 0.4
I can send a map showcasing this bug through dms.