Wojciech Drzymała
- drzymalsw
- drzymalsw
- Europe/Stockholm
- Yes
- No
MC-49424NBT keys do not work properly in case of chests. When you do create a chest with such command:
—
setblock #x #y #z chest 0 replace {Items:[
{Slot:0,id:torch}]}
—And test it with command:
—
{Slot:0,id:torch}
testforblock #x #y #z chest 0 {Items:[]}
—It would not return true value. It will show you this:
—
The block at #x,#y,#z did not have the required NBT keys.
—Hope you'll do something with it.
NBT keys do not work properly in case of chests. When you do create a chest with such command:
setblock #x #y #z chest 0 replace {Items:[{Slot:0,id:torch}]}And test it with command:
testforblock #x #y #z chest 0 {Items:[{Slot:0,id:torch}]}It would not return true value. It will show you this:
The block at #x,#y,#z did not have the required NBT keys.Hope you'll do something with it.
Oh, thank you very much - here I find application for these 'b' characters in the end.
NBT keys do not work properly in case of chests. When you do create a chest with such command:
setblock #x #y #z chest 0 replace {Items:[{Slot:0b,id:torch}]}And test it with command:
testforblock #x #y #z chest 0 {Items:[{Slot:0b,id:torch}]}It would not return true value. It will show you this:
The block at #x,#y,#z did not have the required NBT keys.Hope you'll do something with it.
When you're typing command that is creating a chest, you can not set it's rotation.
If you'll use:
/setblock ~ ~ ~ minecraft:piston #rotationAnd you'll put a correct number, where #rotation is, you will see, that piston is rotating right ways, but it doesn't work when using a chest, it's always faced as number 3.
When you're typing command that is creating a chest, you can not set it's rotation.
If you'll use:
/setblock ~ ~ ~ minecraft:piston #rotationAnd you'll put a correct number, where #rotation is, you will see, that piston is rotating right ways, but it doesn't work when using a chest, it's always faced as number 3.
Particles' "count" argument makes it doesn't work
When I do use command you said, it says:
'~' is not a valid numberI described it in other thread. Anyway, when I'll use command like this:
/particle smoke 121 56 -957 121 56 -957 0It works well and I can see smoke, but when I'll use:
/particle smoke 121 56 -957 121 56 -957 0 1Happens nothing. (With any speed I'd use)
When you're using command /particle and you'll add new argument called "count", your particle would not show.
deleted-When you're using command /particle and you'll add new argument called "count", your particle would not show.-deletedIt was my mistake. Everything works fine.
When using a "/particle" command, you can't recall to your own position or command block's. It says "~ is not a valid number".
By the way, there is another problem with "/particle" command and you can see it on other of my issues (link below).
MC-50500
deleted-When using a "/particle" command, you can't recall to your own position or command block's. It says "~ is not a valid number".-deletedIt was my mistake. I though that [xd], [yd] and [zd] are in-game positions, not relative to first coordinates.
When you will create a chest with such command:
setblock ~ ~ ~ chest 0 replace {Items:[0:{Slot:13b,id:minecraft:iron_sword}]}And you will take an iron sword from it, it will disappear when you right click holding it.
deleted-When you will create a chest with such command:-deletedsetblock ~ ~ ~ chest 0 replace {Items:[0:{Slot:13b,id:minecraft:iron_sword}]}
deleted-And you will take an iron sword from it, it will disappear when you right click holding it.-deletedMy bad...
What is incorrect? You can instruct me.
The problem shows still in 14w10c.
Used command:
setblock 11 45 87 chest 2 replace {Items:[{Slot:0b,id:torch}]}And its' facing is 3 instead of 2. (It's 3 everytime).
Still doesn't work, when used these:
setblock ~2 ~ ~ chest 5 replace {Items:[{Slot:0b,id:1b}]}testforblock ~1 ~ ~ chest 5 {Items:[{Slot:0b,id:1b}]}Positions' recalls are all right, the error says:
Jesus, what I did wrong was putting coordinates of the place, where I wanted to particle be, in [xd], [yd] and [zd] arguments. My mistake, sorry guys.
A'right, it works fine now. But where from should I have know that I must use this 0: before brackets? It's not written on minecraft wiki.
Oh God, I'm so dumb. Thanks.
/setblock ~ ~1 ~ minecraft:mob_spawner 0 destroy {EntityId:Slime,SpawnRange:5b}Actually works fine, when added SpawnRange.