[MCPE-151920] The command does not evaluate the selector argument "hasitem" -> data.

Update: The main three issues still apply in 1.19.2 and 1.19.20.20 exactly as they were before. The crash doesn't occur on the release version but does still occur in the preview.

From my testing in 1.18.31, these are the issues with how data values interact with hasitem:

For blocks with multiple data values, hasitem will detect the blocks while completely ignoring the data field in the command, and will detect them regardless of the block's data value. (What this specific bug report currently describes.)
For most other items, omitting the data field from hasitem (or setting it to a negative value) will act as if it was set to 0, only detecting the 0 data value of the item instead of detecting all instances of that item type regardless of data value.
For items with durability, hasitem will always act as if the data value of the damaged items is 0, and so will only detect them if the data field in the command is set to 0. This also applies to custom items with durability added with behavior packs.

All of this also applies in Preview 1.19.0.31, but the game will now crash if attempting to test for a negative data value on item IDs with only one data value or items with durability.

Edit: Just discovered in Preview 1.19.20.20 that the game also seems to also crash if testing for a negative data value on potions, splash potions, lingering potions, and arrows. I don't know if this used to happen.

Solo alt 2022-07-08T16:07:24Z

The hasitem can not detect lingering potions and splash potions

13 more comments

TheRedSmarty 2022-07-08T17:31:57Z

@Solo alt They both fall under the second issue I stated in my comment. If you don't specify a data value for a Splash Potion, it only looks for Splash Water Bottles (data value 0). You have to you use the correct data value for the effect.

Honestly, I think the three issues I described should be separate bug reports... plus one for the crashing... but all the created ones relating to one of the issues get marked as duplicates of this.

BeeTeeKay 2022-07-21T01:50:43Z

Affects 1.19.10

BeeTeeKay 2022-08-19T02:35:16Z

Affects 1.19.30.22 Preview

IzaacB 2022-11-21T14:35:59Z

It works weird in 1.19.41 with maps as well.

Try this:

/give @s empty_map 1 2
/testfor @a[hasitem={item=empty_map}]   <--- No targets matched selector
/testfor @a[hasitem={item=empty_map,data=2}]     <--- Found IzaacB
/give @s filled_map 1 2
/testfor @a[hasitem={item=filled_map}]    <--- No targets matched selector
/testfor @a[hasitem={item=filled_map,data=2}]     <--- No targets matched selector

Test Pattern 2023-01-10T01:12:32Z

We want to see if the caller, (@s) has an item in inventory, in this case, lime concrete so the game can do something with it.

This works with the example given:

/execute at @s[hasitem= {item=concrete, data=5}] run say lime concrete

this doesn't,

/testfor @s[hasitem= {item=concrete, data=5}]

If the player has lime concrete, the say command runs. If not, it says "no items matched selector

this is how Mojang put the "/testfor" into the @s target using "hasitem={}", as a selector, so it could easily get the data id. testfor only works when the data id = 0.

Greg Walls 2023-03-03T20:21:08Z

Accidentally closed this out, apologies.

user-f2760 2023-03-14T21:16:11Z

I suggest expanding the description and title of this report to note in what ways it doesn't work correctly, as it's not one way, as @unknown already pointed out:

Ignored for block-items.
all durability-items treated as having data of 0.
unprovided treated as testing for 0 on items. (Example: no data= in selector for ID potion only finds water bottles, not mundane potions.)

jordanparki7 2023-04-08T11:30:10Z

Hopefully this can be fixed soon - there's a ton of ideas I've had that have been limited solely by this issue. I know there's workarounds, but in a good amount of cases, they aren't enough. This should be prioritised.

Hangekisobu 2023-04-23T06:05:22Z

Workaround (from Discord Server "Bedrock Commands Community"):
To be typed in chat:

/scoreboard objectives add held dummy

Command Line:

/scoreboard players set @a held 0
/scoreboard players set @a [hasitem={item=diamond_sword,location=slot.weapon.mainhand,slot=0}] held 1
/clear @a [scores={held=1}] diamond_sword 69 1

/effect @a [scores={held=1}, hasitem={item=diamond_sword,location=slot.weapon.mainhand,quantity=0}] strength 1 1 true

