Build the complete GodItems Minecraft server plugin in this project. Target Paper 26.2 and Java 25 (the user confirmed Java 25, overriding the earlier Java 21 mention). The project appears empty, so create all required source and resource files, plugin metadata, and build configuration using the project's standard conventions. Implement a production-ready Bukkit/Paper plugin with no NMS.

Scope and required behavior: 1) Custom items identified by unique PersistentDataContainer IDs (not display names): goditems_crown, goditems_kings_chestplate, goditems_kings_leggings, goditems_kings_boots, goditems_mace, goditems_spear. Display names exactly Crown, Kings Chestplate, Kings Leggings, Kings Boots, God Mace, God Spear. 2) God armor: each piece independently grants its own configurable permanent abilities while actually worn: Crown +10 extra hearts and regeneration; chestplate resistance and fire resistance; leggings strength and speed; boots speed and fire resistance plus double jump. Extra hearts must promptly go away when Crown is removed and health must be safely clamped. Avoid overwriting unrelated potion effects where practical, handle armor swaps, death, respawn, world changes and quit. Prefer event-driven armor updates/effect cleanup over high-frequency polling; if unavoidable, use lightweight checks and clean tasks on disable. Double jump requires configurable cooldown/power, only while boots equipped, must not enable infinite flight or exploit; handle ground/air/jump state safely. 3) Enchantments: every God Armor item gets Protection, Blast Protection, Projectile Protection, Fire Protection, Unbreaking, Mending, with every level configurable. Include powerful configurable extra enchantments per armor item, validating supported enchantments safely. 4) God Mace: configurable powerful enchantments; left click launches player upward with configurable power/cooldown; mark ability-caused fall immunity and clear it safely so it does not give indefinite protection; configurable general fall damage protection while holding mace. Suitable configurable particles and sounds. 5) God Spear: powerful configurable enchantments and abilities; high configurable melee damage; special throw with return-to-owner behavior that avoids item duplication/loss (prefer a controlled projectile/state solution), configurable dash/lunge, special-attack knockback, configurable cooldowns, particles/sounds, and anti-spam. Handle projectile/player lifecycle, logout/death/world change and plugin disable safely. Do not duplicate spears or create unbounded tasks. 6) Recipes: all six items have custom crafting recipes, defined in separate recipes.yml. Configurable enabled switch per recipe, 3x3 shape, ingredients/materials and amounts; validate bad settings and report useful warnings. Bukkit recipes have ingredient material constraints; support configurable ingredient amounts correctly where API allows, or implement safe custom crafting handling to enforce amounts. Prevent duplication/recipe exploits. Reload must replace registered recipes safely. 7) Commands: /goditems give <player> <item> for crown, kingschestplate, kingsleggings, kingsboots, mace, spear; /goditems reload. Admin actions require op or permission. Add permission declarations and tab completion. /kings opens a non-takeable/non-placeable custom inventory GUI listing enabled items and their recipes. Clearly labeled icons; display each recipe's 3x3 layout, required materials and amounts. Configure title, size, item slots/recipe display slots and messages where practical. GUI should refresh/open safely using newly reloaded config and recipes; prevent inventory movement/click/drag exploits. 8) Configuration: detailed config.yml for potion effects/levels, extra hearts, all enchantment levels, double-jump cooldown/power, mace launch/cooldown/fall protection, spear damage/abilities/cooldowns/knockback, particles, sounds, GUI title/size/slots, and messages. Separate recipes.yml for all recipes. Sensible defaults. 9) Provide complete source, plugin.yml, config.yml, recipes.yml, and proper build metadata for Paper 26.2 / Java 25. Use stable API calls supported by Paper 26.2; avoid compile-risky APIs and obsolete version-specific assumptions. Organize code cleanly, guard invalid config, ensure plugin lifecycle/listener/recipe cleanup. No pseudocode or placeholders.

Deliver the implementation in the project source tree. Do not run builds; the workspace lead will compile it. Report briefly what files/features were implemented and any important design notes.

Kodari AI
KodariOct 16 at 8:15 pm 3
GodItemsPlugin
A comprehensive Minecraft Paper plugin that adds six legendary God Items with unique abilities. Crown grants extra hearts and regeneration, chestplate provides resistance and fire protection, leggings enhance strength and speed, boots enable double jump with fire resistance. Mace features powerful launch attacks with fall damage immunity, spear offers throw-and-return mechanics with dash abilities. Includes configurable enchantments, custom crafting recipes, admin commands, and an interactive GUI showcasing all items and recipes.
  1. Create the Paper/Java build and plugin defaults, including separate recipe configuration.

  2. Implement persistent-ID items, configurable armor and weapon abilities, and safe lifecycle cleanup.

  3. Add reloadable recipes, protected recipe GUI, admin commands, and permissions.

Implemented GodItems for Paper 26.2 / Java 25: plugin metadata and build configuration, detailed config.yml, separate recipes.yml, and complete Java sources for persistent-ID items, abilities, recipes, GUI, and commands.

