Create a production-ready Minecraft Java plugin called "VyronEnchantments".
TARGET:
- Minecraft: Java Edition 1.21.11
- Server software: Paper
- Java: 21+
- Plugin must be optimized for public SMP servers.
- Use Adventure API / MiniMessage for messages.
- Use Bukkit/Paper API only where possible.
- Do NOT require NMS unless absolutely necessary.
MAIN PURPOSE:
Create a custom enchantment system with 60 unique custom enchantments.
The plugin must support:
- Custom enchanted books
- Custom enchantment levels I, II and III
- Custom enchantment effects
- Custom particles
- Custom sounds
- Cooldowns
- Activation chances
- Item compatibility
- Villager trading
- Custom Enchanting Table system
- Configuration files
- Permissions
- Admin commands
- Persistent data using PersistentDataContainer
- Reload support
- Performance optimization
================================================== CUSTOM ENCHANTMENTS ==================================================
Create these 60 enchantments:
SWORD / AXE:
- Soul Reaper
- Void Strike
- Thunderlord
- Bloodlust
- Lifesteal
- Berserker
- Executioner
- Frostbite
- Venom
- Gravity
- Repulse
- Inferno
- Doom Mark
- Chain Reaction
- Vampiric Aura
- Rage Core
- Shadow Blade
- Armor Breaker
- Impact
- Soul Slash
ARMOR:
- Phoenix
- Titan
- Guardian
- Reflector
- Enderbound
- Shadowstep
- Windrunner
- Time Breaker
- Fortress
- Second Heart
- Astral Guard
- Ice Skin
- Infernal Skin
- Featherfall+
BOW / CROSSBOW:
- Storm Arrow
- Toxic Arrow
- Frost Arrow
- Death Mark
- Void Arrow
- Explosive Shot
- Piercing Soul
- Hunter's Eye
TOOLS:
- Miner's Fury
- Prospector
- Magnetism
- Blast Miner
- Ore Vision
- Chain Miner
- Tunnel Vision
- Fortune Master
FARMING / UTILITY:
- Lumberjack
- Harvester
- Hydro Boost
- Green Thumb
- Beekeeper
- Deep Fisher
SPECIAL:
- Elytra Surge
- Mace Mastery
- Reality Rift
- Chronoshift
================================================== RARITY SYSTEM ==================================================
Add 5 rarities:
COMMON RARE EPIC LEGENDARY MYTHIC
Distribution:
- Common: 15
- Rare: 15
- Epic: 12
- Legendary: 10
- Mythic: 8
Every enchantment must have:
- ID
- Display name
- Description
- Rarity
- Max level
- Compatible items
- Activation chance
- Cooldown
- Particle effect
- Sound effect
- Level I ability
- Level II ability
- Level III ability
Do NOT make all enchantments simple percentage damage increases.
Abilities should feel unique and powerful.
================================================== ENCHANTMENT BOOKS ==================================================
Custom enchanted books must be identifiable using PersistentDataContainer.
Example:
Item:
Enchanted Book
Display: "⚡ Thunderlord III"
Lore: "Summons lightning when attacking." "Rarity: LEGENDARY" "Level: III"
Custom books must not be confused with vanilla enchanted books.
Books must preserve their custom enchantment data when:
- dropped
- picked up
- stored in chest
- moved through inventory
- traded
- placed in an anvil
================================================== LEVEL SYSTEM ==================================================
Every enchantment supports:
Level I Level II Level III
Higher levels must improve the ability.
Example:
Thunderlord:
Level I: 15% activation chance.
Level II: 25% activation chance and stronger effect.
Level III: 35% activation chance, stronger lightning and chain effect.
Do similar progression for every enchantment.
================================================== VILLAGER SYSTEM ==================================================
Create a special Custom Enchantment Villager system.
Requirement:
A Villager must have 4 Lecterns positioned around it.
When the plugin detects the required 4 Lecterns around the Villager, the Villager becomes a Custom Enchantment Trader.
The trader should offer custom enchanted books.
The trade pool must include all 60 enchantments.
Trade rarity must affect:
- Emerald price
- Book level
- Availability
- Rarity
Common enchantments should be cheaper.
Mythic enchantments should be extremely expensive/rare.
Prevent exploits such as:
- infinite trade generation
- duplicated books
- duplicated emeralds
- invalid trade manipulation
Make the required Lectern arrangement configurable.
================================================== CUSTOM ENCHANTING TABLE ==================================================
Create a custom enchanting system.
Requirement:
- Enchanting Table
- 30 valid Bookshelves
- Bookshelves must be within 10 blocks radius.
If 30 valid Bookshelves are detected:
Enable Custom Enchanting.
Players can then receive custom enchantments from the Enchanting Table.
Custom enchanting should use a weighted random system based on rarity.
Possible rarity chances should be configurable.
Example default:
Common: 40% Rare: 30% Epic: 18% Legendary: 9% Mythic: 3%
Do not replace vanilla enchanting completely.
Allow both vanilla enchantments and custom enchantments.
================================================== ANTI EXPLOIT ==================================================
Prevent:
- Book duplication
- Villager trade duplication
- Inventory duplication
- Anvil duplication
- Item stacking exploits
- Custom enchantment data loss
- Invalid item combinations
Do not trust item display names alone.
Always identify custom enchantments using PersistentDataContainer.
================================================== ITEM COMPATIBILITY ==================================================
Each enchantment must have strict item compatibility.
Examples:
Soul Reaper:
SWORD
Mace Mastery:
MACE
Elytra Surge:
ELYTRA
Miner's Fury:
PICKAXE
Lumberjack:
AXE
Harvester:
HOE
Do not allow incompatible enchantments through anvils or commands unless explicitly forced by an admin command.
================================================== ANVIL SUPPORT ==================================================
Allow players to combine compatible custom enchanted books with compatible items using an Anvil.
Support:
Book + Item Book + Book
Book + Book should upgrade:
Thunderlord I + Thunderlord I = Thunderlord II
Thunderlord II + Thunderlord II = Thunderlord III
Do NOT allow:
Thunderlord III + Thunderlord III
Different custom enchantments may coexist if compatible.
Add configurable maximum enchantments per item.
================================================== COMMANDS ==================================================
Create:
/venchant
/venchant give <player> <enchantment> <level> [amount]
/venchant list
/venchant info <enchantment>
/venchant reload
/venchant debug
/venchant remove <player> <enchantment>
Tab completion is REQUIRED.
Examples:
/venchant give Steve thunderlord 3
/venchant give Steve soul_reaper 2 1
================================================== PERMISSIONS ==================================================
Create:
vyronenchantments.admin vyronenchantments.give vyronenchantments.reload vyronenchantments.list vyronenchantments.info vyronenchantments.debug
Default:
- Normal players: no admin permissions
- Admin: all permissions
================================================== CONFIGURATION ==================================================
Create:
config.yml enchantments.yml messages.yml trades.yml gui.yml
Everything important must be configurable.
Examples:
activation chances cooldowns damage multipliers particle types particle count sound rarity villager prices villager requirements bookshelf radius required bookshelf count enchanting rarity chances maximum enchantments per item messages prefix
================================================== PARTICLES & SOUNDS ==================================================
Every combat enchantment should have unique particles and sounds.
Examples:
Thunderlord:
Lightning + electric particles + thunder sound
Soul Reaper:
Soul particles + sculk/soul sound
Frostbite:
Snowflake-like particles + freeze sound
Void Strike:
Portal/dragon-like particles + teleport sound
Phoenix:
Flame particles + resurrection sound
Do not spam particles every tick.
Use efficient scheduled tasks.
================================================== COOLDOWNS ==================================================
Every active/triggered ability that could be abused must have cooldown support.
Cooldowns must be configurable per enchantment.
Store cooldowns efficiently.
Avoid creating unnecessary repeating tasks.
================================================== PERFORMANCE ==================================================
This plugin will run on a public SMP server.
Optimize for:
- Low CPU usage
- Low memory usage
- No unnecessary repeating tasks
- Event-driven architecture
- Efficient nearby entity detection
- Efficient bookshelf detection
- Efficient cooldown handling
Never scan every loaded block/entity every tick.
Use caching where appropriate.
Clean caches when players leave.
================================================== GUI ==================================================
Create a professional GUI for:
/venchant list
Show:
- Enchantment name
- Rarity
- Max level
- Compatible items
- Description
Clicking an enchantment should show detailed information.
Use a clean SMP-style design.
================================================== MESSAGES ==================================================
Use configurable MiniMessage messages.
Examples:
<green>✔ Custom enchantment applied!
<red>✘ This enchantment cannot be applied to this item.
<yellow>⚡ Thunderlord III activated!
<gray>Cooldown: 8 seconds
================================================== PLUGIN STRUCTURE ==================================================
Use clean OOP architecture.
Suggested structure:
com.vyronmc.enchantments
- VyronEnchantments.java
- enchantment/
- enchantment.impl/
- book/
- villager/
- enchanting/
- anvil/
- command/
- listener/
- gui/
- rarity/
- cooldown/
- config/
- util/
Create an Enchantment interface/base class.
Example:
CustomEnchantment
with methods such as:
getId() getDisplayName() getDescription() getRarity() getMaxLevel() getCompatibleItems() onAttack() onDamage() onBreak() onProjectileHit() onEquip() onUnequip() onKill() onDeath()
Only implement relevant event methods per enchantment.
================================================== IMPORTANT ==================================================
Do NOT create fake placeholder enchantments.
All 60 enchantments must have real functional abilities.
Do NOT use commands as the primary mechanic.
The enchantments must actually work on real Minecraft items.
Make the plugin compile successfully.
Provide:
- Complete source code
- plugin.yml
- config.yml
- enchantments.yml
- messages.yml
- trades.yml
- gui.yml
- README.md
- Build instructions
- Installation instructions
Use Maven or Gradle.
Prefer Maven unless there is a strong reason to use Gradle.
Make the final project directly buildable into a .jar.
Before finishing, check the entire project for:
- compile errors
- missing imports
- API incompatibilities
- duplicate classes
- invalid Material names
- incorrect Paper API usage
- null pointer risks
- event listener issues
- item duplication exploits
- thread-safety problems
The final result must be a professional, production-ready Paper plugin.