MythicEnchantsLegacyMigrator

A one-off migration tool for servers upgrading from the old Lumine "MythicEnchants 1.x" plugin to the modern MythicEnchants. It is not loaded automatically — nothing runs at boot, and it only touches files when you explicitly ask it to.

Why this is a separate addon

Legacy migration used to run automatically inside core on every enchant-file load. That caused real problems on servers that never had a legacy install: the detection heuristics could misfire on unrelated/hand-written modern enchants and register duplicate-named enchantments. Since migration is a one-time, opt-in operation, it now lives here instead — core no longer touches legacy schemas at all.

Usage

1. Drop MythicEnchantsLegacyMigrator.jar into plugins/MythicEnchants/addons/.
2. Restart the server (or reload addons).
3. Run /mench legacymigrate to dry-run — this scans plugins/MythicMobs/Enchantments/ (recursively) and reports which files contain old-schema enchantments, without writing anything.
4. Run /mench legacymigrate apply to actually rewrite the matched files in place. Each rewritten file gets a one-time <name>.yml.bak backup alongside it.
5. Restart the server. The addon only rewrites files on disk — core's EnchantmentLoader already finished parsing enchants for the current boot by the time addons load, so the modernised files take effect on the next start.

Permission: mench.legacymigrate

What gets migrated

Field mapping is verified against the real 1.x plugin source (io.lumine.mythicenchants), not guessed from a template:

An Enchanting.Weight of 5 is synthesised for any migrated enchant, since 1.x had no per-enchant table-weight concept (odds were entirely rarity-driven via a separate rarities.yml). Tune weights by hand afterward.

Two 1.x-only skill-line conditions have no modern equivalent and are flagged only, never rewritten — ?enchantlevel{level=N} and ?enchantslot{slot=X}. Review those lines by hand.