Equipment and Integration Rules
Last updated
Every rule on this page is a key inside a MatchEntityFormat section.
equipPurpose: Matches one of the entity's configured equipment slots using MatchItemFormat.
Context: The entity must expose Bukkit EntityEquipment; each configured slot contains a MatchItemFormat section.
equip.main-hand
unset
Match the main-hand item.
equip.off-hand
unset
Match the off-hand item.
equip.helmet
unset
Match the helmet item.
equip.chestplate
unset
Match the chestplate item.
equip.leggings
unset
Match the leggings item.
equip.boots
unset
Match the boots item.
match-entity:
equip:
main-hand:
material:
- bow
- crossbow
helmet:
contains-name:
- CommanderConfigured slots use OR. The example passes when either the main hand is a bow/crossbow or the helmet name contains Commander.
Rules inside one slot's MatchItemFormat use their normal same-level AND behavior.
An entity without an equipment object fails this rule.
A missing/empty slot normally fails that slot's MatchItemFormat.
To require several equipment slots simultaneously, place each slot requirement in separate surrounding MatchEntityFormat checks; one equip block cannot express slot-level AND by itself.
mythicmobsPurpose: Matches a MythicMobs internal mob ID.
Context: Registered only when MythicMobs is loaded. The entity must be an active MythicMob instance.
mythicmobs
empty
Accepted MythicMobs internal names. Entries use OR.
IDs are compared case-insensitively with MythicMob#getInternalName.
Display names are not used.
A normal Bukkit entity that is not an active MythicMob does not match.
If MythicMobs is absent during startup, this rule is not registered and the key is ignored.
levelled-mobsPurpose: Matches the level stored by LevelledMobs.
Context: Registered only when LevelledMobs is loaded. The level is read from LevelledMobs' level integer PDC key; missing data is treated as level 0.
levelled-mobs
unset
Exact level, inclusive range, >= minimum, or <= maximum.
10~20 is inclusive at both ends.
Only >=, <=, range, and exact forms are implemented; standalone > and < are not supported.
The expected values must parse as integers.
If LevelledMobs is absent during startup, the rule is not registered and the key is ignored.
Current implementation limitation: matching reads levelled-mobs as a scalar string, but rule-presence detection uses getStringList. On standard Bukkit configuration a scalar may therefore be treated as absent and skipped. Verify this rule on the target build before relying on it.
Last updated
match-entity:
mythicmobs:
- SkeletonKing
- FlameGuardianmatch-entity:
levelled-mobs: '10~20'match-entity:
levelled-mobs: '>=5'match-entity:
levelled-mobs: '<=50'match-entity:
levelled-mobs: '15'