-
Bug
-
Resolution: Fixed
-
Minecraft 17w45a, Minecraft 17w45b
-
None
-
Confirmed
when running a command such as
/execute if block ~ ~ ~ skull run say hi
and standing inside a skull, the command returns false, even though it should return true. (The command doesn't run)
this doesn't just affect execute (if/unless) block, this also affects fill replace.
In general, testing for any block that has block states (without specifying any) will always look for the default state of the block, when really it should ignore states. Therefore, the following two commands are equivalent:
execute if block ~ ~ ~ redstone_wire run say only unpowered redstone wire
execute if block ~ ~ ~ redstone_wire[power=0] run say only unpowered redstone wire
- is duplicated by
-
MC-121826 Blockstate matching uses default values for not set properties instead of wildcard
- Resolved
-
MC-121846 Wildcard blockstate selection doesn't work
- Resolved
- relates to
-
MCPE-168391 Block state predicates in commands do not work properly (unprovided states require default value)
- Open