/replaceitem entity @a [scores={held=1,hasitem={item=diamond_sword,location=slot.weapon.mainhand,slot=0,quantity=0}] slot.weapon.mainhand 0 diamond_sword 1 69

it might work 🙂

jordanparki7 2023-04-23T16:59:15Z

@Hangekisobu_231 That workaround only helps for a very small number of cases when you want to detect if the player is holding a non-enchanted item with a data value. It fails to consider enchanted items, items in other hotbar slots, items in the inventory. A fix for the 'hasitem' selector is ESSENTIAL and should be prioritised as it really is impacting community creations. I have personally scrapped 6 or 7 features of maps purely for this reason. I'll give you some examples from the Bedrock Commands Community Discord of how this bug has affected the community:

Tool repair system which takes into account tool durability (data component), player XP and mending to give the player the exact amount of XP to repair the tool without additional XP
Crate system which detects if a player has a certain flower (based on crate tiers)
Removal of banned items including Poison arrows, Locator maps, Invisibility Potions, (Factions Realms)
Achievement system for detecting when a player has gathered specific items (eg. 64x Spruce Leaves)
Custom spells system where a player has a particular "Item Totem" (eg. Blue Dye) to perform a specific spell.
A really awesome in-game market system to sell items on an auction house

These are specific examples that are not possible with that workaround. These examples show unequivocally that this bug is limiting player's creativity and further reinforce the need for this bug to be fixed as soon as possible.

BeeTeeKay 2023-04-25T01:26:24Z

Affects 1.20.0.21 Preview

Jeff bezos 2023-04-28T04:47:41Z

It seems like This only affects blocks and tools because I can get it to work with music discs but not with quartz blocks or swords

PleaseFixThis 2023-09-27T08:48:44Z

I tried to use this command

/execute as @a[hasitem={item=planks,data=0}] run /say has oak planks

but it successfully executes no matter which type of plank you have

Test Pattern 2024-01-02T11:02:17Z

still not fully implemented? Lets get on this one... I've tested every potion(drinkable, splash and lingering) as well as every suspicious_stew, ...they work (except for filters in the API noted below).

all of the following FLOWERS resolve to "poppy" (data 0)?

to recreate: copy one of the following 'replaceitem' commands and paste in chat, and then place any 1 tall flower in the players (@s) inventory slot 0. no matter what the flower is, any command listed below will erase it.

// poppy (correct)
"/replaceitem entity @s[hasitem=[{item=red_flower,data=0,quantity=1,location=slot.inventory,slot=0}]] slot.inventory 0 destroy air 1",
//blue orchid <--poppy
"/replaceitem entity @s[hasitem=[{item=red_flower,data=1,quantity=1,location=slot.inventory,slot=0}]] slot.inventory 0 destroy air 1",
// allium <-- poppy
"/replaceitem entity @s[hasitem=[{item=red_flower,data=2,quantity=1,location=slot.inventory,slot=0}]] slot.inventory 0 destroy air 1",
// azure_bluet aka houstonia <-- poppy
"/replaceitem entity @s[hasitem=[{item=red_flower,data=3,quantity=1,location=slot.inventory,slot=0}]] slot.inventory 0 destroy air 1",
// red tulip <-- poppy
"/replaceitem entity @s[hasitem=[{item=red_flower,data=4,quantity=1,location=slot.inventory,slot=0}]] slot.inventory 0 destroy air 1",
// orange tulip <-- poppy
"/replaceitem entity @s[hasitem=[{item=red_flower,data=5,quantity=1,location=slot.inventory,slot=0}]] slot.inventory 0 destroy air 1",
// white tulip <-- poppy
"/replaceitem entity @s[hasitem=[{item=red_flower,data=6,quantity=1,location=slot.inventory,slot=0}]] slot.inventory 0 destroy air 1",
// pink tulip <-- poppy
"/replaceitem entity @s[hasitem=[{item=red_flower,data=7,quantity=1,location=slot.inventory,slot=0}]] slot.inventory 0 destroy air 1",
// oxeye daisy aka oxeye <--poppy
"/replaceitem entity @s[hasitem=[{item=red_flower,data=8,quantity=1,location=slot.inventory,slot=0}]] slot.inventory 0 destroy air 1",
// cornflower <-- poppy
"/replaceitem entity @s[hasitem=[{item=red_flower,data=9,quantity=1,location=slot.inventory,slot=0}]] slot.inventory 0 destroy air 1",
// lily of the valley <-- poppy
"/replaceitem entity @s[hasitem=[{item=red_flower,data=10,quantity=1,location=slot.inventory,slot=0}]] slot.inventory 0 destroy air 1"
// poppy (correct I guess)
"/replaceitem entity @s[hasitem=[{item=red_flower,data=11,quantity=1,location=slot.inventory,slot=0}]] slot.inventory 0 destroy air 1",
"/replaceitem entity @s[hasitem=[{item=red_flower,data=12,quantity=1,location=slot.inventory,slot=0}]] slot.inventory 0 destroy air 1",
"/replaceitem entity @s[hasitem=[{item=red_flower,data=13,quantity=1,location=slot.inventory,slot=0}]] slot.inventory 0 destroy air 1",
"/replaceitem entity @s[hasitem=[{item=red_flower,data=14,quantity=1,location=slot.inventory,slot=0}]] slot.inventory 0 destroy air 1",
"/replaceitem entity @s[hasitem=[{item=red_flower,data=15,quantity=1,location=slot.inventory,slot=0}]] slot.inventory 0 destroy air 1"

inconsistencies: recipes - "red_flower" works in an ingredient array using "data"

{
  "format_version": "1.12",
  "minecraft:recipe_shapeless": {
    "description": {
    "identifier": "minecraft:blue_dye_from_cornflower"
    },

    
    "tags": [ "crafting_table" ],
    "group": "blue_dye",
    "ingredients": [
      {
        "item": "minecraft:red_flower",
        "data": 9
      }
    ],
    "result": {
      "item": "minecraft:dye",
      "data": 18
    }
  }
}

inconsistencies: "red_flower:<int> works in loot table array using "item" (wandering_trader_trades.json)

// start snippet
            {
              "max_uses": 12,
              "wants": [
                {
                  "item": "minecraft:emerald",
                  "quantity": 1
                }
              ],
              "gives": [
                {
                  "item": "minecraft:red_flower:0"
                }
              ]
            },
            {
              "max_uses": 8,
              "wants": [
                {
                  "item": "minecraft:emerald",
                  "quantity": 1
                }
              ],
              "gives": [
                {
                  "item": "minecraft:red_flower:1"
                }
              ]
            },
            {
              "max_uses": 12,
              "wants": [
                {
                  "item": "minecraft:emerald",
                  "quantity": 1
                }
              ],
              "gives": [
                {
                  "item": "minecraft:red_flower:2"
                }
              ]
            },
            {
              "max_uses": 12,
              "wants": [
                {
                  "item": "minecraft:emerald",
                  "quantity": 1
                }
              ],
              "gives": [
                {
                  "item": "minecraft:red_flower:3"
                }
              ]
            },
            {
              "max_uses": 12,
              "wants": [
                {
                  "item": "minecraft:emerald",
                  "quantity": 1
                }
              ],
              "gives": [
                {
                  "item": "minecraft:red_flower:4"
                }
              ]
            },
            {
              "max_uses": 12,
              "wants": [
                {
                  "item": "minecraft:emerald",
                  "quantity": 1
                }
              ],
              "gives": [
                {
                  "item": "minecraft:red_flower:5"
                }
              ]
            },
            {
              "max_uses": 12,
              "wants": [
                {
                  "item": "minecraft:emerald",
                  "quantity": 1
                }
              ],
              "gives": [
                {
                  "item": "minecraft:red_flower:6"
                }
              ]
            },
            {
              "max_uses": 12,
              "wants": [
                {
                  "item": "minecraft:emerald",
                  "quantity": 1
                }
              ],
              "gives": [
                {
                  "item": "minecraft:red_flower:7"
                }
              ]
            },
            {
              "max_uses": 12,
              "wants": [
                {
                  "item": "minecraft:emerald",
                  "quantity": 1
                }
              ],
              "gives": [
                {
                  "item": "minecraft:red_flower:8"
                }
              ]
            },
            {
              "max_uses": 12,
              "wants": [
                {
                  "item": "minecraft:emerald",
                  "quantity": 1
                }
              ],
              "gives": [
                {
                  "item": "minecraft:red_flower:9"
                }
              ]
            },
            {
              "max_uses": 7,
              "wants": [
                {
                  "item": "minecraft:emerald",
                  "quantity": 1
                }
              ],
              "gives": [
                {
                  "item": "minecraft:red_flower:10"
                }
              ]
            },

inconsistancies:

there is currently no way to use either a command (shown above) or a filter (shown below) in add-on entity to identify alt states of items, or at least it isn't in any documentation publicly available.

UPDATE 6/1/24: there is a filters only solution I found, based on that all minecraft namespace items do not need the 'minecraft:' namespace

// start snippet
"filters":{
	"any_of":[
		// WORKS!
		{"test": "has_equipment","domain": "inventory","value": "red_flower:1"},
                 // FAILS
                {"test": "has_equipment","domain": "inventory","value": "minecraft:red_flower:1"},
		// may work after flattening
		{"test": "has_equipment","domain": "inventory","value": "minecraft:blue_orchid"},
	]
},
"add": {
	"component_groups": [
		"phantom:fx_saturation_cg"
	]
}

jordanparki7 2024-02-22T00:12:37Z

Bump - this really should be fixed by now. As outlined in my previous comment, it's seriously impacting community creations.

thetoiletslayer 2024-07-04T19:54:09Z

Data values virtually don't work at all in the latest version of bedrock(1.21.1)

Try running this

/give @s iron_nugget 1 55

If you change the 55 to a different number, it will stack with the first one. Same if you get on from the creative menu, container, etc.

Data values are useless now

kilor112 2024-08-20T11:58:34Z

szea_ll14 2024-12-18T03:26:39Z

Many bugs of hasitem are linked as duplicates, but I think most of them have different causes. Issues should be separated.