zenphayt

PROJECT: VOIDREAPER

Professional Minecraft Paper Plugin — Complete Development

Act as an expert Minecraft Java Plugin Developer, Paper API Engineer, Gameplay Systems Developer, and Minecraft Particle/VFX Specialist.

Build a complete, production-quality Minecraft plugin named VOIDREAPER.

This is a complete plugin development project, NOT a prototype or demonstration.

IMPORTANT:

Do not develop or generate a resource pack or texture pack.

Focus entirely on the actual plugin, gameplay mechanics, damage systems, particle effects, animations, sounds, and stability.

The final output must include:

  1. A compiled, functional VOIDREAPER.jar.
  2. Complete editable Java source code.
  3. All configuration files.
  4. Maven or Gradle build files.
  5. Installation and configuration instructions.
  1. SERVER COMPATIBILITY

Target platform: Paper.

Required Minecraft versions: 1.21.1 through 1.21.11 inclusive.

Requirements:

  • Java-based Paper plugin.
  • Use appropriate Java and Paper API versions.
  • Handle API differences between supported Minecraft versions.
  • Use version-specific compatibility adapters if required.
  • Do not claim a version is supported unless it has been tested.
  • Avoid unnecessary dependencies.
  • Plugin must start without errors.
  • Plugin must shut down cleanly.
  • No client-side mods or resource packs required.
  1. CUSTOM ITEM: VOIDREAPER

Item name: §5§lVOIDREAPER

Lore: §8The Power Beyond Reality

Design identity:

  • Dark purple and black.
  • Legendary cosmic Mace.
  • Obsidian-inspired appearance using vanilla item materials.
  • Purple energy particles.
  • Unique glowing visual effects.
  • Dark magical atmosphere.

IMPORTANT:

The actual custom item must be identifiable through PersistentDataContainer (PDC).

Do not identify VOIDREAPER using display name alone.

Normal Minecraft Maces must remain completely unaffected.

Requirements:

  • Custom item identifier.
  • Safe item persistence.
  • Correct identification after inventory movement, dropping, picking up, and storage.
  • No accidental conversion of ordinary Maces.
  • Custom item acquisition through admin command.
  • Prevent unintended duplication.
  1. PASSIVE ABILITIES

All passive abilities must be fully implemented.

A. VOID AURA

A continuous cosmic aura around the player holding VOIDREAPER.

VISUAL EFFECTS:

  • Dark purple particles.
  • Violet soul particles.
  • Rotating particle circles.
  • Small floating energy fragments.
  • Expanding purple rings.
  • Occasional dark magical bursts.

FUNCTIONAL EFFECTS:

  • Detect eligible nearby hostile entities.
  • Apply configurable damage over time.
  • Apply configurable debuffs.
  • Never damage the weapon holder.
  • Respect PvP settings.
  • Respect protected regions.
  • Do not repeatedly damage the same target every tick.

CONFIGURATION:

  • Aura radius.
  • Damage interval.
  • Damage amount.
  • Maximum targets.
  • Particle density.
  • Debuff duration.

B. DIVINE PROTECTION

FUNCTION:

  • Reduce incoming damage by a configurable percentage.
  • Apply a defensive effect when the holder receives damage.
  • Add configurable cooldown.
  • Prevent repeated activation exploits.

VISUALS:

  • Purple protective shield effect.
  • Rotating energy circle.
  • Expanding protective ring.
  • Purple magical sparks.
  • Activation sound.

C. SOUL ABSORPTION

FUNCTION:

  • Detect eligible entity deaths caused by VOIDREAPER.
  • Grant soul-energy charges.
  • Prevent duplicate soul rewards.
  • Store charges safely.
  • Provide configurable regeneration or absorption benefits.
  • Enforce maximum soul capacity.

VISUALS:

  • Purple soul particles.
  • Energy orb moving toward the holder.
  • Absorption animation.
  • Unique sound.

D. GRAVITY MASTER

FUNCTION:

  • Manipulate nearby eligible entities' movement.
  • Controlled upward and downward movement.
  • Configurable radius and duration.
  • Prevent accidental caster targeting.
  • Handle fall damage safely.
  • Respect protected regions.

VISUALS:

  • Rotating purple gravity field.
  • Floating particles.
  • Expanding rings.
  • Dark violet energy fragments.
  1. ACTIVE ABILITIES

This section is the highest priority.

Previously, abilities activated but did not deal damage, and their visual effects were missing.

This must never be considered a completed implementation merely because the activation event works.

