mojira.dev
MCPE-182675

"minecraft:damage_sensor": {"cause":"magic","damage":false} ignores "oozing", "weaving", "wind_charged", "infested"

Expected behavior: splash potion ("oozing", "weaving", "wind_charged", "infested") would not affect entity, as potions are magic.

Actual result: entity gets effect and starts throwing off particles.

Tests: "minecraft:damage_sensor" does not recognize "oozing", "weaving", "wind_charged", or "infested" as damage causes individually.

added new component:

"minecraft:spell_effects": {
    "remove_effects": ["wind_charged", "weaving", "infested", "oozing"]
}

entity still takes magic effect from splash potion.

I'll try some "damage_sensor" filters under the "entity_attack" cause and enable the "spell_effects" component from a component group dynamically, as it does not work passively. That said...

"minecraft:damage_sensor": { "cause": "magic", "damage": false }

...should block these NEW effects natively without this tedious work around process.

Linked issues

Attachments

Comments 7

A status effect is not damage. The documentation for damage_sensor equates damage with removing health points.

A status effect is not damage. The documentation for damage_sensor equates damage with removing health points.

Thanks GH .I'm guessing Spell effect will need to be added to the entity to remove any of these status effects, so I suppose I'll use the entity sensor to trigger the component group removing the Spell effect. Even as a closed report, I'll update this so future devs with a similar assumption will have a solution.

Thanks GH .I'm guessing Spell effect will need to be added to the entity to remove any of these status effects, so I suppose I'll use the entity sensor to trigger the component group removing the Spell effect. Even as a closed report, I'll update this so future devs with a similar assumption will have a solution.

As a developer courtesy... I've got a technique posted on twitter to remove/hide the new 1.21 status effects from a 3rd party entity. Twitter Link @TestPattern360 Cheers!

As a developer courtesy... I've got a technique posted on twitter to remove/hide the new 1.21 status effects from a 3rd party entity. Twitter Link @TestPattern360 Cheers!

Test Pattern

(Unassigned)

Unconfirmed

Windows

Windows 10

1.21.0

Retrieved