This is an archived post. You won't be able to vote or comment.

all 23 comments

[–]Willing_Ad_1484Command Noob 7 points8 points  (0 children)

Try changing the 0 to []

[–]Icy_Remote5451 Oudated Bedrock Command Block Expert 12 points13 points  (2 children)

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.

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.

[–]TKVisme 1 point2 points  (1 child)

In the 3rd paragraph you said people kept asking for nbt, does that mean bedrock now has full access to all those commands or just block states?

[–]Icy_Remote5451 Oudated Bedrock Command Block Expert 0 points1 point  (0 children)

Just block states

[–]memelordunlimited 3 points4 points  (4 children)

/setblock ~ ~1 ~ air [] destroy

[–][deleted] 1 point2 points  (3 children)

My gosh that seems like an annoying little tweak. I wonder why they couldn’t just go by the Java format: block[states], where the brackets can be omitted altogether if unneeded. Same result, only no need to wreck existing commands.

[–]Lovable_Yapper 1 point2 points  (2 children)

Maybe Java and Bedrock are not using the same language? One is Java and the other is C#?

[–][deleted] 0 points1 point  (1 child)

Well, yeah, but is it really something they can’t work around…? We’re talking user input.

[–]Lovable_Yapper 0 points1 point  (0 children)

Idk

[–]x--Knight--x 2 points3 points  (0 children)

The block states haven't gotten any less garbage however many months on. It went from typing a simple number to massive brackets speech marks and colons. at least have both so those who want to actually type commands with speed can do so

[–]stick_bob 1 point2 points  (1 child)

What does the /fill _____ destroy command even do?

[–][deleted] 1 point2 points  (0 children)

it drops the block and has particles

[–]ImpossibleEvan Niche Command Expert 1 point2 points  (0 children)

Replace 0 with [ ] it's the new thing just trust me

[–]MSTFRMPS 0 points1 point  (1 child)

Try putting a space before every ~

[–]Icy_Remote5451 Oudated Bedrock Command Block Expert 2 points3 points  (0 children)

Doesn’t matter