Build the newly created project into a professional, complete Bukkit/Paper Minecraft Java Edition plugin named Royal Weapons, implementing the user's request for five custom weapons and a configurable sound system. First inspect the project template, existing files, target Minecraft/API version, and conventions, then implement compatibly; do not assume unsupported APIs. You own all code/resources/plugin metadata/config/docs. Do not try to build or claim verified compilation.
Required weapons (give them recognizable custom names/lore and identify them robustly with PersistentDataContainer, not display-name checks):
- MACE item named CROWN HAMMER: a powerful smash ability; trigger on a documented intuitive action (prefer right-click). Create particles around user and affected targets, damage enemies in a configurable radius, knock them back, apply short Slowness/stun, activation/impact sounds and a per-player cooldown. Do not damage blocks.
- ROYAL SPEAR: use the best compatible in-game spear-like item/material (TRIDENT if the target API lacks a dedicated spear). Give unique name/lore/appearance. A right-click throws a magical spear/projectile with a particle trail, extra hit damage and special effect; return it to its owner (safe return mechanic, don't duplicate/drop it, handle online/offline/death/world-change/removal). Configurable cooldown and throw/hit/return sounds.
- AXE named ASTRAL AXE: right-click Astral Strike summons an astral attack from above at the targeted location/forward point; star particles, lightning-style cosmetic effect (visual only, no uncontrolled vanilla lightning fire/block damage), impact effect, configurable-radius area damage, brief Weakness or Slowness, charge/activation/impact sounds, configurable cooldown.
- SWORD named DARK FIRE SABER: dark flame visuals while held/used, right-click Dark Inferno fires a forward wave/cone, damages enemies, briefly burns and weakens them, dark flame and explosion-style cosmetic particles (no block destruction), swing/activation/fire/impact sounds and configurable cooldown.
- CROSSBOW named AURA BOW: magical lore/appearance, special-shot cooldown; fired projectiles have aura trails, on hit create aura explosion visuals and bonus damage. Add config options for piercing and homing behavior, safely defaulted/documented. Charging/shooting/projectile/impact sounds.
Project expectations:
- Provide clear configurable weapon values (cooldowns, damages, radii/ranges/durations/knockback) and every sound key/default in config.yml, including at least crown_hammer_activate, crown_hammer_impact, royal_spear_throw/hit/return, astral charging/activate/impact, dark saber swing/activate/fire/impact, and aura crossbow charge/shoot/projectile/impact. Use Bukkit/Paper sound names sensibly, with graceful fallback for invalid configured values; explain in README how operators may use valid Bukkit Sound enum names and/or registered namespaced resource-pack sound identifiers if supported by target API.
- Include a permission-protected admin command to give each weapon, usage/help, tab completion if appropriate, and reload configuration. Add plugin metadata, a default config, permission declarations and README with install/commands/permissions/abilities/config/safe behavior. Give commands namespaced to Royal Weapons and plugin identity/version appropriate to template.
- Use safe entity filtering (do not hit caster, teammates if a clear existing mechanism exists, armor stands, dead entities; never damage blocks), server-thread-safe Bukkit scheduling, per-player cooldowns with useful feedback, and cleanly cancel/clean any tasks/projectile tracking on plugin disable. Prevent ordinary projectiles/weapon items from unintentionally acquiring weapon abilities; preserve weapon identity after legitimate item movement/reload.
- Avoid costly per-tick world scans; use bounded nearby entity queries and configurable particle effects. Implement the behavior robustly and consistently with the template's target API. Keep code readable and maintainable.
Deliver working source/config/docs and a concise final report. Do not build; I will run compilation after your delegation completes.