Recipe crafting enforces configured ingredient amounts and consumes them safely. Spear throws use a controlled projectile state that returns the original item on hit, timeout, disconnect, death, or shutdown. Armor effects and health bonuses are cleaned up when gear is removed or the plugin shuts down.

No build was run, as requested.

Add a persistent server-wide singleton limit: at most one legitimate God Item of each type (Crown, Kings Chestplate, Kings Leggings, Kings Boots, God Mace, God Spear) may ever be issued by this plugin. The source is the current GodItems plugin under src/main/java/com/kodari/goditems. Existing flow: ItemFactory.create(item) creates tagged item stacks; GodItemsCommand handles /goditems give and currently creates/gives without limits; RecipeManager registers shaped recipes and its PrepareItemCraftEvent creates preview results, while CraftItemEvent cancels vanilla crafting, consumes exact configured ingredients, then creates/gives one item. GodItemsPlugin constructs ItemFactory/RecipeManager/GUI/AbilityListener and handles reload. AbilityListener removes/returns the same spear during throw, so do not treat that lifecycle as new item issuance.

Implement this cleanly with a new persistent registry/data file in the plugin data folder (e.g. singleton-items.yml), loaded on enable and saved immediately when each item is successfully claimed; claims must survive /goditems reload and server restart. The claim operation must be main-thread-safe/atomic so two nearly simultaneous crafting/give events cannot issue two of one type. Add a service/API that reports claimed state and claims an item exactly once.

Enforce every plugin issuance route:

  • /goditems give must refuse if already claimed, with a clear configurable message; successful give claims before delivery and still safely handles full inventory/drop.
  • crafting preparation should not expose a craftable result when that item's singleton is already claimed (or recipe disabled); CraftItemEvent must re-check availability, cancel, and must not consume ingredients or give anything if claim fails. On a successful craft, consume exact ingredients once, claim once, deliver exactly one item even for shift-click/multicraft.
  • Do not claim items merely for recipe registration/GUI previews; they must not accidentally reserve a singleton. Avoid changing the spear return path, which must preserve the existing claim.
  • Update /kings UI/status so claimed-but-enabled items are clearly marked as already claimed/unavailable, while preserving recipe display behavior.
  • Add sensible default configurable messages in config.yml for already-claimed states and any GUI status needed. Update reload to keep persistent claims and not reset them.

Important: this is deliberately a permanent one-time issuance ledger, rather than attempting to infer that an item was destroyed in lava or scan every offline player's NBT, unloaded chunk, or container. Once claimed it cannot be crafted/given again, even if lost; mention this in the report. Do not add a reset command or silently release a claim. Keep the code compatible with project's Paper 26.2 / Java 25 setup, preserve current features, do not build; workspace lead compiles. Report files/behavior changed briefly.

Kodari AI
KodariOct 16 at 8:23 pm 1
  1. Add a persistent, synchronized singleton-claim registry and initialize it once at startup.

  2. Gate /goditems give and crafting on atomic claims; persist before delivering and keep previews claim-free.

  3. Show claim status in /kings and refresh open menus after a successful claim.

Added the persistent singleton issuance ledger in SingletonItemRegistry.java. Claims are synchronized, written atomically to singleton-items.yml before an item is delivered, and retained across /goditems reload and server restarts.

/goditems give and crafting now refuse already-claimed items; crafting previews hide unavailable results, and successful crafts consume ingredients once and issue exactly one item. /kings marks claimed items as unavailable and refreshes open menus after an issuance. Added configurable claim messages and GUI status text in config.yml.

Claims are permanent: a lost or destroyed item cannot be reissued, and there is no reset command. The spear return path is unchanged. No build was run.

Ismael Zaabat

oke the crafting recepi doesnt work make sure that in the gui drafing recepi in a 3x3 area is and the god prear needs to be an actual spear not an triedent and add an excalibor that takes a heart if u kill som1 if u hold the sword u get strength 2 and just an op sword also make a resource pack so everything looks cool and make the crafting recepi much harder like neth block or like hard to get items

Kodari AI
KodariOct 16 at 10:23 pm 3
  1. Fix recipe crafting and render each recipe as a 3×3 grid in /kings.

  2. Change God Spear to a real spear item, if supported by the target Paper API.

  3. Add Excalibur’s recipe, kill ability, held Strength II, and configurable sword settings.

  4. Resource-pack generation is disabled here; I’ll point you to the project setting to enable it.

  • Fixed recipe matching to accept mirrored patterns while consuming the configured ingredients once; /kings now displays recipes in a true 3×3 grid. Default recipes are significantly harder.

  • God Spear now uses NETHERITE_SPEAR; old config values of TRIDENT are handled as a spear.

  • Added Excalibur with powerful enchantments, Strength II while held, and a configurable heart-steal ability. Heart balances persist in excalibur-hearts.yml and respect configured limits.

  • Added Excalibur to recipes, /goditems give, the Kings GUI, and the singleton issuance ledger.

