Team Y4SH

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.

Kodari AI
KodariOct 17 at 5:39 am 1
Created EnchainSMPPlugins
Delegated to EnchainSMP Running
Create a complete, clean, compile-ready Paper 1.21.x plugin named EnchainSMP implementing the user's requested features. Inspect the project template first and preserve its conventions. Implement: (1) configurable repeating reward interval, default 900 seconds, awarding each online player a random enchanted book; each player's book enchantment is different from their own previously awarded books until that player has collected the full supported vanilla enchantment pool, then their pool resets; do not globally enforce differences across all players; (2) books display enchantment name and vanilla max level; (3) anvil combination of enchanted reward book with any item, ignoring vanilla enchantment/item compatibility while enforcing each enchantment's actual vanilla maximum level (including correct behavior for supported modern Paper 1.21 enchantments); no overleveling; preserve existing valid enchantments, applying book enchantment to item and consuming inputs appropriately; (4) provide robust best-effort support for arbitrary items/custom items. Avoid unsafe reflection/NMS unless unavoidable; Paper API support should be the project's configured target. For spear compatibility: research available API/custom model practicalities in this codebase/dependency; make Riptide, Loyalty, Channeling and Impaling apply and function on actual spear item implementations where Paper API allows. Explicitly document in config/README any fundamental API limitations—do not falsely claim arbitrary enchantments can reproduce an enchantment's effect on an incompatible material. (5) /enchain reload, /enchain give <player> <enchantment> [level], /enchain reset [player]; sane tab completion; permissions documented. (6) config.yml for interval, broadcasts and customizable messages; reload should reload config and reschedule reward task. Persist per-player collected pools across restarts (YAML or equivalent). Handle offline players, missing/invalid enchantments, full pool, shutdown/task cancellation, and permissions safely. Add plugin.yml, config.yml, README with commands/permissions/limitations and sensible defaults. Enforce vanilla max levels for commands and anvil results; prevent malformed levels. Use modern namespaced enchantment APIs as needed. Implement now; do not build or claim verified compilation.

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.

Report from 1 project
EnchainSMPCompleted
TaskCreate a complete, clean, compile-ready Paper 1.21.x plugin named EnchainSMP implementing the user's requested features. Inspect the project template first and preserve its conventions. Implement: (1)...

…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.

Kodari AI
KodariOct 17 at 5:44 am 1
Compiled EnchainSMPSucceeded

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.

Kodari can make mistakes. Review important code before using.
Files

No files in this session

Code