API to disable specific enchantments server-side

Is your feature request related to a problem?

Server owners and plugin developers often want to disable specific enchantments (for example Frost Walker, Mending, or custom ones) for gameplay balance or grief-prevention reasons.

Historically, plugins could reflect into Bukkit’s internal enchantment registry to remove entries, but since 1.20 this registry is immutable. This means there is now no safe, supported way to disable enchantments without writing large amounts of boilerplate to intercept every possible source (enchanting tables, anvils, villager trades, loot, commands, and the enchantment’s own effect).

Describe the solution you'd like.

An official API to disable enchantments, without reflection.
For example:

• A server-managed set of disabled enchantments:
  server.disableEnchantment(Enchantment.FROST_WALKER);
• Or an isEnabled(Server) method on Enchantment that Paper checks internally before:
  • Offering enchantments in tables
  • Applying them in anvils
  • Generating them in villager trades and loot
  • Executing /enchant
  • Triggering special effects (like Frost Walker ice)

Describe alternatives you've considered.

• Event interception and stripping: intercepting PrepareItemEnchantEvent, EnchantItemEvent, PrepareAnvilEvent, VillagerAcquireTradeEvent, LootGenerateEvent, and command preprocess events, then removing blocked enchantments. This works, but it is very verbose, fragile, and requires continuous maintenance to cover new pathways.

• Reflection hacks: editing the internal enchantment registry directly. This worked in older versions but no longer works after the registry was made immutable.

Other

This API would remove the need for brittle reflection hacks, reduce plugin boilerplate. It also keeps the registry immutable (which I understand why probably wont be reverted) while still giving server owners control over which enchantments are available.

No files or tests are named. Start by tracing the listed pathways—enchanting tables, anvils, villager trades, loot, /enchant, and enchantment effects—and review the referenced event interception alternatives. Done means a supported server-side mechanism consistently disables selected enchantments across those pathways without reflection.