-
Bug
-
Resolution: Unresolved
-
None
-
1.14.4, 19w44a, 19w45a, 19w45b, 1.15 Pre-release 1, 1.15 Pre-Release 2, 1.15 Pre-release 3, 1.15 Pre-release 4, 1.15, 1.15.1, 1.15.1 Pre-release 1, 1.15.2 Pre-release 2, 1.15.2, 20w06a, 20w07a, 20w09a, 20w10a, 20w11a, 20w13a, 20w14a, 20w15a, 20w16a, 20w19a, 20w20a, 20w28a
-
None
-
Confirmed
-
Advancements
The Bug
When a player shoots the end crystal that the ender dragon is healing from, nothing you can put for the type of what the direct_entity is will satisfy that condition for the criteria player_hurt_entity.
This is the criteria I was using:
"criteria": { "crystactics": { "trigger": "minecraft:player_hurt_entity", "conditions": { "damage": { "type": { "is_explosion": true, "direct_entity": { "type": "minecraft:end_crystal" } } }, "entity": { "type": "minecraft:ender_dragon" } } }
I tried end_crystal, arrow, player and even ender_dragon. Whatever you specify the direct_entity should be, nothing works.
When you punch an end_crystal as opposed to shooting it, "player" will work for direct_entity.
To make things easier, I made a datapack (attached) with all the advancements you need to reproduce the advancement bugs I reported.
- relates to
-
MC-188568 The entity_properties block loot table condition is still dysfunctional for some explosive entities
- Reopened