MC-58985Blocks pushed by Pistons above Y=256 are deleted
Unsure if this is limited to snapshots or what, but if I push a block above 256 with a piston, that block is deleted from the world.
http://prntscr.com/3we3pm
http://prntscr.com/3we3sq
Soo... yh.
Environment
Mac OS X - Java 7
Linked Issues
Created Issue:
Pistons above 256
Unsure if this is limited to snapshots or what, but if I push a block above 256 with a piston, that block is deleted from the world.
http://prntscr.com/3we3pm
http://prntscr.com/3we3sqSoo... yh.
Environment
Mac OS X - Java 7
is duplicated by
Blocks pushed by Pistons above Y=256 are deleted
![[Mojang] Searge (Michael Stoyke)](../../../data/assets/gravatar/searge.png){kind=small}
![[Mojang] Nathan Adams](../../../data/assets/gravatar/dinnerbone.png){kind=small}
[Mojang] Nathan AdamsA comment with security level 'global-moderators' was removed.
A comment with security level 'global-moderators' was removed.
Boross Gergő I get what you mean, and I also agree with sac11221, but putting this being potentially expected behaviour and thus potentially a bug aside, could you give me examples of when piston without a block below/above extending towards absolute build maximum (Sky/Void) would come in handy?
Again, while I understand that this could be seen as expected behaviour, fixing things like these just for the sake of it, when it has no use/benefits whatsoever (and doesn't break gameplay in some manner), seems like developer worktime invested into something that could be used elsewhere better (e.g. revamping the whole Redstone system).
From what we've seen in the past, it also doesn't seem to be advisable to have the Devs fiddle with the piston code at the current state of the code in totality, unless there'd be a really good reason to do so.
Of course, up to Mojang to decide, but I always get nervous when I see piston bugposts due to past experiences.
Edit: I remembered an old bugfix (2014), found it now: MC-58985
Blocks would get deleted past the build limit.
Arrabbani Maybe due to fix of MC-58985, this bugpost here is a dupe of MC-69876, as [Mod] markderickson found out; a potential fix is also mentioned in said bugpost.
Blocks cannot exist above 256 / below 0.
Could it not just prevent the piston instead of removing the block from existence?
This would be a feature request, please see: Minecraft Suggestions on Reddit.
pistons just not extending is what happened in the previous versions.
this is very annoying because it destroys upwards flying machines
That was my point ^^
Pretty sure it's a change, but might not be.
I know for a fact that if you try to push a block below Y level 0 it just doesn't work. Which i'd think would be the same for above 256.
Seems somewhat silly to have it for one but not the other etc etc but hey ho
Reopened.
actually pushing blocks below does delete them. i know in the past it didnt but it does now. and in the past you couldnt push blocks above either
I'm surprised the mod didn't know that, but it's supposed to be impossible to push blocks below 0 or above 255. The piston is supposed to react as if you tried to push bedrock. It's mentioned in the wiki and is the behavior in most versions since the piston was introduced. Of course the build limit would've been 127 back when it was introduced. Among other things people trying upwards moving slimepunk ships are likely to hit the build limit quick, and a nice safe "there's an invisible ceiling here" mechanic is important. Clone should do the same for clone-move ships trying the same trick.