Enchantment cost/level ranges are too narrow and homogeneous

[Lykrast]

General Information

All enchantments (except Curing) use the "default" min/max levels/costs for enchanting (1+10*level min, 6+10*level max), which means they are all available at similar "modified enchantment levels" (level 1 on 11-16, level 2 on 21-26, level 3 on 31-36).

Imo the fact they're all on the same level is an issue, as vanilla enchantments are far more spread out. That gives 2 issues:

• At low enchanting levels you just get Curing (starts at modified enchanting level 1) and Unbreaking (starts at 5).
• Amplify and Raging are harder to get because you can only get them from modified enchanting level 11 to 16.
• From modified enchating level 37 to 51 you can only get Curing or Unbreaking III. This can be seen by enchanting a high enchatability shield (like Silver) at level 30 on a table: very often (a good 50% of the time I'd say) you just get Curing and Unbreaking III.

I don't have good suggestion for their level costs, but maybe just using similar values to some vanilla enchantments could be a good start. Spreading out some of the enchantments around so you can get a few more at early levels (like enchanting level 5) and a few that don't appear until higher levels would be nice. Like, Poison Spikes and Wither Spikes don't feel like they should be available at the exact same level y'know? (or maybe that's just me on this)

Mostly, increase the max level costs, to be like minLevel+20~30 or something, instead of the default +5, so that we can get more of them at higher enchanting level.

To Reproduce:

1. Get an Enchanting Table with enough Bookshelves for level 30
2. Enchant a bunch of Silver/Nickel/Terrasteel Shields
3. Count how many have just Unbreaking III and/or Curing

Expected behavior:

Some more exciting enchantments, which I could only get like 50% of the time.

---

Environment Versions

Mystic Mods Versions

• Superior Shields: 2.1.0

Other Versions:

• Forge: 43.0.0
• Minecraft: 1.19.2

[EpicSquid]

I um. I had absolutely no idea that this is how it worked. I will definitely be tweaking this. Thank you.

[EpicSquid]

Fixed in 2.1.1 release