Every active ability must have:

  • Input detection.
  • Item verification.
  • Cooldown verification.
  • Actual gameplay logic.
  • Target detection.
  • Actual damage or status effects.
  • Particle animations.
  • Sound effects.
  • Proper cleanup.
  • Error handling.

ACTIVE 1: BLACK HOLE

Activation: Right-click while holding VOIDREAPER.

CONCEPT:

Create a dramatic purple-black cosmic singularity.

VISUAL ANIMATION:

PHASE 1 — SUMMONING

  • Purple particles gather at the target location.
  • A dark energy sphere starts forming.
  • Multiple circular particle rings appear.
  • Violet sparks spiral inward.
  • Deep summoning sound.

PHASE 2 — FORMATION

  • Create a large dark central sphere using supported Minecraft display entities or particle techniques.
  • Multiple purple rings rotate around it.
  • Add layered violet particles.
  • Add a bright purple outer boundary.
  • Create a visually convincing accretion-disk effect.

PHASE 3 — GRAVITY

  • Detect nearby eligible entities.
  • Pull them gradually toward the center.
  • Apply configurable damage at controlled intervals.
  • Exclude the caster.
  • Do not affect protected regions.
  • Do not destroy blocks.

PHASE 4 — COLLAPSE

  • Shrink the energy rings.
  • Pull particles toward the center.
  • Create a powerful violet implosion.
  • Finish with a dramatic purple burst.

Important:

Do not simply spawn a few particles and call it a black hole.

The animation must be layered, continuous, and visually recognizable.

ACTIVE 2: GOD'S WRATH

Activation: Shift + Right-click.

CONCEPT:

A powerful celestial energy strike.

VISUAL ANIMATION:

PHASE 1 — CHARGING

  • Purple energy surrounds the caster.
  • Multiple rotating rings.
  • Violet runes made from particles.
  • Charging sound.

PHASE 2 — TARGETING

  • A visible circular target marker.
  • Vertical purple particle column.
  • Short warning animation.

PHASE 3 — IMPACT

  • Descending purple energy column.
  • Lightning-like visual effects.
  • Expanding impact ring.
  • Large violet particle explosion.

FUNCTION:

  • Apply actual configurable area damage.
  • Apply controlled knockback.
  • Detect valid targets.
  • Exclude caster.
  • Respect PvP and region protections.
  • Never destroy blocks.

PHASE 4 — AFTERMATH

  • Fading purple energy circle.
  • Floating particles.
  • Impact sound and final visual burst.

ACTIVE 3: TIME BREAKER

Activation: Shift + Left-click.

CONCEPT:

Temporarily manipulate time in an area.

VISUAL ANIMATION:

PHASE 1 — ACTIVATION

  • Purple clock-inspired particle patterns.
  • Rotating energy circles.
  • Expanding violet wave.
  • Unique activation sound.

PHASE 2 — TIME FREEZE

  • Visible purple area boundary.
  • Suspended particle patterns.
  • Dark violet energy rings.
  • Distinct visual indication around affected entities.

FUNCTION:

  • Temporarily slow or immobilize eligible entities.
  • Use configurable duration.
  • Prevent affecting the caster.
  • Store and restore relevant entity states safely.
  • Ensure all effects expire.
  • Respect PvP and region protections.

PHASE 3 — RELEASE

  • Expanding purple ring.
  • Large energy burst.
  • Restore normal movement.
  • Unique release sound.
  1. INPUT SYSTEM

Implement these exact controls:

Right-click = BLACK HOLE

Shift + Right-click = GOD'S WRATH

Shift + Left-click = TIME BREAKER

Requirements:

  • Correctly distinguish every input.
  • Prevent duplicate ability execution.
  • Prevent incorrect activation of two abilities from one click.
  • Handle Paper interaction events correctly.
  • Respect item identity through PDC.
  • Prevent unwanted vanilla Mace behavior for VOIDREAPER.
  • Never interfere with ordinary vanilla Maces.
  1. DAMAGE SYSTEM — CRITICAL

This section is mandatory.

Previous implementation had abilities that appeared to activate but did not damage entities.

Implement a proper damage architecture.

Requirements:

  • Use correct Bukkit/Paper damage APIs.
  • Check entity validity and health.
  • Exclude caster.
  • Exclude invalid or protected targets.
  • Respect PvP configuration.
  • Respect invulnerability and damage cooldown behavior.
  • Prevent accidental repeated damage.
  • Ensure damage is actually applied.
  • Ensure damage attribution is correct where supported.
  • Handle entity death events correctly.
  • Avoid duplicate damage from overlapping tasks.

