33:6 causes crashes

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.

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.

/setblock ~ ~1 ~ minecraft:piston 6 replace

Seems to be fixed.

Just wanted to note: the same is for sticky pistons, but also fixed