When I summon a item entity on the ground with:
/summon Item ~ ~ ~3 {Item:{id:351,Damage:5,Count:1}}And use testfor like so:
/testfor @e[type=Item,r=200] {Item:{id:351,Damage:5,Count1}}The testfor command realizes there is an item on the ground (item.item.dyePower.purple) but says it does not meet the criteria. Any help?
I am using the exact same NBT Data for each. I with this would work, because when I tried to put in
@e[type=item.item.dyePowder.purple]it complained about the UUID. Please help me, as this is CRITICAL in a command block invention I'm making.
Linked issues
Comments 5
That's no bug in the bug tracker, you have either escape sqare brackes with \, or enclose the whole command with {code} tags (did that for you)
Press the little ❓ at the foot of the editor for formatting help.
I think the problem here (and with a lot of similiar bugs) is that command blocks don't properly understand "." in [ ] I had this post-1.8 Snapshot in 1.7 with scoreboard "all.Kill" objective.
Essentially a duplicate of/related to: https://mojang.atlassian.net/browse/MC-30976
You have not labeled the tag-types, which are required in this case. For your command (prior to 14w03a):
/testfor @e[type=Item,r=200] {Item:{id:351s,Damage:5s,Count1b}}14w03a+:
/testfor @e[type=Item,r=200] {Item:{id:minecraft:dye,Damage:5s,Count1b}}
There is a bug with the bug tracker where "[]" won't show up, but trust me, I added them.