how do i fix this | Bedrock Add-Ons | Page 1

Hello! It seems that you have been having trouble with the newly added block states for Minecraft bedrock 1.19.70, this is a pre-typed message just to give an outline on how this stuff works since I already know there’s going to be too many people asking about this.

First thing I’ll say is if you have a metadata of 0 for your command just replace it with a [] and you’ll be good, now if that isn’t the issue continue reading.

Now, why were block states added? Because java also has them, and they wanted to have bedrock be more similar to Java so that java players can switch over to bedrock (which makes more money), and also probably because they were sick of people that kept asking for nbt.

As for why your command isn’t working, it is because the old system (metadata) has been replaced with a better one, aka block states, these are basically, well, the states that a block can be in. A good example of this can be seen below:

setblock ~~~ stained_glass[“color”:”green”]

Which will, as you would guess, set the defaulted position’s block to green stained glass. If you are wondering how one would get the block states you can go visit the following link (just make sure you use the ones labeled under bedrock edition):

https://minecraft.fandom.com/wiki/Block_states

There can also be multiple block state arguments on one block, such as the “wood” block, in this case you would just separate it with a comma, an example of this is shown below:

setblock ~~~ wood[“pillar_axis”:”z”,”stripped_bit”:true,”wood_type”:”spruce”]

Now, you might’ve noticed “hey, this won’t work, the true isn’t incased in quotation marks1!!1!!1!” and to that I say, very nicely observed, but you’re wrong, for true and false boolean and integer (aka number) inputs you do not put quotation marks because they are not string inputs.

Minecraft Wiki

Block states

Block states (also known as block properties) are extra pieces of data that further define a block, such as how it appears or behaves.
In Bedrock Edition, there are also aux values (also known as Metadata) to define a block. Aux values are in the format of binary flags, which basically match the block states one-to-one. And they are accessible i...

Oh and detection commands involving blocks (such as /testforblock or /execute if block) need to have ALL the block states listed and defined in order for it to work. An example of what to do and what not to do is below:

❌What not to do:

execute if block ~~~ stone_button[“button_pressed_bit”:true]

✅What to do:

execute if block ~~~ stone_button[“button_pressed_bit”:true,”facing_direction”:1]

Now this should cover pretty much everything but you’re free to ping/reply to this if you still have SPECIFIC questions :D.

#how do i fix this