Create reusable methods such as:

  • applyAbilityDamage()
  • findEligibleTargets()
  • applyKnockback()
  • pullEntity()
  • applyTemporaryEffect()
  • isValidTarget()

These must contain actual implementations, not empty placeholder methods.

  1. PARTICLE AND ANIMATION ENGINE — CRITICAL

Previous visuals did not appear even though particles were supposedly enabled.

Implement a centralized VFX system.

Requirements:

  • Use supported Bukkit/Paper particle APIs.
  • Verify particle types exist for each target version.
  • Use correct particle counts and offsets.
  • Use appropriate particle data types.
  • Use supported sounds.
  • Schedule animations using controlled repeating tasks.
  • Use multiple particle layers for complex visuals.
  • Handle animation timing correctly.
  • Ensure particles are visible to nearby players.
  • Do not assume a particle effect works without testing it.

Create reusable animation utilities for:

  • Circular particle rings.
  • Expanding particle rings.
  • Rotating spirals.
  • Particle columns.
  • Particle spheres.
  • Energy bursts.
  • Particle trails.
  • Implosion effects.

For each active ability, implement a separate animation controller.

IMPORTANT:

If a complex visual cannot be created with one particle type, combine multiple supported particle types and display entities where appropriate.

Never leave an ability with an empty visual implementation.

  1. COOLDOWN SYSTEM

Each active ability must have its own cooldown.

Requirements:

  • Configurable cooldown.
  • Action bar feedback.
  • Remaining cooldown display.
  • No accidental bypass.
  • Correct cleanup after logout.
  • No cooldown exploit through item movement or switching.
  • Persistent or session-based behavior clearly documented.
  1. CONFIGURATION

Generate a complete config.yml.

Include:

  • Enable/disable each ability.
  • Damage values.
  • Radius.
  • Duration.
  • Cooldowns.
  • Particle density.
  • Sound volume.
  • PvP settings.
  • Mob targeting.
  • Protected-world settings.
  • Maximum affected entities.
  • Debug mode.

All major values must be configurable without recompiling.

  1. COMMANDS

/voidreaper give <player> /voidreaper reload /voidreaper info /voidreaper version

Permissions: voidreaper.admin voidreaper.give voidreaper.reload voidreaper.use

Include:

  • Tab completion.
  • Permission validation.
  • Useful error messages.
  • Successful command feedback.
  1. PERFORMANCE
  • Avoid expensive entity scans every tick.
  • Use efficient scheduling.
  • Avoid excessive particle spawning.
  • Limit simultaneous animations.
  • Clean up temporary display entities.
  • Cancel tasks when abilities end.
  • Cancel tasks on player logout when appropriate.
  • Cancel all plugin tasks on shutdown.
  • Prevent memory leaks.
  • Support multiple players using abilities simultaneously.
  1. TESTING — MANDATORY

Do not deliver the plugin without testing.

Test on actual Paper servers.

For each supported Minecraft version, report whether it was actually tested.

Test all passive abilities.

Test all three active abilities.

For BLACK HOLE:

  • Does the animation appear?
  • Does the black hole form correctly?
  • Are entities pulled?
  • Is actual damage applied?
  • Does the collapse animation play?

For GOD'S WRATH:

  • Does charging appear?
  • Does targeting work?
  • Does the impact animation appear?
  • Is actual damage applied?
  • Does knockback work?

For TIME BREAKER:

  • Does activation appear?
  • Are targets affected?
  • Does the effect expire correctly?
  • Does the release animation appear?

Also test:

  • Cooldowns.
  • PvP restrictions.
  • Normal vanilla Maces.
  • Multiple simultaneous players.
  • Player logout.
  • Server shutdown.
  • Reload behavior.

Do not report tests as successful if they were not actually performed.

If a feature fails, fix it before delivery.

  1. SOURCE CODE QUALITY

Deliver:

  • Complete Java source code.
  • plugin.yml.
  • config.yml.
  • Maven or Gradle build configuration.
  • Version compatibility layer.
  • Ability classes.
  • Damage manager.
  • Particle animation manager.
  • Cooldown manager.
  • Item manager.
  • Event listeners.
  • Command manager.

Use clean object-oriented architecture.

Avoid:

  • Empty methods.
  • Fake functionality.
  • Placeholder code.
  • Hardcoded version assumptions.
  • Unhandled exceptions.
  • Duplicate event listeners.
  • Unmanaged repeating tasks.
  1. FINAL DELIVERY

Create this folder:

VOIDREAPER_RELEASE/ │ ├── VOIDREAPER.jar │ ├── Source-Code/ │ ├── src/ │ ├── pom.xml │ ├── plugin.yml │ └── config.yml │ └── Documentation/ ├── Installation.md ├── Commands.md ├── Configuration.md └── Testing-Report.md

The final JAR must be a real compiled Paper plugin.

The source code must be complete and editable.

Do not generate a resource pack or texture pack.

FINAL REQUIREMENT:

I want VOIDREAPER to be a genuinely working custom Minecraft Mace plugin.

All four passive abilities and all three active abilities must function correctly.

Every active ability must have actual gameplay effects, real damage where specified, proper target detection, cinematic purple particle animations, sounds, and reliable cooldowns.

A plugin that only activates particles without applying the actual ability effects is NOT acceptable.

Prioritize functionality, visual quality, stability, and compatibility over rushing the implementation.

Kodari AI
KodariNov 11 at 4:59 pm 5
VoidReaper
A comprehensive Paper plugin adding a legendary custom Mace with four passive abilities (Void Aura, Divine Protection, Soul Absorption, Gravity Master) and three active abilities (Black Hole, God's Wrath, Time Breaker). Features a complete particle animation engine, damage system, cooldown management, configurable settings, and full PvP/region protection integration. The plugin uses PersistentDataContainer for item identification, supports multiple simultaneous players, and includes a version compatibility layer for Minecraft 1.21.1-1.21.11.
  1. Create the Paper plugin source, item/damage/cooldown systems, passive and active ability controllers, and command/listener wiring.

  2. Add configuration, Gradle metadata, and the requested operational documentation.

  3. Clearly document compatibility and testing limits; no server-side tests or compiled JAR can be claimed without running them.

Created the Java 21 Paper plugin source, configuration, Gradle build, and installation, command, configuration, and testing documentation. It includes PDC item identification, passive and active ability systems, cooldowns, damage/target handling, particle effects, and optional WorldGuard region checks.

Testing: No Paper server tests were performed. The project compiles against Paper 1.21.1; compatibility with Paper 1.21.1–1.21.11 is not verified, as recorded in Documentation/Testing-Report.md.

JAR: I have not compiled or tested a VOIDREAPER.jar, so I can’t claim one is ready. To generate and download it in Kodari:

  1. Click Compile in the desktop top bar, or on phone tap ⋮ → Compile Project.

  2. Click Compile in the window.

  3. When it succeeds, click Download on the build or Download VOIDREAPER.jar in chat.

Kodari can make mistakes. Review important code before using.
Files
Documentation
src
build.gradle
Code
17 1,312
src/main/java/com/kodari/voidreaper/VoidReaperPlugin.java
package com.kodari.voidreaper;

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

public final class VoidReaperPlugin extends JavaPlugin {
    private ItemManager itemManager;
    private CooldownManager cooldownManager;
    private TargetingManager targetingManager;
    private VfxManager vfxManager;
    private AbilityManager abilityManager;
    private PassiveManager passiveManager;

    @Override
    public void onEnable() {
        saveDefaultConfig();
        itemManager = new ItemManager(this);
        cooldownManager = new CooldownManager();
        targetingManager = new TargetingManager(this);
        vfxManager = new VfxManager(this);
        abilityManager = new AbilityManager(this, itemManager, cooldownManager, targetingManager, vfxManager);
        passiveManager = new PassiveManager(this, itemManager, cooldownManager, targetingManager, vfxManager);

        Bukkit.getPluginManager().registerEvents(
                new VoidReaperListener(itemManager, abilityManager, passiveManager), this);
        VoidReaperCommand command = new VoidReaperCommand(this, itemManager);
        PluginCommand pluginCommand = getCommand("voidreaper");
        if (pluginCommand == null) {
            getLogger().severe("The voidreaper command is missing from plugin.yml; disabling.");
            Bukkit.getPluginManager().disablePlugin(this);
            return;
        }
        pluginCommand.setExecutor(command);
        pluginCommand.setTabCompleter(command);
        passiveManager.start();
        getLogger().info("VOIDREAPER enabled.");
    }

    @Override
    public void onDisable() {
        if (passiveManager != null) passiveManager.stop();
        if (abilityManager != null) abilityManager.shutdown();
        getLogger().info("VOIDREAPER disabled.");
    }

    public ItemManager getItemManager() {
        return itemManager;
    }
}