Switch to NamespacedKeys for enchantments

- Switched to using NamespacedKeys for enchantments instead of their names. This means that all properly registered custom enchantments are supported in one go.
- Removed the overengineered enchantment platform stuff. That was built with the idea that every custom enchantment plugin would have their own way of implementing custom enchantments. However, now that I found out that custom enchantments can just be registered using NamespacedKeys, none of this is required anymore.
This commit is contained in:
Pim van der Loos
2020-12-14 13:17:52 +01:00
parent 9d737eeed5
commit 03d0f9492e
11 changed files with 314 additions and 344 deletions

38
vanillaEnchantments Normal file
View File

@@ -0,0 +1,38 @@
minecraft:feather_falling
minecraft:frost_walker
minecraft:unbreaking
minecraft:projectile_protection
minecraft:knockback
minecraft:respiration
minecraft:punch
minecraft:protection
minecraft:blast_protection
minecraft:lure
minecraft:impaling
minecraft:smite
minecraft:silk_touch
minecraft:infinity
minecraft:thorns
minecraft:luck_of_the_sea
minecraft:multishot
minecraft:vanishing_curse
minecraft:fire_aspect
minecraft:depth_strider
minecraft:flame
minecraft:piercing
minecraft:fire_protection
minecraft:sharpness
minecraft:power
minecraft:sweeping
minecraft:aqua_affinity
minecraft:binding_curse
minecraft:bane_of_arthropods
minecraft:soul_speed
minecraft:looting
minecraft:efficiency
minecraft:mending
minecraft:riptide
minecraft:quick_charge
minecraft:fortune
minecraft:loyalty
minecraft:channeling