Create a Minecraft server plugin inspired by Enchain SMP: allow all vanilla enchantments on every item, including normally incompatible combinations, and implement their effects across item types wherever technically feasible. In particular a Riptide sword or mace should launch the player like a Riptide trident, and Wind Burst on those weapons should trigger its upward burst on successful attacks, including when combined with Riptide. Preserve vanilla levels and appropriate triggers/cooldowns/environmental conditions where practical; avoid duplicating effects that Minecraft already applies natively. Support obtaining/applying enchantments through normal gameplay mechanisms as feasible and provide a permission-protected command for applying arbitrary vanilla enchantments to the held item, with usage and tab completion. Handle special cases and conflicts safely. Include plugin metadata and concise documentation of commands, permissions, mechanics, and any enchantment effects or vanilla interactions that cannot be generalized via the server API. Feature code only.

Kodari AI
KodariNov 6 at 7:56 am 2
EnchantEverything
A Minecraft Spigot plugin enabling all vanilla enchantments on any item, including normally incompatible combinations. Riptide on swords or maces launches players like tridents, while Wind Burst triggers upward bursts on successful melee attacks, stacking with Riptide. Preserves vanilla levels, triggers, cooldowns, and environmental conditions where feasible, avoiding duplicate native effects. Supports normal gameplay application through anvils and enchanting tables, plus a permission-protected /enchantall command with tab completion for applying arbitrary vanilla enchantments to held items. Safely handles conflicts and special cases, with comprehensive documentation of mechanics and API limitations.
  • Add an anvil path and a permission-protected command for unrestricted vanilla enchantments.

  • Implement non-native Riptide and Wind Burst behavior without duplicating native effects.

  • Document the supported mechanics and server API limitations.

Created the plugin with unrestricted anvil combinations, /enchain, Riptide launches for swords and maces, and an approximated Wind Burst effect for swords.

Limitation: Other enchantments can be applied to any item, but their effects are not generalized across item types; Minecraft determines whether they work. The README documents the mechanics and limitations.

The initial implementation only emulates Riptide on swords/maces and Wind Burst on swords; user explicitly wants vanilla enchantment effects generalized to every item wherever feasible. Extend existing EnchantListener and related code substantially: make Riptide work on any non-trident held item and Wind Burst on any non-mace held item with appropriate vanilla-like triggers; implement as many other vanilla enchantment effects across normally unsupported held items/equipment as practical using Paper 1.21.4 events, avoiding double application on native-supported items, preserving level scaling and appropriate triggers. Cover combat, protection, mining, durability, movement and projectile effects where feasible without breaking vanilla. Consider enchantment table support where technically feasible, and keep anvil/command behavior. Do not claim unsupported mechanics work; update README with specific supported and unsupported effects and limitations. Feature code only.

Kodari AI
KodariNov 6 at 7:56 am 1
  1. Extend Riptide and Wind Burst to other held items.

  2. Generalize practical combat, equipment, mining, durability, movement, and projectile effects.

  3. Assess enchantment-table support and update the mechanics documentation.

[Generation stopped]

Continue the existing Universal Enchants plugin. User requests Minecraft 26.2 and all other vanilla enchantments to work across items. Update build.gradle Paper API dependency and plugin metadata to target Paper/Minecraft 26.2, adapting Java toolchain and API usages as needed. Existing code targets Paper 1.21.4. Generalize every vanilla enchantment's actual effects to every item where technically possible, not merely allowing application: make Riptide work on any non-trident held item and Wind Burst on any non-mace held item, including both together; cover combat, armor/protection, tools/mining, durability, movement, projectiles and other vanilla enchantments with appropriate triggers and level scaling. Avoid duplicating effects Minecraft already applies; retain anvil/command behavior and support normal enchantment acquisition where feasible. Be realistic about API limitations and document specifically any mechanics that cannot be generalized or require an appropriate context; do not falsely claim universal functionality. Update README for 26.2, commands, permissions, and supported/limited mechanics. Feature code only.

Kodari AI
KodariNov 6 at 7:59 am 5
  1. Update the project for Paper 26.2.

  2. Extend enchantment effects and acquisition where the server API allows.

  3. Document supported effects and precise limitations.

