Do not resolve unless actually resolved!!!!!
/give @p stone_button 1 0 {CanPlaceOn:["stonebrick 3"]}
/give @p stone_button 1 0 {CanPlaceOn:[stonebrick 3]}
do not work! Yet
/give @p stone_button 1 0 {CanPlaceOn:["stonebrick"]}
/give @p stone_button 1 0 {CanPlaceOn:[stonebrick]}
both work!
Comments 10
I think this feature is not implemented yet 😞
Both give you a stone button with the attribute:
Can be placed on:
missingno
indeed not implented yet, but using
/give @p minecraft:stone_button 1 0 {CanPlaceOn:[minecraft:stonebrick]}
makes you able to place it on normal, cracked, mossy and ciceled stone bricks
@Steven, I know that, but that's all I can do, so for my chiseled bricks, I make them silverfish stone bricks.
Yep, while you could give something that works for any wool, for example you can't do one which can be placed only on white wool.
can this be resolved as works as intended?
and BTW data values are no longer in blocks themselves, they are now completely block states, items still have them trough
If it's intended to work like this, then that's pretty stupid. Why the heck would they want it to be this way, reducing it's potential.
the ability to do so was never introduced and data values in blocks are gone now, so this can be closed
Try this: