Conflicts

The conflict system prevents incompatible enchantments from being applied to the same item.

How It Works

When a player applies an enchantment (via /superenchant, anvil, or enchanting table), the plugin checks if the new enchantment conflicts with any existing enchantments on the item. If a conflict is found, the application is denied.

Conflict checking is bidirectional: if enchant A lists enchant B in its conflicts, they cannot coexist on the same item regardless of which is applied first. You only need to declare the conflict on one side.

YAML Syntax

Add a conflicts list to your enchantment file:

conflicts:
  - other_enchant_id
  - another_enchant_id

Example

# In heavy.yml
display_name: "<gray>Heavy"
conflicts:
  - lightweight

# lightweight.yml doesn't need to declare the conflict back,
# but it can for clarity:
display_name: "<white>Lightweight"
conflicts:
  - heavy

Bypassing Conflicts

Players with the superenchants.bypass.conflicts permission (default: op) can apply conflicting enchantments. This is useful for admins who want to create special items.

Notes

• Conflict IDs are the enchantment file names (without .yml), always lowercase

• Conflicts only prevent application -- they don't remove existing enchantments

• The conflict check runs when applying via /superenchant, anvil combining, and the enchanting table

• /segive gives books without conflict checks since books can hold any enchantment; the check happens at application time