Updated the project to target Paper 26.2 and Java 25. Riptide now works on non-trident main-hand items; Wind Burst is left to Minecraft’s native post-attack effect to avoid duplication.

Not complete: I did not implement universal cross-item effects for every enchantment. The README identifies which effects depend on vanilla slots or item-specific contexts. The build and gameplay behavior have not been verified.

Continue the existing EnchantEverything/EnchainInspired Paper 26.2, Java 25 plugin. The user wants more vanilla enchantment EFFECTS to work across different items, and a visible Riptide wind-up on swords and other items like a trident. Existing code in com.kodari.enchain.EnchantListener allows unrestricted anvil enchantments and instantly launches a non-trident main-hand Riptide item; /enchain already applies enchantments, and README describes native Wind Burst. Implement actual additional effects, not just the ability to attach enchantments.

Riptide: replace the instant non-trident launch with a vanilla-like short charge/wind-up for Riptide items, with visible sword/hand feedback and appropriate sound/particles or an action-bar indicator. Prefer a genuine hold-then-release charge with a trident-like use pose if the Paper 26.2 API and unmodified client support it safely on arbitrary items. Do not assume ordinary swords send a release-use event or overwrite an item's existing components/usability to fake it. If true hold/release or the trident pose is not safely available for arbitrary items, implement a clearly visible timed wind-up followed by an automatic launch instead, and document the actual controls and animation limitation honestly. Use the vanilla 26.2 charge timing if practical. Apply to any non-trident held item, including swords and maces, ideally both hands without double triggering; native tridents must keep their vanilla behavior. Respect wet/rain requirements, cooldown and level scaling; cancel the charge when its item or hand changes, the player becomes ineligible, logs out/dies, or the plugin disables, and spend durability only on successful launch. Do not break protected/cancelled interactions, regular block use, or other items when Riptide is not being activated. Account for vanilla's pre-cancelled right-click-air events rather than inadvertently disabling activation in air. Preserve the existing Wind Burst + Riptide sword behavior without double-applying a native 26.2 Wind Burst effect.

Add several meaningful cross-item effects, beyond native enchantment support. At minimum, make Protection, Fire Protection, Blast Protection, Projectile Protection, Feather Falling and Thorns on held or otherwise non-native-slot equipment affect the player in their appropriate situations. Count only actually held/worn equipment, exclude equipment/slots where Minecraft already applies that effect, honor event cancellation, prevent damage-event recursion, and handle vanilla protection stacking/caps as closely as the API permits without duplicating native mitigation. Also implement additional distinct effects where safely possible, prioritizing Respiration, Aqua Affinity, Depth Strider, Swift Sneak, Soul Speed, and Channeling on otherwise unsupported items with their appropriate contexts, level scaling, and safe cleanup of any temporary attribute modifiers. Do not silently invent conflicting controls, bypass protection plugins, modify other plugins' attributes, permanently change player state, or claim effects are universal when they require a context. Where Minecraft 26.2 already applies an effect on a given item/slot, use the native effect rather than applying it twice. Preserve command/anvil support and compatibility with Paper 26.2 and Java 25; use the Paper API without requiring a resource pack or external plugin if possible.

Update README.md to explain the wind-up controls, what animation is actually possible, which added enchantment effects work on non-native items/equipment and their triggers, which effects are native, and remaining limitations. Feature code only.

Kodari AI
KodariNov 6 at 8:14 am 5
  1. Replace instant Riptide with a cancellable, visible charge.

  2. Add safe cross-slot protection and other feasible effects.

  3. Update the README with controls and limitations.

Added a visible, automatic Riptide charge for non-trident items in either hand, plus held-item protection and cross-slot Respiration, Aqua Affinity, Depth Strider and Swift Sneak effects. Thorns is left to Minecraft’s native equipment-slot handling.

The README documents the controls and limitations. Soul Speed and Channeling were not generalized, and the build and gameplay behavior have not been verified.

Expand the existing EnchantEverything / EnchainInspired Minecraft plugin with more actual vanilla enchantment effects on items and equipment that cannot normally use them. The user previously asked for all enchantments to work on every item and now asks for more support. Project targets Paper 26.2 / Java 25; retain that target. Read the existing src/main/java/com/kodari/enchain/EnchantListener.java, EnchainPlugin.java and README.md first. It already supports unrestricted anvil/command application, non-trident Riptide wind-up, native Wind Burst, held-item protections, and cross-slot Respiration, Aqua Affinity, Depth Strider and Swift Sneak. Do not merely add the enchantment to items; implement new effects while preserving those mechanics.

