The current way to test for specific component groups is to add components which don't work on this entity, testing for active effects or testing for families. All of these ways have a significant problem: You can't add them dynamically as you do with component_groups.
If I want to test whether component_group A and B are currently active, I already cannot use the static is_family (One component_group overwrites the minecraft:type_family of the other). Using effects and broken components may have unwanted side effects (in the future) like healing the entity (regeneration) or displaying a saddle texture (is_saddled). But most importantly: We're pretty limited with the amount of component_groups we can test for.
All this could be solved with a simple and small new filter...
{ "test": "has_component_group", "subject": "self", "value": "minecraft:zombie_jockey" }
...which would test whether the defined component_group is currently active.
I am strongly convinced -as an AddOn creator- that this feature would open the door for new, amazing creations and a more convenient experience while creating AddOns.
1 Comments
Please sign in to leave a comment.
Post a new comment: