Delete or rename its YAML file in plugins/SuperEnchants/enchants/, then run /sereload. For example, to disable Venom, delete venom.yml.
Alternatively, to prevent specific players from using it without removing it entirely, negate the permission:
/lp user Steve permission set superenchants.use.venom false
How do I change activation rates?
Edit the chance field in the enchantment's YAML file:
# 20% base + 10% per levelchance:base:0.20per_level:0.10
Remove the chance field entirely to make it always activate.
How do I create a custom enchantment?
See the Creating Enchantments guide for a complete walkthrough. In short:
Create a new .yml file in plugins/SuperEnchants/enchants/
Define the required fields (display_name, max_level, applicable_items, trigger, target)
Add actions from the Action Types list
Run /sereload to load it
Can I change the max level of an enchantment?
Yes. Edit the max_level field in the enchantment's YAML file and run /sereload. Players who already have higher levels will keep them, but new applications will be capped.
Does it work with protection plugins?
Yes. SuperEnchants integrates with WorldGuard, GriefPrevention, Towny, Lands, and Residence. Enchantments that modify blocks (vein mine, timber, multi-break, lava walker, etc.) check region permissions before acting.
Enable or disable this in config.yml:
Can enchantments appear in the enchanting table?
Yes. Add an enchanting_table section to the enchantment YAML:
How do villager trades work?
When villager-trades.enabled is true in config.yml, librarian villagers have a chance to offer custom enchanted books. The chance, base-emerald-cost, and max-emerald-cost settings control the rates.
How do I see what enchantments are on an item?
Custom enchantments appear in the item's lore (the purple/gray text below the item name). You can also use /seinfo for details on any specific enchantment.
An enchantment isn't loading. How do I debug?
Set debug: true in config.yml
Run /sereload
Check the console for warnings like Enchant 'myenchant' missing display_name or action 'key' failed to parse