🔗Compatibility

EnchantedMobs loads integrations only when the corresponding plugin is present. Missing optional plugins do not prevent normal startup.

Item providers

The default item-hook implementation directly supports:

• ItemsAdder

• Oraxen

• MMOItems

• EcoItems

• EcoArmor

• MythicMobs items

• eco

• NeigeItems

• ExecutableItems

• Nexo

• CraftEngine

These integrations are used by ItemFormat, saved items, item matching, equipment abilities, and configuration fields that request a provider item by plugin name and item ID.

See ItemFormat™ for the local item format reference.

ItemBridge mode

config.yml can switch item resolution to ItemBridge:

hook-item-method: ITEMBRIDGE

When enabled, the plugin asks ItemBridge to detect its supported providers. If ItemBridge cannot resolve an item, EnchantedMobs falls back to a directly registered item hook when available.

The default mode is:

hook-item-method: DEFAULT

Use ItemBridge mode when you need one of its additional providers or standardized ID detection. Keep the default mode when the built-in hooks already cover the server and you prefer fewer integration layers.

MythicMobs

MythicMobs integration provides:

• MythicMobs item resolution;

• the mythicmobs Match Entity rule;

• the mythic_skill ability for running a configured MythicMobs skill.

The relevant feature safely remains unavailable when MythicMobs is not loaded.

LevelledMobs

When LevelledMobs is installed, the levelledmobs Match Entity rule is registered. This allows power selection rules and typed match_entity conditions to include LevelledMobs-specific matching.

PlaceholderAPI

The expansion identifier is enchantedmobs and currently provides:

Placeholder	Result
%enchantedmobs_player_power%	Calculated strength of the online player.
%enchantedmobs_chunk_power%	Nearby average player strength using mob-power-generator.player-scan-range.

Offline or unavailable player context resolves to 0.

PlaceholderAPI placeholders that return numbers may also be used in the player-power.yml formula. placeholderapi-cache-ticks controls caching of the final value when formula placeholders are involved.

NBTAPI

When NBTAPI is installed, additional legacy NBT Match Item rules are registered.

Example:

nbt:
  string:
    customNBT: Hello
  int:
    anotherNBTComponent.theNBTKey: 5

Supported value groups include:

• byte

• short

• int

• long

• float

• double

• string

For modern Minecraft item components, prefer the normal ItemFormat and native matching options where possible.

Other declared optional dependencies

The plugin metadata also declares optional loading relationships for integrations such as MythicChanger and PacketEvents. Availability of a concrete feature still depends on the current implementation and installed plugin version; check startup logs to confirm that a hook was registered successfully.