Implement at least these additional features:

  1. Soul Speed on held items and worn non-feet equipment: while on applicable soul blocks, give the vanilla-like level-scaled movement benefit, respecting any existing native boots effect rather than duplicating it. Use the 26.2 enchantment data and appropriate plugin-owned transient attribute modifier(s), update as equipment/terrain changes, and clean up on quit/disable. Only actually held/worn items count, never items in ordinary inventory. Do not change other plugins' modifiers or leave permanent speed changes.
  2. Channeling on an arbitrary Channeling-enchanted main-hand item: on a successful direct melee hit during a thunderstorm against a sky-exposed target, trigger a real vanilla-like lightning strike, including on a sword or mace. This is an added melee trigger, not a claim that vanilla tridents work that way. Do not duplicate native thrown-trident Channeling, trigger on sweep/projectile/lightning damage, or strike after a cancelled hit. Respect the normal cancellable lightning event and protection plugins; avoid recursion or duplicate strikes. Document any necessary cooldown and the fact that real lightning can cause damage/fire.
  3. Add additional meaningful cross-item support as feasible, prioritizing Frost Walker on non-feet held/worn equipment and offensive enchants from non-main-hand equipment (Sharpness, Smite, Bane of Arthropods and Fire Aspect). For Frost Walker, use vanilla-style level/radius and conditions, and only freeze appropriate source water with cancellable entity block-form events; ice must melt safely, with no overwriting later player changes, no protection bypass, and no permanent plugin-owned terrain after unload/disable. If the API cannot support this safely, leave it unimplemented and document why rather than risking world corruption. For the offensive enchants, only add the bonuses from non-native slots on appropriate direct melee hits, use vanilla scaling/entity tags and relevant status/fire events, respect cancellation, and do not reapply the main-hand effects that Minecraft 26.2 already handles. Consider Power/Punch/Flame from other equipped items on real bow/crossbow shots if safely supported without manufacturing ammo or duplicating launcher effects.

Use Paper's native effects wherever they already work, honor cancelled combat/block/projectile events and other plugins, and do not break the existing Riptide controls, Wind Burst, anvil or /enchain command. Limit levels and stacking appropriately; handle native and extra sources together without double-applying an enchant. Prioritize correctness and meaningful features over unsafe approximations. Update README.md with each newly supported effect, actual slot/trigger requirements and scaling/limitations, plus which requested effects are still unsupported; do not claim universal support. Feature code only.

Kodari AI
KodariNov 6 at 8:18 am 3
  1. Add terrain-aware Soul Speed and safe modifier cleanup.

  2. Add direct-melee Channeling and feasible cross-slot combat effects.

  3. Document supported effects and limitations.

Added cross-slot Soul Speed and main-hand melee Channeling, and updated the README with their triggers and limitations.

Frost Walker and the requested cross-slot offensive and projectile enchantments remain unsupported. Build and gameplay behavior have not been verified.

Follow up on the previous EnchantEverything Paper 26.2 / Java 25 task. Your report said: "Frost Walker and the requested cross-slot offensive and projectile enchantments remain unsupported." Soul Speed and Channeling now compile, but the requested additional combat support is unfinished. Read src/main/java/com/kodari/enchain/EnchantListener.java and README.md first.

Implement cross-item melee support for Sharpness, Smite, Bane of Arthropods and Fire Aspect on non-native equipped slots (offhand and worn items) as practical, not merely enchantment application. On appropriate successful direct melee hits, add level-scaled damage/effects from non-native equipment; distinguish undead and arthropod targets using Paper/Minecraft entity tags or another accurate current 26.2 API, and use the actual 26.2 enchantment conditions/scaling. Keep existing vanilla main-hand effects and don't apply them twice. Define sensible capped/strongest-level behavior when the same enchantment occurs in multiple equipped slots; use only actually equipped items. Respect cancelled/zero-damage events, other plugins' cancellable fire and potion events, normal attack cooldown scaling as closely as Paper permits, and do not cause recursive damage or affect sweep/projectile hits. Avoid replacing stronger or longer effects from elsewhere. If Bane's slowness or Fire Aspect cannot be implemented safely with cancellable events, implement the safe damage support and document the limitation instead.

