MC-121826Blockstate matching uses default values for not set properties instead of wildcard
The bug
Blockstate matching uses the default values for not set properties instead of allowing any value. This means that for example stone matches only stone[variant=stone]
How to reproduce
- Place granite below you
/setblock ~ ~-1 ~ stone[variant=granite]
- Try to test for stone in general
/execute if block ~ ~-1 ~ stone run say Any stone found→ The message is not displayed, only when changing stone to stone[variant=granite]
Created Issue:
Block statement acting weird
execute unless block -13 63 -7 stone_button[powered=false] run scoreboard players add Timer bb.timer 1will increase the score even the button is not being push but put facing state in the command will working as expected
Added Labels: blockstate
Changed Summary:
Blockstatement acting weirdBlockstate matching uses default values for not set properties instead of wildcard
Changed Description:
execute unless block -13 63 -7 stone_button[powered=false] run scoreboard players add Timer bb.timer 1will increase the score even the button is not being push but put facing state in the command will working as expected
The bug
Blockstate matching uses the default values for not set properties instead of allowing any value. This means that for example stone matches only stone[variant=stone]
How to reproduce
- Place granite below you
/setblock ~ ~-1 ~ stone[variant=granite]- Try to test for stone in general
/execute if block ~ ~-1 ~ stone run say Any stone found→ The message is not displayed, only when changing stone to stone[variant=granite]
![[Mod] Neko](../../../data/avatars/users/92901.png){kind=small}
Added Linked Issues:
duplicates
Made the report more generic, I hope you are fine with that.