#goto negative coords off by one error
fw4hre0xxq opened this issue ยท 4 comments
Some information
Operating system: Win 10 Pro x64
Java version:
openjdk version "1.8.0_242"
OpenJDK Runtime Environment Corretto-8.242.08.1 (build 1.8.0_242-b08)
OpenJDK 64-Bit Server VM Corretto-8.242.08.1 (build 25.242-b08, mixed mode)
Minecraft version: 1.12.2
Baritone version: baritone-standalone-forge-1.2.11
Forge mods (if used): Just Forge, no mods
Exception, error or logs
Please find your latest.log
or debug.log
in this folder and attach it to the issue
Linux: ~/.minecraft/logs/
Windows: %appdata%/.minecraft/logs/
Mac: /Library/Application\ Support/minecraft/logs/
How to reproduce
- Create a brand new 1.12.2 install (I used MultiMC).
- Teleport around until you find negative coordinates on land.
- Issue a #goto command with two arguments (the X and Z coordinates) with at least one of them being negative.
- Observe. Expected behavior is that when Baritone stops moving, if the coordinates specified in step 3 are e.g. -100 -100, the F3 screen will show -100 -100. Actual behavior is that F3 reads -99 -99. When one coordinate is negative and one is postitive, only the negative coordinate will be effected. When the coordinates are -0 -0 the F3 screen shows 0 0.
This
Final checklist
- I know how to properly use check boxes
- I have included the version of Minecraft I'm running, baritone's version and forge mods (if used).
- I have included logs, exceptions and / or steps to reproduce the issue.
- I have not used any OwO's or UwU's in this issue.
Thoughts: Is it possible that Baritone isn't accounting for Minecraft having a negative zero?
Possibly related to #1364