33:6 causes crashes
The ID of basic Pistons "33:6", when a Redstone Torch is placed below it, causes the game to crash.
Linked Issues
is duplicated by8
MC-30973Game crashes when powering a piston with orientation data 6 (fixed)DuplicateMC-31189Crash with 33:6 (Piston Extension).DuplicateMC-31419/setblock ~0 ~0 ~0 minecraft:piston 14 crashes the gameDuplicateMC-31593Hopper: java.lang.ArrayIndexOutOfBoundsException: 6DuplicateMC-32326Piston falling on Redstoneblock Crashes gameDuplicateMC-38350Hopper: java.lang.ArrayIndexOutOfBoundsException: 6DuplicateMC-41785Minecraft All Sided Piston Game CrashDuplicateMC-43665Minecraft 6-sided piston CrashDuplicateAttachments1
Created Issue:
33:6 causes crashes
The ID of basic Pistons "33:6", when a Redstone Torch is placed below it, causes the game to crash.
relates to
![[Mod] CubeTheThird](../../../data/assets/gravatar/cubethethird.jpeg){kind=small}
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
![[Mod] Ezekiel (ezfe)](../../../data/assets/gravatar/ezekielelin.jpeg){kind=small}
Is this still a concern in the current Minecraft version 1.7.2 / Launcher version 1.3.4 or later? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.
Please reopen, MC-13252 is closed as "invalid" because the block was spawned with external tools. This is spawned using the new /setblock command (and therefore using only methods Minecraft provides)
Duplicate of MC-13252 - 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.
Duplicate of MC-13252 - 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.
Cannot reproduce, please attach the crash report, otherwise this ticket is incomplete.
Piston data value ranges only from 0 to 5.
Even so, if the value only goes up to 5 then why do you get a piston when giving the block to yourself? And, giving an invalid block ID should always result in "There is no such block with ID etc."
Trying to give yourself "33:6" still gives you the standard piston, so no problems there.
Hey guys - just to follow up, I'll go grab the crash report, it's very easily reproducible. It does require one to use an external program such as MCEdit or WorldEdit to add the block to your world, but once the block is placed, it will crash once a torch is below it.
The block appears as a piston with all sides being the top.
Crash report is being added right now.
Crash report for the block
"A full error report has been saved to C:\Users\Other Users\AppData\Roaming\.minecraft\crash-reports\crash-2013-04-07_01.10.03-server.txt - Please include a copy of that file (Not this screen!) if you report this crash to anyone; without it, they will not be able to help fix the crash
"
But:
This ticket is invalid as it relates to a modded or 3rd party client/server.
I came here because my own bug report (
MC-30973) got marked as a duplicate of this.Now my point for Kumasasa: with snapshot 13w36 and 13w37 you can place these blocks without any third party programs or mods.
It was a bit more difficult in 13w36a thou but it was possible via summoning a falling block entity with these data values. In 13w37a /setblock was added and now it is really simple to recreate: Type "/setblock ~ ~ ~ 33 6 replace" and then power the result of this.
I repeat: Reopen this as the invaild status is now invalid.
Well, yes.
Reopened.
Confirmed for 13w42a.
Command is different now, which is perfectly fine with receiving a redstone signal.
Seems to be fixed.
Just wanted to note: the same is for sticky pistons, but also fixed