If practical and safe, additionally extend Power, Punch or Flame from non-native equipment to real bow/crossbow-fired projectiles without manufacturing ammo or duplicating the launcher's native effects; otherwise document these as unsupported. Frost Walker was previously left out for terrain/protection safety; do not implement an unsafe approximation. Preserve Riptide, Soul Speed, Channeling, anvil and command behavior. When cleaning up after a player quits, also remove all plugin-owned transient Respiration, Aqua Affinity, Depth Strider and Swift Sneak modifiers as well as Soul Speed; never touch other plugins' modifiers. Update README.md with the exact new supported slots, stacking, triggers and limitations. Feature code only.

Kodari AI
KodariNov 6 at 8:21 am 4
  1. Add safe cross-slot melee enchantment effects.

  2. Clean up all plugin-owned transient modifiers on quit.

  3. Update the README with supported effects and limitations.

  • Added cross-slot Sharpness, Smite and Bane of Arthropods melee effects, including Bane’s slowness.

  • Added quit cleanup for all plugin-owned transient attribute modifiers.

  • Updated the README with stacking, triggers and limitations. Cross-slot Fire Aspect, projectile enchantments and Frost Walker remain unsupported.

Build and gameplay behavior have not been verified.

Fix a runtime dependency problem in the just-added cross-slot Bane of Arthropods support. In src/main/java/com/kodari/enchain/EnchantListener.java, line 3 imports com.cryptomorin.xseries.XPotion and the Bane hit handler calls XPotion.matchXPotion("SLOWNESS"), but build.gradle declares only the Paper API, the project has no manifest.kod or bundled XSeries source, and Paper itself need not provide XSeries. Although compilation succeeded in the workspace, a standalone server can fail with NoClassDefFoundError when Bane triggers. Remove XSeries completely and create the Slowness IV effect using the native Paper 26.2 PotionEffectType.SLOWNESS or the native potion-effect registry and PotionEffect. Preserve the existing duration/level, stronger-or-longer-effect protection, normal cancellable potion-effect event, and cancelled/dead target checks. Do not introduce another external dependency. Preserve the other mechanics and README. Feature code only.

Kodari AI
KodariNov 6 at 8:21 am 1
  • Replace the XSeries lookup with Paper’s native Slowness effect.

  • Preserve the existing checks and effect duration.

Replaced XSeries with Paper’s native Slowness effect. Existing duration, effect protection, and cancellation checks are preserved; no dependency was added.

Make a substantial expansion to the existing EnchantEverything / EnchainInspired Minecraft plugin. The user wants as many vanilla enchantment EFFECTS as possible to work on arbitrary item types, not merely the ability to attach enchantments, and is happy for this to be a thorough, larger task. Target Paper 26.2 and Java 25. First read src/main/java/com/kodari/enchain/EnchantListener.java, EnchainPlugin.java, EnchantCommand.java and README.md. The current plugin has unrestricted anvil and /enchain application; a non-trident Riptide wind-up; native Wind Burst; held protection; cross-slot Respiration, Aqua Affinity, Depth Strider, Swift Sneak, Soul Speed, Sharpness, Smite and Bane; and main-hand melee Channeling. Preserve those features, /enchain, and enchain.apply.

