On a command block, the item is unpickable? Any ideas why?
You didn't specify the Count tag. Without it, it is assumed to be a stack of 0, meaning unobtainable. Simply add "Count:1".
Also, you should get into the habit of using the standard form for the id name: "minecraft:diamond_sword", it is likely this will soon be enforced and without the "minecraft:" the command may not work in future versions.
You didn't specify the Count tag. Without it, it is assumed to be a stack of 0, meaning unobtainable. Simply add "Count:1".
Also, you should get into the habit of using the standard form for the id name: "minecraft:diamond_sword", it is likely this will soon be enforced and without the "minecraft:" the command may not work in future versions.
I am too used to using TAB to autocomplete. Now I realize that for /testfor command, you have to use the minecraft: . Thanks for ur reminder, I will try to change my habit of writing minecraft:
Is there a command to spawn an entity in, like make a sunflower appear as if someone had pressed q and thrown it.
(PS, if there is, is there a way to make that sunflower named something? (Coin))
there sure is.
May I know the problem why when I did
On a command block, the item is unpickable? Any ideas why?
You didn't specify the Count tag. Without it, it is assumed to be a stack of 0, meaning unobtainable. Simply add "Count:1".
Also, you should get into the habit of using the standard form for the id name: "minecraft:diamond_sword", it is likely this will soon be enforced and without the "minecraft:" the command may not work in future versions.
Fixed command:
/summon Item ~ ~ ~ {Item:{id:"minecraft:diamond_sword",Count:1}}
Thanks!
I am too used to using TAB to autocomplete. Now I realize that for /testfor command, you have to use the minecraft: . Thanks for ur reminder, I will try to change my habit of writing minecraft: