Implement a Minecraft 26.3 Java server plugin with two features: (1) enforce a 30-second cooldown on mace use/attack for each player, and (2) Fire Aspect must not affect player targets, while retaining its normal effect on non-player entities. Inspect the generated project structure and use its existing platform APIs and plugin conventions. Ensure the mace cooldown is applied per player and prevents mace attacks/use during the cooldown, with clear player feedback if appropriate. For Fire Aspect, cancel/block the Fire Aspect ignition/damage effect specifically on player victims without disabling unrelated fire damage or other enchantment behavior. Do not add tests. Implement the feature code and any required plugin metadata/configuration; do not attempt to build.

Kodari AI
KodariOct 30 at 9:33 am 1
MaceCooldownAndFireAspectFix
A Minecraft 26.3 Java server plugin implementing two gameplay modifications. First, it enforces a 30-second per-player cooldown on mace attacks and usage, preventing any mace swing or use during the cooldown period with clear chat feedback to the player when the cooldown is active or expires. Second, it modifies Fire Aspect behavior so that the enchantment no longer ignites or applies fire damage to player victims, while preserving its normal ignition effect on all non-player entities such as mobs and animals. The plugin listens to player attack events to track mace usage timestamps per player UUID, cancels mace attacks during cooldown, and intercepts entity damage events to block Fire Aspect fire application specifically when the target is a player. Plugin metadata and configuration are included for server integration.
  1. Create the Paper 26.3 plugin scaffold with a per-player 30-second mace cooldown that blocks attacks and interactions while active.

  2. Cancel Fire Aspect ignition only for player victims, leaving normal damage and effects on non-player entities intact.

Created the Paper 26.3 plugin with a 30-second per-player mace cooldown: the first mace attack starts it, later mace attacks are cancelled, and mace interactions are blocked during the cooldown with feedback. Fire Aspect combustion is cancelled only for player victims; normal damage, unrelated fire damage, and Fire Aspect on non-player entities remain enabled.

No NMS was needed; this uses Bukkit/Paper events. I did not build or run tests.

Kodari can make mistakes. Review important code before using.
Files
src
build.gradle
settings.gradle
Code
5 121
src/main/java/com/kodari/maceguard/MaceGuardPlugin.java
package com.kodari.maceguard;

import org.bukkit.plugin.java.JavaPlugin;

public final class MaceGuardPlugin extends JavaPlugin {
    @Override
    public void onEnable() {
        getServer().getPluginManager().registerEvents(new CombatRestrictionListener(), this);
    }
}