Work systematically through the Paper/Minecraft 26.2 vanilla enchantment registry and data, not just one or two entries. Add a broad set of actual new cross-item enchantment effects, prioritizing the following and continuing down the list instead of stopping at the first milestone. Aim to deliver many distinct new effects, subject to safe API support:

  1. Combat: extend Fire Aspect, Knockback and Sweeping Edge from non-native equipped slots to appropriate real melee/sweep hits. Use vanilla 26.2 conditions and level scaling, only add the difference beyond a native main-hand effect, use sensible strongest-level caps, respect attack cooldown as practicable, and keep sweep separate from direct hits. Use the normal cancellable combustion and knockback/velocity mechanisms where available, do not shorten another effect, and only perform side effects following a confirmed uncancelled hit. Also implement Impaling on appropriate targets and consider Density and Breach on otherwise unsupported equipment, using actual 26.2 entity tags, fall/armor conditions, event APIs, and native scaling; do not add the main-hand effect again if Minecraft already applied it. Extend existing melee Channeling to suitable non-main-hand equipped items if this can be done without duplicate strikes.
  1. Projectiles: add Power, Punch, Flame and Piercing from otherwise unsupported equipped items to genuine player bow/crossbow arrow shots where the API safely permits. Account for which hand actually fired, including an off-hand bow with an enchanted sword in the main hand; snapshot equipment at the shot and use native arrow properties and vanilla scaling. Add only the extra effect beyond what the launcher already applied, respect cancellation and other plugins, and do not create free arrows or fire extra projectiles. Explore Infinity, Multishot and Quick Charge if the 26.2 API supports their normal behavior without duplicating ammunition, breaking existing launchers, or bypassing protection; otherwise clearly document the precise limit.
  1. Mining and fishing: extend Efficiency from otherwise non-native held/worn items to real mining using the appropriate vanilla 26.2 player attribute and its conditions, with only plugin-owned transient modifiers and no fake block breaks or drop multiplication. Explore Fortune, Silk Touch and Looting through safe native loot-context APIs; never duplicate or replace other plugins' drops or bypass block protection. Extend Lure and, if the API permits it safely, Luck of the Sea from other equipped items to genuine fishing-rod hooks with the vanilla timing/luck behavior; do not manufacture fish or catch loot.
  1. Movement and protection: explore Frost Walker on non-feet held/worn items using appropriate source-water and radius conditions, cancellable entity block-form events, and vanilla temporary frosted-ice behavior. Only implement it if temporary ice will melt safely across chunk unload/restart/disable, without overwriting later player changes, force-loading chunks, or bypassing protection; otherwise explain the blocker. Also extend held Fire Protection's burn-duration and Blast Protection's explosion-knockback effects if the appropriate cancellable APIs allow safe, non-duplicated behavior.
  1. Review every other vanilla 26.2 enchantment, including any newly introduced ones, for similarly safe opportunities on arbitrary items. Mending, Unbreaking, Thorns, curses, trident/spear effects and fishing/projectile effects have specific contexts: use Minecraft's existing native behavior wherever it already works and do not double it. Where an action inherently requires a projectile, fishing rod, damageable item or another context, either provide a genuinely safe, clearly documented activation that does not interfere with existing controls/resources or state the limitation; do not silently claim the effect works on every item. Never duplicate/lose gear, grant free ammunition or drops, or add an external runtime library.

Across all features, count only actually held/worn equipment unless a different context is explicitly documented; honor cancelled events and other plugins; use the native enchantment's vanilla max and carefully handle multiple sources; do not mutate events at MONITOR, cause recursive damage, break Riptide/Wind Burst, or leave tasks, transient modifiers or state on quit/disable. Use existing vanilla effects rather than duplicating them. Organize new helpers/listeners as needed. Update README.md with an accurate per-enchantment or grouped status covering newly generalized triggers/slots, native-only behavior, stacking, relevant controls and remaining API/context limitations. Continue implementing as many as safely feasible; if a particular mechanic really cannot be generalized safely, skip that mechanic and give the reason rather than using a dangerous approximation. Feature code and documentation only.

Kodari AI
KodariNov 6 at 8:28 am 5
  1. Review the existing mechanics and 26.2 enchantment data.

  2. Extend safe combat and projectile effects.

  3. Add feasible mining, fishing and movement effects.

  4. Document supported triggers and remaining limitations.

Added cross-slot Impaling, Fire Aspect, Sweeping Edge, Efficiency and arrow Piercing, plus Channeling from worn and offhand equipment. Updated the README with triggers, stacking and limitations.

The expansion remains incomplete: Knockback, projectile Power/Punch/Flame, fishing extensions and several other requested effects are still native-only or unsupported. Build and gameplay behavior have not been verified.

Continue the existing EnchantEverything Paper 26.2 / Java 25 plugin. Read EnchantListener.java, EnchainPlugin.java and README.md first. The user wants as many more actual cross-item enchantment effects as safely possible, and specifically: right-click an item enchanted with Multishot to shoot swords carrying its current enchantments EXCEPT Multishot. Implement this custom feature plus a substantial expansion of enchantment effects; do not merely make enchantments attachable.

