the new staicases do not follow the orientation id 0-3 etc. as normal stairs do making them impossible to usue in the fill-command when using fill command no mather what number is inserted orientation is always the same, old stairs do not have this problem.
[media][media][media][media]Linked issues
is duplicated by 3
Attachments
Comments 8
In fact, since block states was added, all newly added blocks doesn't support data values at all.
Such as Beehives, Azalea Leaves, Lightning Rod, and so many blocks
Because data values are already deprecated. /setblock or /fill support block states completely.
The problem is that some command such as testforblock and /fill ... replace .. (MCPE-133360) doesn't support block states still
relates to MCPE-130557, MCPE-119722, MCPE-127106,MCPE-125466, MCPE-105912, etc
The new blocks such as copper and deepslate use a different format for their orientation, you now need to specify the upside down bit and orientation separately. For example the following command will set a south facing upside down cut copper stair below you
setblock ~ ~-1 ~ cut_copper_stairs["upside_down_bit":true,"weirdo_direction":3]
Note there is no space between the block and the square bracket. The fill command works the same way.
Slabs have now been changed as of 1.19.40.22 to use the old system so deepslate, copper and mud can use the 0/1 after the name to specify lower and upper slab respectively, but their stairs still use the newer system as described above.
Is this still an issue in the latest version (1.17.11)? If so, can you please add it to the affected versions (or mention it if you are not the reporter).
This ticket will automatically reopen when you reply.