If try to place a piston past 16777217 (or -16777217) facing upwards, it is very difficult to place it upward in certain places. Along the x 16777217 (and subsequent lines) moving north/south, it is possible to place upward in strange ways, and also along the z 16777217 line and subsequent. I have not been able to figure out how to place it every time yet, although it seems to be related to the South/East direction.
Happens both in Survival and Creative with both Sticky and Regular Pistons.
I have uploaded a video showing this:
http://www.youtube.com/watch?v=TKuiymEN5zc
From MC-88328:
Affected coordinates in a chunk:
1
5
9
13
The screenshot shows the result of trying to place pistons facing upwards. The lapis lazuli blocks mark the 0,0 corner; the redstone blocks mark the 15,15 corner.
Code analysis by @unknown: https://bugs.mojang.com/browse/MC-4132?focusedCommentId=320335&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-320335
Linked issues
is duplicated by 1
relates to 1
Attachments
Comments 15
I have no reason to build that far out, I was just messing around out there and noticed this piston glitch. It doesn't affect me, and probably wouldn't affect anyone else, but I wanted to report it, as it is a bug.
Plus, although it is 16 million out, the world goes all the way out to 30 million; if the chunks are going to be available they should work.
Is this still a concern in the current Minecraft version? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.
I have not been able to place a piston facing up anywhere for the past few weeks. Tried every different placement direction possible. Never had this problem before. Using x-box one.
Please link to this comment in the description
The following is based on a decompiled version of Minecraft 1.10 using MCP 9.30.
The reason for this is that the method net.minecraft.block.BlockPistonBase.getFacingFromEntity(BlockPos, EntityLivingBase) casts the positions to floats which causes a precision loss. Keeping them as doubles solves this.
Can I ask you why you're building so far out?
You've hit the limitations of the game engine, and stuff will act wonky.