The x coordinate that they appear at is always the same as their y coordinate. So the code that displays them must be reading their y coordinate when figuring out what x coordinate to render them at.
Ah, I see now. I guess I should just use a fill instead like "/execute @p ~ ~ ~ fill ~ ~-1 ~ ~ ~-1 ~ planks 0 replace dirt". Thanks
I can confirm that this happens also in creative mode, and to most blocks (not all were tested).
I am having the same issue. Using NBTExplorer, I noted that my coordinates were at -92, 114, -9. I think that this issue may be related to the positioning of the player, but I'm not sure.
EDIT: Using NBTExplorer to change my coordinates did nothing, after checking again, they were back to the original coordinates.
@Kumasasa I see how the original bug report escaped my searching. At least it was marked as the right duplicate this time. Additionally, I am sorry for creating another issue, as I was unsure whether issues could be reopened.
If this is not unmarked, then I will probably make a new report with additional information pertaining to why this is not a duplicate of MC-13661.
@Talven81 This is not a duplicate of MC-13661. I haven't changed the window resolution at all when this happens. I get the Mojang screen, and then this happens. Note that the title screen for MC-13661 has normal length-width proportions, that of the default window size. This time, the (visual) title screen is in a square, and not the right length-width proportions. I believe MC-13661 is for most recent versions, while this only happens with 13w38a.
I also did use the search function with "13w38a screen resolution title screen", and I got no results.
They can also spawn in trees and get stuck- this is notable in the large oak trees where they spawn on top of a log and get stuck in the leaves