Create a Paper 1.21.x Minecraft plugin called EnchainSMP.
The main feature is that any enchantment can be applied to any item, while keeping vanilla max levels.
Core Features
Every 15 minutes, every online player receives 1 random enchantment book.
The enchantment is different for every player.
Each enchantment can only be given once to a player until they have collected them all.
After collecting every enchantment, the pool resets automatically.
The book should display the enchantment name and its vanilla level.
Enchanting System
Players can combine the random enchantment book with any item in an anvil.
Ignore vanilla item restrictions (Sharpness on sticks, Protection on helmets, etc.).
Never exceed vanilla limits:
Sharpness V
Protection IV
Unbreaking III
Mending I
etc.
Do not create illegal levels like Sharpness X or Fortune X.
Spear Compatibility
Riptide must fully work on custom spear items.
The spear should behave like a trident for Riptide while still being a spear.
Loyalty, Channeling, and Impaling should also function correctly on spears.
Universal Item Support
Any enchantment should work on any item:
Weapons
Tools
Armor
Blocks
Food
Custom items
Preserve all enchantment effects whenever possible.
Commands
/enchain reload — reload config
/enchain give — give a specific enchant book
/enchain reset — reset collected enchantments
Config
Change reward interval (default 900 seconds)
Enable/disable broadcast messages
Customize messages
Support permissions
The code should be clean, optimized, and ready to compile as a Paper plugin with no enchantment level exceeding vanilla limits.
I’ve started the EnchainSMP Paper plugin, including the reward system, anvil enchantment handling, commands, configuration, and documentation. I’ll report back when the implementation is ready.
…n>1. Inspect the plugin template and target API conventions.
2. Implement rewards, per-player enchantment tracking, commands, and anvil handling.
3. Add configuration, persistence, and documentation for limitations and permissions.Created EnchainSMP with per-player reward pools persisted across restarts, configurable scheduled rewards and messages, max-level-validated /enchain commands, and an anvil handler that preserves existing enchantments while rejecting overlevelled results.
Spear/API limitations are documented: enchantments can be applied where item metadata permits, but Paper’s public API cannot make unsupported enchantment effects work on arbitrary spear implementations. A trident-backed custom-model spear retains vanilla trident behavior.
I did not build or verify compilation.
EnchainSMP is implemented, and the Paper plugin build succeeded. It includes configurable timed rewards, per-player collection tracking, /enchain commands, and an anvil handler that enforces vanilla enchantment maximum levels.
Spear behavior has an API limitation: applying enchantments cannot make unsupported effects work on arbitrary spear implementations. The README documents this and the trident-backed custom-model approach for retaining vanilla trident behavior.
No files in this session