mojira.dev
MCPE-179599

has_damage test doesn't evaluate "magma" value

Reproduce:

Set min_engine_version to 1.20.71

Set entity format version to 1.20.71

{
      "test": "has_damage",
      "value": "magma"
     }

 

Expected Result:

No errors thrown. /damage shows "magma" as a damage option, so it should be evaluated here in this filter. Additionally, fire, fire_tick, contact, and self_destruct do no work to test for magma damage. There is currently no way to test for magma block damage as of recent using has_damage filter.

Observed Result:

[Actor][error] ... minecraft:damage_sensor | triggers | on_damage | any_of | all_of | none_of | Filter member value of test has_damage must be a preset string.

[Actor][error] ... minecraft:damage_sensor | triggers | on_damage | any_of | all_of | none_of | Filter test failed to parse inputs -> has_damage

Linked issues

Attachments

Comments 5

Please attach a sample behavior pack that can be used to test this.

I attached a simple BP with a damage sensor containing a test for "magma" and "contact" damage, and NOT dealing damage when touching them. Instead, you get an error and you are immune to all damage.

I attached a simple BP with a damage sensor containing a test for "magma" and "contact" damage, and NOT dealing damage when touching them. Instead, you get an error and you are immune to all damage.

Can confirm, affects 1.20.72. Reproduced on Windows.

V1beR8er

(Unassigned)

738375

Confirmed

Multiple

Android 13

1.20.70, 1.20.72 Hotfix, 1.21.70

Retrieved