[MC-4132] Piston placement issue past 16777217 Created: 05/Dec/12  Updated: 12/Jul/20  Resolved: 05/Oct/16

Status: Resolved
Project: Minecraft: Java Edition
Component/s: None
Affects Version/s: Minecraft 1.4.4, Minecraft 1.4.5, Minecraft 1.8, Minecraft 1.8.1, Minecraft 1.8.4, Minecraft 1.8.6, Minecraft 15w44a, Minecraft 1.10.2, Minecraft 16w32a, Minecraft 16w32b, Minecraft 16w33a, Minecraft 16w35a
Fix Version/s: Minecraft 16w40a

Type: Bug
Reporter: Eric Lanini Assignee: [Mojang] Grum (Erik Broes)
Resolution: Fixed Votes: 4
Labels: precision-loss
Environment:

Singleplayer
OS X 10.7.5/10.9.4
Java 1.6.0_37/1.6.0_65


Attachments: PNG File 2015-05-31_13.13.57.png     PNG File Piston placing near world end (15w36d).png    
Issue Links:
Duplicate
is duplicated by MC-88328 Cannot place upwards / downwards faci... Resolved
Relates
relates to MC-11416 Dispenser / Dropper / Piston / Comman... Resolved
relates to MC-3718 Textures and Effects are off when far... Resolved
CHK:
Confirmation Status: Confirmed

 Description   

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 marcono1234: https://bugs.mojang.com/browse/MC-4132?focusedCommentId=320335&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-320335



 Comments   
Comment by Marcono1234 [ 10/Jul/16 ]

Relates to MC-88330 (new version of MC-3718)

Comment by Marcono1234 [ 10/Jul/16 ]

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.

Comment by Swekob [ 28/Oct/15 ]

Confirmed for 15w44a.

Comment by Kumasasa [ 23/Feb/15 ]

@Mwhatley: This bug tracker is only for Minecraft PC edition.

Comment by Whatley [ 23/Feb/15 ]

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.

Comment by HJS [ 20/Sep/14 ]

Oh,OK

Comment by StevenNL2000 [ 20/Sep/14 ]

MC-3718 is talking about different numbers, so it's not a duplicate. Also, MC-3718 was fixed in 14w32a, while this one is present in 1.8.

Comment by HJS [ 20/Sep/14 ]

Duplicate of MC-3718 I think. It is not marked as a duplicate.

Comment by Kumasasa [ 19/Sep/14 ]

16777217 = 0x1000001 = 2 24 +1

Comment by StevenNL2000 [ 19/Sep/14 ]

This bug just doesn't make sense, as there is nothing in Java that is limited to or stops at 16777217. 16777217=0x1000001=2^24+1, as posted below.

Comment by Eric Lanini [ 19/Sep/14 ]

This is still an issue and I have updated the affected version as well as environment.

Comment by Talven81 [ 26/Nov/13 ]

No response in 4 months, assuming no longer an issue.

Comment by Kumasasa [ 14/Jul/13 ]

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.

Comment by Eric Lanini [ 05/Dec/12 ]

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.

Comment by Mustek [ 05/Dec/12 ]

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.

Generated at Sun Jan 12 12:03:33 UTC 2025 using Jira 9.12.2#9120002-sha1:301bf498dd45d800842af0b84230f1bb58606c13.