Custom Multishot: on right-click air with a non-bow/non-crossbow item bearing Multishot in either hand, fire a vanilla-like spread of three sword-looking projectiles. They must visibly look like swords to unmodified clients; use safe projectile entities with item-display passengers or an equivalent native Paper API visual, not collectible dropped equipment. Snapshot all source-item enchantments except Multishot at launch and apply their relevant supported projectile/impact effects on targets, e.g. Sharpness/Smite/Bane/Impaling, Fire Aspect, Channeling, Wind Burst or other effects where meaningful and safely feasible; don't promise effects that lack a projectile context. Make it clear in the README which effects work for these custom swords. Never grant or drop free swords or duplicate the source item, inventory, enchantment data, ammo or loot. Attribute damage to the shooting player and pass through normal cancellable damage/protection events. Avoid hitting the shooter or invoking effects on cancelled/zero damage hits, recursive triggers and duplicate native effects. Remove displays and projectiles on collision, timeout, player quit and plugin disable, including chunk unload handling; no persistent/leaked entities, duplicate on reload or tasks. Apply a reasonable cooldown and source-item durability cost on successful shot where applicable, respecting creative and break events. Preserve vanilla Multishot behavior on bows/crossbows and avoid unintended block activation/protected events. Precisely define conflicts with existing Riptide right-click: Riptide should take precedence when its wet conditions are met; Multishot fires otherwise, without double-triggering either action. Handle pre-cancelled right-click-air semantics safely. Do not require resource packs or external runtime dependencies.

Broader support: systematically review existing README and current Paper 26.2 enchantments; implement as many meaningful missing effects as safely feasible, not only Multishot. Prioritize non-native-slot Power, Punch, Flame for genuine bow/crossbow arrows; Knockback, Density and Breach for real melee where reliably implementable; Lure/Luck of the Sea on genuine fishing hooks using proper timing/luck APIs; held Fire Protection burn duration and Blast Protection knockback; safe appropriate support for other native effects. Consider Frost Walker only if cancellable block formation and native temporary frosted-ice lifecycle safely handle protection, unload/restart and other players' changes. Do not duplicate native launcher/main-hand/equipment effects; use strongest-level capped stacking or carefully documented alternatives, appropriate vanilla triggers/scaling, actual equipped slots only, cancellable events and safe modifier/task cleanup. Never bypass protections or create free ammo, drops, permanent world edits or inventory items. Preserve current combat, Channeling, Riptide, Wind Burst, anvil and command mechanics. Skip and explain any effect impossible to safely generalize rather than fake universal support.

Update README with controls, exact custom sword behavior and supported inherited enchantments, cooldown/durability and Multishot+Riptide interaction, all newly generalized enchantments and their limitations, and honest remaining limitations. Feature code and documentation only.

Kodari AI
KodariNov 6 at 3:22 pm 7
  1. Review the existing listener, lifecycle and documented mechanics.

  2. Add custom Multishot swords with cleanup, durability and Riptide precedence.

  3. Extend other effects where Paper supports them safely.

  4. Update the README with controls and limitations.

Added custom Multishot sword volleys, plus cross-slot Power, Flame and Lure. The README documents controls, inherited effects and remaining limitations.

The broader expansion remains incomplete: Punch, Knockback, Density, Breach and the other requested candidates were not generalized. The changes have not been verified by a build or gameplay test.

Kodari can make mistakes. Review important code before using.
Files
src
build.gradle
README.md
settings.gradle
Code
8 814
src/main/java/com/kodari/enchain/EnchainPlugin.java
package com.kodari.enchain;

import org.bukkit.Bukkit;
import org.bukkit.plugin.java.JavaPlugin;

public final class EnchainPlugin extends JavaPlugin {
    private EnchantListener listener;
    private SwordVolley swordVolley;

    @Override
    public void onEnable() {
        EnchantCommand command = new EnchantCommand();
        getCommand("enchain").setExecutor(command);
        getCommand("enchain").setTabCompleter(command);
        listener = new EnchantListener(this);
        Bukkit.getPluginManager().registerEvents(listener, this);
        swordVolley = new SwordVolley(this);
        Bukkit.getPluginManager().registerEvents(swordVolley, this);
    }

    @Override
    public void onDisable() {
        if (listener != null) listener.close();
        if (swordVolley != null) swordVolley.close();
    }
}