EnchantsForge
Build the Altar, then earn the enchantment
EnchantsForge adds custom enchantments to Paper 1.21.x and makes players build something to get them. There is no shortcut command: you raise an Altar in the world, and that is where enchanting happens.
WHY ENCHANTSFORGE
- The Altar is a place, not a command. Players build the structure, and enchanting becomes somewhere you go. A server with a landmark is a server people remember
- The enchantments stay put. They survive renaming in an anvil, splitting a stack and being handed around, because they are not written in the item's description where any edit could wipe them
- Rarity means something. Five tiers with weighted odds, so a legendary is rare on your server without you having to police it
- Conflicts are enforced everywhere. Two enchantments that should not share an item cannot, at the Altar and at the anvil. Players do not find the hole; there is not one
- Books make it an economy. Enchantments can exist as books, which means they can be sold, traded and given as rewards
WHAT YOU GET
- A physical Altar — a structure players build in the world, which is where enchanting happens
- 16 custom enchantments — each with its own levels, cost and behaviour
- Five rarity tiers — common through legendary, with weighted application
- Browser GUI — paginated and colour-coded by rarity, click any entry to read exactly what it does
- Conflict system — incompatible enchantments are refused at the Altar and at the anvil
- Enchantment books — obtainable in game, and grantable by staff at any level
- Durable data — enchantments survive anvil renames, stack splits and item transfers
- Developer API — write your own enchantment, register it, and hook seven events, without touching the plugin
- PlaceholderAPI — enchantment data for scoreboards, TAB or chat
- English and Spanish included, and every string a player reads lives in messages.yml in MiniMessage format
HOW IT WORKS IN PLAYA player gathers the materials, builds the Altar at their base and opens the browser to see what is available. They pick a rare one, apply it to their sword, and later try to add a second that conflicts — the Altar refuses and tells them which one is in the way. Months later they rename the sword in an anvil, and everything on it is still there.CONFIGURATION
- config.yml — the Altar recipe, rarity weights, which enchantments are enabled, their costs and levels, and the conflict table, every key with a comment beside it
- messages.yml — every string a player reads, so you can reword or re-colour the plugin without touching anything else