🔍Match Entity Format

MatchEntityFormat is the shared configuration format used whenever EnchantedMobs needs to test a living entity.

It is used by power-generation match-entity sections, the match_entity Power Condition, and abilities such as nearby_entities that filter candidate entities.

match-entity:
  entity-types:
    - ZOMBIE
    - SKELETON
  entity-health: 20

The example matches a zombie or skeleton whose current health is at least 20.

Evaluation rules

A MatchEntityFormat section does not use a type field. Each recognized key enables one rule.

Rules on the same level use AND:

match-entity:
  monster: true
  ranged: true
  entity-health: 10

The entity must be a Bukkit monster, must satisfy the ranged check, and must currently have at least 10 health.

Within most list-based rules, entries use OR.

Empty and invalid inputs

• A missing MatchEntityFormat section matches everything.

• A missing entity does not match.

• MatchEntityFormat accepts LivingEntity; non-living entities cannot be evaluated by this matcher.

• An unrecognized key is ignored.

• none: true forces the section to fail.

Logical composition

Use numbered any groups for alternatives that contain several rules:

match-entity:
  any:
    1:
      entity-types:
        - SKELETON
      ranged: true
    2:
      mythicmobs:
        - SkeletonKing

Use not to reject any entity matching a nested rule:

match-entity:
  monster: true
  not:
    entity-types:
      - CREEPER
    entity-tag:
      - minecraft:bosses

See Logical Rules for exact any and not behavior.

Nested equipment matching

The equip rule contains one MatchItemFormat section per equipment slot:

match-entity:
  equip:
    main-hand:
      material-tag:
        - minecraft:swords
    helmet:
      material:
        - carved_pumpkin

Configured equipment slots use OR: matching either the main hand or helmet is enough for the equip rule to pass.

Optional rule availability

Rule	Requirement
mythicmobs	MythicMobs must be loaded when EnchantedMobs starts.
levelled-mobs	LevelledMobs must be loaded when EnchantedMobs starts.
Paper-specific ranged classification	On Paper, the entity must implement Paper's RangedEntity and hold a supported ranged weapon.

Unavailable integration rules are not registered. Their keys are ignored rather than treated as a failed match.

Rule index

Rule key	Reference
entity-types	Identity and State Rules
none	Identity and State Rules
entity-contains-name	Identity and State Rules
entity-health	Identity and State Rules
entity-tag	Identity and State Rules
entity-pdc	Identity and State Rules
ranged	Identity and State Rules
monster	Identity and State Rules
equip	Equipment and Integration Rules
mythicmobs	Equipment and Integration Rules
levelled-mobs	Equipment and Integration Rules
any	Logical Rules
not	Logical Rules

Complete example

match-entity:
  monster: true
  entity-health: 20
  any:
    1:
      ranged: true
      equip:
        main-hand:
          material:
            - bow
            - crossbow
    2:
      mythicmobs:
        - SkeletonKing
  not:
    entity-types:
      - CREEPER

The entity must be a monster with at least 20 current health. It must either be a ranged bow/crossbow user or the MythicMob SkeletonKing, and it must not be a creeper.

Related references

• MatchItemFormat: item rules used by equip.

• Power Conditions: the match_entity condition selects a trigger-context entity and applies this format.

• Abilities: nearby_entities uses MatchEntityFormat to filter nearby living entities.

• Mechanics: power generation uses apply-rules.match-entity.