Texture generation is disabled for this project. Enable it via Settings → Generation to create resource-pack art. No build was run.

Ismael Zaabat

make sure the armor also uses netherite and after 24 hours the player that got killed wil get his health back and the pleyer who killed loses the heart that he stole also when u hold the mace ur completly imune to cpvp and ancor pvp also add some cool trims to the god armor

Kodari AI
KodariOct 16 at 10:28 pm 2
  1. Make the God armor netherite and apply distinctive trims.

  2. Add a 24-hour heart-steal expiry that restores the victim and removes the killer’s stolen heart.

  3. Make holding the God Mace protect against crystal and anchor PvP.

  1. God armor is now forced to Netherite, including for existing configs, and gets distinct configurable trims.

  2. Excalibur heart steals are recorded persistently. After 24 hours, the victim’s maximum heart is restored and the killer loses the transferred heart, even if either player is offline or the server restarts.

  3. Holding the God Mace cancels damage from End Crystal and respawn-anchor explosions.

No build was run.

Ismael Zaabat

how do i make recorce pack for this

Kodari AI
KodariOct 16 at 10:31 pm 1

Texture generation is currently disabled for this project. Click the Settings button → Generation → enable it, then ask me to create textures for the God armor, spear, mace, and Excalibur. You can enable it for all projects at kodari.ai/settings?tab=features.

Ismael Zaabat

oke make the recource pack

Kodari AI
KodariOct 16 at 10:40 pm 21
  1. Create unique artwork for the seven GodItems.

  2. Add resource-pack models and metadata, then assign those models to the plugin’s items.

Created the resource pack in resource-pack/ with custom artwork and models for the Crown, armor pieces, God Mace, God Spear, and Excalibur. The plugin now assigns those models to the items it creates.

Zip the contents of resource-pack/ and install or distribute that pack to players; the plugin does not serve it automatically. The armor has custom inventory icons, while worn armor keeps its Netherite appearance and the configured trims. No build was run.

Kodari can make mistakes. Review important code before using.
Files
resource-pack
src
build.gradle
settings.gradle
Code
36 2,094
src/main/java/com/kodari/goditems/GodItemsPlugin.java
package com.kodari.goditems;

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

public final class GodItemsPlugin extends JavaPlugin {
    private ItemFactory itemFactory;
    private RecipeManager recipeManager;
    private GuiManager guiManager;
    private AbilityListener abilityListener;
    private SingletonItemRegistry singletonItemRegistry;
    private ExcaliburHeartManager excaliburHeartManager;

    @Override
    public void onEnable() {
        saveDefaultConfig();
        if (!getDataFolder().exists() && !getDataFolder().mkdirs()) {
            getLogger().severe("Could not create plugin data folder.");
        }
        if (!new java.io.File(getDataFolder(), "recipes.yml").exists()) saveResource("recipes.yml", false);
        singletonItemRegistry = new SingletonItemRegistry(this);
        singletonItemRegistry.load();
        itemFactory = new ItemFactory(this);
        excaliburHeartManager = new ExcaliburHeartManager(this, itemFactory);
        excaliburHeartManager.load();
        recipeManager = new RecipeManager(this, itemFactory, singletonItemRegistry);
        recipeManager.reload();
        guiManager = new GuiManager(this, itemFactory, recipeManager, singletonItemRegistry);
        abilityListener = new AbilityListener(this, itemFactory);
        Bukkit.getPluginManager().registerEvents(recipeManager, this);
        Bukkit.getPluginManager().registerEvents(guiManager, this);
        Bukkit.getPluginManager().registerEvents(abilityListener, this);
        Bukkit.getPluginManager().registerEvents(excaliburHeartManager, this);
        excaliburHeartManager.applyToOnlinePlayers();
        GodItemsCommand command = new GodItemsCommand(this, itemFactory, guiManager, singletonItemRegistry);
        registerCommand("goditems", command);
        registerCommand("kings", command);
    }

    private void registerCommand(String name, GodItemsCommand executor) {
        PluginCommand command = getCommand(name);
        if (command == null) {
            getLogger().severe("Command '" + name + "' is missing from plugin.yml.");
            return;
        }
        command.setExecutor(executor);
        command.setTabCompleter(executor);
    }

    public void reloadPlugin() {
        reloadConfig();
        recipeManager.reload();
        abilityListener.reloadEffects();
        guiManager.refreshOpenMenus();
    }

    public SingletonItemRegistry getSingletonItemRegistry() {
        return singletonItemRegistry;
    }

    public void refreshOpenMenus() {
        if (guiManager != null) guiManager.refreshOpenMenus();
    }

    @Override
    public void onDisable() {
        if (abilityListener != null) abilityListener.shutdown();
        if (excaliburHeartManager != null) excaliburHeartManager.shutdown();
        if (recipeManager != null) {
            for (GodItem item : GodItem.values()) {
                Bukkit.removeRecipe(new org.bukkit.NamespacedKey(this, "goditems_" + item.id()));
            }
        }
    }
}