-
Bug
-
Resolution: Invalid
-
None
-
1.15.2, 20w15a, 20w19a, 20w20b, 20w21a, 20w22a, 1.16 Pre-release 2, 1.16 Pre-release 3, 1.16 Pre-release 4, 1.16 Pre-release 5, 1.16 Pre-release 6, 1.16 Pre-release 7, 1.16 Pre-release 8, 1.16 Release Candidate 1, 1.16, 1.16.1, 20w27a, 20w28a, 20w29a, 20w30a, 1.16.2 Pre-release 1, 1.16.2 Pre-release 3, 1.16.2, 1.16.3, 1.16.4, 20w46a, 20w51a, 1.16.5, 21w17a, 21w19a, 1.19.4, 23w12a
-
None
-
Community Consensus
-
Commands, Data Packs
-
Normal
-
Platform
The bug
Targeting an entity using a predicate that contains the damage_source_properties condition simply doesn't work.
I tried the following commands in both repeating command blocks and datapack tick functions:
execute as @e[predicate=predicate_path] run say hit
{
"condition": "minecraft:damage_source_properties",
"predicate": {
"is_fire": false
}
}
execute as @e[predicate=predicate_path,nbt={HurtTime:10s}] run say hit
{
"condition": "minecraft:damage_source_properties",
"predicate": {
"is_fire": false
}
}
execute as @e[predicate=predicate_path] run say hit
{
"condition": "minecraft:entity_properties",
"entity": "this",
"predicate": {
"nbt": "{HurtTime:10s}"
},
"condition": "minecraft:damage_source_properties",
"predicate": {
"is_fire": false
}
}
After hitting mobs, I didn't get any sort of response. I tried all kinds of damage types, but didn't get any feedback, and nothing was logged. If you try it yourself, you'll find that the damage_source_properties selector simply doesn't work. I've confirmed that most other predicate conditions are functional - it only seems to be an issue with this one.