When in F3 mode, the Block positioning will be off by 1 from the XYZ positioning (negatives only). This occurs as the Block positioning has no -0 number (as shown)
Linked issues
Attachments
Comments 4
It looks like it's rounding up for the negatives and rounding down for the positives.
Jar_ I'm not sure you understood what the OP was reporting. Or perhaps I did not.
But if you compare the positive and negative pictures, you'll notice that the block value for x is 1 less then the decimal coordinate shown above it. Contrary to the positive.
Take that Negative x Picture. Shows the player in the 0 block on the x at 0.699 yet the block shows a value of 1, contrary to displaying a 0 as it does for the positive integer.
Could see this being confusing for map makers that may use the wrong/incorrect value shown in the block location on the f3 debug screen.
This is not talking about the XYZ positioning in F3 mode, but the Block positioning (see underneath XYZ). I can understand why you got confused.
Duplicate of Works As Intended
Duplicate of MC-36602 - If you have not, please use the search function in the future, to see if your bug has already been submitted. If you could not find the original report, please comment with the keywords you searched for.
Works as intended.