Dhruv Bahirgonde

also research altar smp before makeing this plugin look at all the visuals on altar and stuff and also research popular mc server hoplite to

📎 1 file 38,195 chars
📄
pasted-code-1790372887471.txt
txt 1458 lines
▶
# ⚔️ ADMIN SWORDS — ULTIMATE 12-SWORD PREMIUM MINECRAFT PVP PLUGIN

## ROLE

You are a senior Minecraft Java plugin developer, combat-system designer, VFX artist, resource-pack developer, and UI/UX designer.

Build a complete, polished, production-oriented Minecraft PvP sword plugin with **12 unique admin swords**. The plugin must feel like a premium custom combat system inspired by high-quality Minecraft PvP servers and action-survival games.

The goal is not to create basic commands that spawn random particles. The goal is to create a cohesive combat experience with recognizable sword identities, strong animations, readable attack indicators, satisfying sounds, responsive abilities, and reliable server-side mechanics.

**Do not claim a feature is complete if it is only a placeholder, simulated effect, missing asset, or unimplemented mechanic.**

If a requested feature cannot be implemented using the selected server API, explain the limitation and implement the closest functional alternative without silently changing the ability's behavior.

---

# 1. ABSOLUTE CORE RULE — ZERO PASSIVES

This rule overrides all other design decisions.

There are exactly **12 swords**.

Each sword has exactly:

* 1 Primary Ability
* 1 Secondary Ability

That means:

**12 swords × 2 abilities = 24 total abilities.**

There must be no passive abilities.

Do not add:

* Passive damage.
* Passive healing.
* Passive speed.
* Passive defense.
* Passive critical-hit effects.
* Passive hit counters.
* Passive charge generation.
* Passive elemental damage.
* Passive stun.
* Passive knockback.
* Passive cooldowns.
* Automatic attacks unrelated to an activated ability.
* Effects that permanently remain active while a sword is held.

Every ability must be activated manually using the player's configured activation control.

An ability may have automatic stages after activation. For example, a charged projectile can fly after activation, or a giant sword can strike after the wielder successfully hits a target. These are part of the activated ability, not passives.

Do not invent extra abilities.

---

# 2. TARGET SERVER AND COMPATIBILITY

Build for the exact Minecraft Java server version configured by the project.

Default target:

**Paper 1.21.11, unless the user explicitly chooses a different compatible version.**

Before writing the final code:

1. Confirm the target API and build configuration.
2. Use supported APIs for the target version.
3. Avoid silently relying on features from a different Minecraft version.
4. Keep implementation version-aware where necessary.
5. Make the plugin compile successfully.
6. Avoid unnecessary NMS or unstable internals unless they are genuinely required and documented.

Use a clear Gradle or Maven project structure.

Suggested organization:

```text
AdminSwords/
├── src/main/java/
│   └── your/package/adminswords/
│       ├── AdminSwordsPlugin.java
│       ├── commands/
│       ├── abilities/
│       ├── swords/
│       ├── combat/
│       ├── cooldowns/
│       ├── keybinds/
│       ├── gui/
│       ├── effects/
│       ├── sounds/
│       ├── resourcepack/
│       ├── listeners/
│       └── utilities/
├── src/main/resources/
│   ├── plugin.yml
│   ├── config.yml
│   ├── swords.yml
│   ├── abilities.yml
│   ├── messages.yml
│   └── resource-pack/
└── README.md
```

Use sensible package and class names. The structure can differ if the architecture is cleaner, but maintain separation between commands, abilities, cooldowns, visuals, and configuration.

---

# 3. THE 12 SWORDS

Implement all 12 swords.

## ORIGINAL SWORDS

1. 🕸️ Cobweaver
2. 🌑 Crimson Whisp
3. ✨ Lumina
4. 🐉 Elyth
5. 🌪️ Atherion
6. 🗡️ Shade Dagger
7. 🛡️ Ancient Sword
8. ☠️ Elemental Sword

## NEW SWORDS

9. 🕳️ Voidreaver
10. ❄️ Frostbane
11. ☀️ Solara
12. 🔥 Infernal Edge

Every sword must have:

* Unique item identifier.
* Unique name and lore.
* Unique visual identity.
* Unique primary ability.
* Unique secondary ability.
* Custom model/texture where the resource pack is available.
* Distinct particle effects.
* Distinct sound effects.
* Distinct ability animations.
* Primary cooldown.
* Secondary cooldown.
* Player-only cooldown boss bars.
* Server-side validation.
* Cleanup and cancellation handling.
* Configuration support.

Do not reuse the exact same ability animation for every sword with a different particle color. Each sword must have a recognizable personality.

---

# 4. CUSTOM SWORD TEXTURES AND RESOURCE PACK

Create a professional resource-pack structure for the swords.

Every sword should have:

* Custom texture.
* Custom model or item-model configuration appropriate to the target version.
* Unique silhouette or decorative details.
* Distinct blade, handle, guard, and ornament design.
* Inventory icon presentation.
* First-person visual consideration.
* Third-person visual consideration.
* Dropped-item presentation where appropriate.

## Visual design standards

Avoid:

* Flat recolored vanilla swords.
* Blurry textures.
* Unreadable details.
* Excessive noise.
* Random symbols.
* Identical models with only different colors.
* Placeholder textures presented as finished artwork.

Each sword should have a deliberate color palette and readable silhouette.

### Model design examples

**Cobweaver:** Jagged spider-fang blade, web-like guard, pale silk accents, dark metallic core.

**Crimson Whisp:** Corrupted red blade, twisted vine details, dark smoky core, glowing crimson markings.

**Lumina:** Radiant white-gold blade, symmetrical divine guard, crystalline light details.

**Elyth:** Dragon-scale guard, curved dragon-inspired blade, glowing energy channel.

**Atherion:** Lightweight wind-shaped blade, floating ring accents, sharp aerodynamic silhouette.

**Shade Dagger:** Compact dark dagger, purple edge highlights, shadow-like guard.

**Ancient Sword:** Heavy ancient guardian weapon, dark stone-metal appearance, sonic energy markings.

**Elemental Sword:** A complex forbidden elemental design combining fire, poison, lightning, and earth motifs.

**Voidreaver:** Distorted void-metal blade, spatial cracks, black and violet energy.

**Frostbane:** Ice-crystal blade, frosted guard, translucent-looking crystalline details where supported.

**Solara:** Sun-metal blade, radiant gold core, solar emblem and warm luminous accents.

**Infernal Edge:** Molten blade, dark volcanic guard, red-orange cracks and demonic energy details.

If the resource pack is required, include installation instructions and explain what visuals are server-side versus client-side.

---

# 5. PREMIUM VISUAL EFFECT SYSTEM

Do not treat VFX as an afterthought.

Every ability should be built as a sequence of visual stages.

## Ability visual phases

Each ability should have a suitable combination of:

### Phase A — Activation

* A distinct activation sound.
* A short animation or visual cue.
* Particles that originate from the sword or wielder.
* A clear action bar, title, or subtitle when appropriate.
* An indication if the ability failed because of range, target, or cooldown.

### Phase B — Charging / Wind-up

Use this phase for abilities that require a visible preparation period.

* Energy gathering.
* Expanding rings.
* Rising particles.
* Rotating runes.
* Weapon glow or Display Entity animation where appropriate.
* Target or ground warning indicator.
* Audio charge buildup.

Do not make every ability have a long charge-up. Instant attacks should feel responsive.

### Phase C — Travel / Attack Motion

For projectiles and dashes:

* Create a visible direction.
* Add a recognizable trail.
* Use motion-aligned particles where possible.
* Avoid leaving permanent particles in the world.
* Ensure visual effects do not misrepresent the actual hitbox.

### Phase D — Impact

Every impact should feel different depending on the sword.

Use a layered effect system:

1. Initial contact flash.
2. Main particle burst.
3. Directional impact particles.
4. Ground or air shockwave.
5. Secondary sound layer.
6. Damage or status feedback.
7. Short-lived residual visual effect when specified.

### Phase E — Completion

* Finish the visual effect.
* Stop looping sounds.
* Remove temporary entities.
* Cancel scheduled tasks.
* Remove temporary markers.
* Update cooldown UI.
* Avoid leaving invisible ability states behind.

---

# 6. PARTICLE QUALITY AND PERFORMANCE

Use particles deliberately.

Every sword should have its own particle language.

## Shape examples

* Expanding rings.
* Spiral trails.
* Circular arenas.
* Directional beams.
* Ground cracks.
* Vertical pillars.
* Rotating runes.
* Converging energy.
* Radial shockwaves.
* Rising smoke.
* Projectile trails.
* Impact bursts.

Do not spawn massive amounts of particles every tick without a reason.

Implement configurable particle density:

* LOW
* MEDIUM
* HIGH

The server should retain correct mechanics regardless of particle quality.

Where possible:

* Spawn particles only within a sensible viewing range.
* Use player-specific particle visibility when useful.
* Avoid unnecessary loops.
* Avoid spawning entities when particles or server-side effects are sufficient.
* Use temporary Display Entities only when they meaningfully improve the visual result.
* Ensure every temporary visual object has a cleanup reference.

Use supported Paper particle APIs and version-appropriate implementations.

---

# 7. COMBAT READABILITY

High visual quality must not make the combat confusing.

Every major attack must have a readable visual indicator.

Examples:

* A glowing circle on the ground before an explosion.
* A beam direction before it fires.
* A shadow mark on a target.
* A visible path for a dash.
* A warning ring before an area shockwave.
* A giant sword shadow before it strikes.
* A frost circle before freezing.
* A gravity sphere before its implosion.

The warning should communicate:

* Where the attack will occur.
* Whether the player is inside the danger area.
* When the attack is about to activate.
* Whether the attack can be avoided.
* Whether the effect belongs to the wielder or another player.

Do not hide important attack hitboxes behind misleading or excessively bright effects.

---

# 8. SOUND DESIGN

Every sword needs unique audio feedback.

Use multiple sound layers when appropriate:

* Activation sound.
* Charge sound.
* Projectile launch.
* Movement sound.
* Impact sound.
* Explosion sound.
* Completion sound.
* Failure/miss sound.
* Cooldown-ready sound where enabled.

Avoid sound spam.

Sound volume, pitch, and category must be configurable where appropriate.

Do not play continuous sounds indefinitely. Stop them when the ability ends or is cancelled.

Use appropriate Minecraft sound events available for the target version. Where custom resource-pack audio is used, include the sound asset structure and resource-pack configuration.

---

# 9. COOLDOWN SYSTEM

Every sword has exactly two player-facing cooldowns:

**Primary Cooldown**

**Secondary Cooldown**

There are no passive cooldowns.

Cooldown values must be configurable.

## Cooldown behavior

* Cooldown starts only when the ability is successfully activated, unless explicitly configured otherwise.
* Failed activation should not consume a cooldown unless specified by the ability.
* Do not allow activation during cooldown.
* Separate primary and secondary cooldown states.
* Avoid duplicate activation from a single input.
* Prevent accidental reactivation through repeated interaction events.
* Display remaining time accurately.
* Remove the cooldown UI when ready.

## Boss bars

Boss bars must be visible only to the player using the sword.

Example:

`⚔ COBWEAVER PRIMARY — 8.0s`

`⚔ COBWEAVER SECONDARY — 14.0s`

Requirements:

* Create only after an ability is used.
* Decrease smoothly toward zero.
* Display the remaining duration.
* Remove the bar completely when ready.
* Do not show the boss bar to other players.
* Do not leave boss bars behind after disconnects or reloads.
* Support two independent cooldown bars if both abilities are cooling down.

Avoid boss bar duplication. Store and manage each player's active cooldown bars safely.

---

# 10. ADMIN COMMANDS

Use clear, safe commands.

## Give sword

```text
/sword give  
```

Examples:

```text
/sword give cobweaver PlayerName
/sword give elemental PlayerName
/sword give voidreaver PlayerName
```

Only authorized admins/OPs should use the give-sword functionality.

Add tab completion where possible.

## Sword menu

```text
/sword menu
```

Open the player's sword control configuration GUI.

If `/sword` without arguments is supported, make its behavior clear and consistent.

## Configure cooldown

```text
/cooldown   
```

Example:

```text
/cooldown cobweaver primary 8
/cooldown elemental secondary 30
```

Restrict configuration commands to authorized admins.

Validate:

* Sword name.
* Ability type.
* Cooldown value.
* Permission.
* Numeric limits.
* Invalid arguments.

Do not create passive cooldown commands.

## Optional admin commands

If implemented, include:

```text
/sword reload
/sword list
/sword giveall 
```

Do not add unnecessary commands.

---

# 11. KEYBIND CONFIGURATION GUI

Create a polished graphical configuration menu.

The player must be able to configure the Primary and Secondary activation controls independently.

## Supported controls

* Crouch + Right Click.
* Crouch + Left Click.
* Right Click.
* Left Click.
* Drop Key.
* Offhand Swap.

Default activation controls can be configured per sword or globally.

Example:

```text
PRIMARY
Current Keybind: Crouch + Left Click

SECONDARY
Current Keybind: Right Click
```

The menu must clearly identify which ability each setting controls.

## Input handling requirements

* Prevent one input from triggering both abilities.
* Prevent accidental sword drops when Drop Key is used as an ability control.
* Prevent accidental offhand swapping when that control is configured.
* Avoid repeated activation from duplicate or conflicting events.
* Ensure crouch combinations are detected correctly.
* Ensure left-click and right-click handling does not break normal gameplay unnecessarily.
* Do not activate abilities from unrelated items.
* Validate the sword held by the player before activating an ability.

## Persistence

Save player keybind settings permanently using a suitable data-storage system.

Save settings on change and/or through a safe persistence strategy.

Load them on player join.

Handle:

* Invalid stored settings.
* Missing player settings.
* Plugin reload.
* Player disconnect.
* Configuration migration where necessary.

If a control cannot be detected reliably on the target server without client modifications, explain the limitation and implement the safest supported alternative.

---

# 12. SWORD ABILITIES

Implement the original 8 sword designs exactly as specified in the original design brief, preserving their names, themes, ability behavior, and stated effects.

The following visual enhancements are mandatory.

## 🕸️ COBWEAVER

Theme: Spider / Web / Trap

### PRIMARY — COBWEB HEAD

Default: Crouch + Hit.

* Target range: 12 blocks.
* Web/head visual impact.
* Six-second web duration.
* Eating/use-blocking effect for four seconds.
* Blindness for eight seconds.
* Slowness for five seconds.
* White web particles.
* Spider particles.
* Web explosion.
* Wrapping animation.
* Spider and magical trap audio.

Implement the target restriction, duration, and status effects according to the original ability brief. Do not let the web visual alone determine the hitbox.

### SECONDARY — SPIDER DOMINION

* Approximately eight-block radius.
* Ten-second duration.
* Webs rise from the ground.
* Additional web visuals appear periodically.
* Nearby enemies are slowed.
* Wielder is immune.
* Clear arena boundary and escape readability.
* Spider sounds and crawling visual effects.
* Remove all temporary effects and visual objects at completion.

## 🌑 CRIMSON WHISP

Theme: Corrupted vines / Darkness

### PRIMARY — CRIMSON VINE

* Giant crimson vine growth beneath the target.
* Thirty-second duration.
* Growth stage every three seconds.
* Crimson particles erupt from the ground.
* Growth sounds.
* Standing on the vines causes one true damage every two seconds.
* Wielder is immune.
* Clearly show the active zone.

### SECONDARY — CRIMSON PRISON

* Giant circular vine prison.
* Ten-second duration.
* Vines rise and surround the target.
* Slowness.
* Vine restraints.
* Damage pulses.
* Crimson particle growth.
* Escape difficulty that remains visually understandable.
* Final crimson explosion.

## ✨ LUMINA

Theme: Divine light / Holy power

### PRIMARY — WEAVING ASCENSION

Manual activation.

* Weaving for ten seconds.
* Resistance I.
* Regeneration I.
* Health Boost II.
* All attacks become critical hits during the active ability, as specified.
* Golden aura.
* White/gold particles.
* Light beams.
* Critical-hit particles.
* Powerful divine sound.
* All effects end when the ability expires.

This is an active ability, not a passive.

### SECONDARY — FORCEFIELD

* Four-second duration.
* Wielder becomes invincible according to the specified mechanic.
* Transparent energy sphere.
* Golden/white shield particles.
* Energy waves.
* Visible attack impacts.
* Shield impact sound.
* Remove invulnerability safely at the end.
* Ensure ability cancellation cannot leave permanent invulnerability.

## 🐉 ELYTH

Theme: Dragon / Sky / Mace

### PRIMARY — DRAGON

Support the configured keybind and optional `/dragon` command if implemented.

* Freeze target for five seconds.
* Armor-shredding effect.
* Teleport wielder 15 blocks upward as specified.
* Mace Mode.
* Powerful downward slam.
* Successful slam deals five hearts true damage.
* Dragon particles.
* Dragon breath.
* Fire/energy trail.
* Huge impact shockwave.
* Dragon roar.
* Validate the mace-mode state and clean it up safely.

### SECONDARY — DRAGONFALL

* Giant spectral dragon visual above the battlefield.
* Dragon movement/flight animation.
* Dragon energy attack.
* Large impact zone.
* Knockback.
* Slowness.
* Strong damage.
* Massive dragon explosion.
* Wielder immunity to their own attack.

## 🌪️ ATHERION

Theme: Wind / Storm / Kinetic energy

### PRIMARY — ATHERION DASH

Support the configured keybind and optional `/atherion` command if implemented.

* Dash forward 14 blocks.
* Visible wind trail.
* If the dash hits a player: launch them and deal five hearts true damage.
* Wind explosion on impact.
* Wind-charge attack may deal two true damage.
* The wind-charge mechanic has a two-second internal cooldown only if the ability is configured to use it.
* Do not turn this internal timing into a passive mechanic.
* Validate collisions and prevent unintended repeated damage.

### SECONDARY — TEMPEST COLLAPSE

* Massive storm above the target.
* Warning phase.
* Wind pull toward the center.
* Wind column crashes down.
* Enemies launch upward.
* Expanding shockwaves.
* Slowness.
* Damage.
* Large circular wind explosion.
* Wielder immunity where specified.

## 🗡️ SHADE DAGGER

Theme: Assassin / Shadow / Poison

### PRIMARY — TRIPLE SHADOW DAGGERS

* Launch three spectral daggers.
* Each dagger deals 1.5 true damage.
* On a valid hit, teleport wielder to target.
* Slowness III.
* Poison IV.
* Weakness II.
* Black smoke.
* Purple particles.
* Shadow explosion.
* Teleport effect.
* Prevent unintended multi-teleport behavior if multiple daggers hit the same target.

### SECONDARY — SHADOW EXECUTION

* Mark a target.
* Temporary hidden/invisible state as specified.
* Three shadow clones appear.
* Simultaneous clone attack visuals.
* Multiple shadow strikes.
* Final strike teleports wielder behind target.
* Giant black/purple explosion.
* Clean up all temporary marks, clones, and scheduled tasks.

## 🛡️ ANCIENT SWORD

Theme: Warden / Ancient guardian / Sonic energy

### PRIMARY — WARDEN BEAM

Support the configured keybind and optional `/warden` command if implemented.

* Powerful Warden-style beam.
* Five or more hearts true damage, configurable where appropriate.
* Blindness V for six seconds.
* Sonic beam.
* Sonic rings.
* Ground distortion.
* Dark energy particles.
* Massive sonic boom.
* Directional beam visualization.
* Validate line of sight and target rules.

### SECONDARY — ANCIENT CATACLYSM

* Gigantic sonic shockwave.
* Expanding rings.
* Powerful knockback.
* True damage.
* Blindness/dark visual.
* Sonic particles.
* Ground crack effect.
* Wielder immunity.
* Clear area warning.

## ☠️ ELEMENTAL SWORD

Theme: Fire / Poison / Lightning / Earth / Forbidden magic

This sword must receive exceptionally detailed VFX.

### PRIMARY — POISON CIRCLE

* Eight-block radius.
* Twelve-second duration.
* Poison particles.
* Toxic mist.
* Rising ground particles.
* Green magical runes.
* Poison bubbles.
* Toxic smoke.
* Poison status.
* Wielder immunity.
* Water placement restriction inside the circle.

Water counter:

When a player attempts to place water inside the Poison Circle:

* Remove/drain the placed water immediately.
* Play a draining sound.
* Spawn a green particle explosion.
* Do not permanently destroy the bucket unless explicitly configured.
* Validate the block location against active zones.
* Avoid interfering with water outside the active ability.

### SECONDARY — CELESTIAL FIRE SWORD

Stage 1 — Summon:

* Giant fire/energy sword above the wielder.
* Vertical floating position.
* Fire, smoke, embers, orange/red particles.
* Burning aura.
* Deep charging sound.

Stage 2 — Follow:

* Sword follows the wielder from above during the charge.
* Smooth movement.
* Short configurable charge period.
* Clear sword visibility.
* Avoid unnecessary entity creation.
* Stop and clean up on cancellation.

Stage 3 — Strike:

* On a valid successful hit, sword launches downward.
* Crashes into the target.
* Giant explosion.
* Fire burst.
* Shockwave.
* Ground particles.
* Smoke.
* Elemental energy.
* Wielder immunity to own explosion.

Target effects:

* Slowness.
* Poison.
* Weakness.
* Bleeding.

Bleeding:

* Twelve-second duration.
* Damage every two seconds.
* Six bleeding ticks.
* Each tick deals 0.5 hearts damage.
* Total six bleeding ticks.
* Red damage particles.
* Visual bleeding impact.
* Final elemental burst.
* Finishing sound.
* Remove bleeding state after completion.

Miss behavior:

If the wielder does not hit a valid target before timeout:

* Remove the giant sword.
* Enter cooldown according to the configured behavior.
* Play a miss/failure sound.
* Clean up all visual objects and scheduled tasks.

---

# 13. NEW SWORDS — FULL DESIGN SPECIFICATIONS

Implement the following four new swords with the same quality level as the original eight.

## 🕳️ VOIDREAVER

Theme: Void energy / Gravity / Space distortion.

Color palette: Black, deep violet, dark blue, and small high-contrast void highlights.

Visual identity:

* Distorted void-metal blade.
* Cracks in space around the sword.
* Purple-black particles.
* Dark energy trails.
* Warped-looking impact effects.
* Avoid excessive screen-obscuring effects.

### PRIMARY — VOID RIFT

Activation: Configurable primary keybind.

Mechanics:

* Open a rift in front of the wielder.
* Create a directional void attack.
* The rift expands or travels toward a valid target.
* Apply configured damage and knockback.
* Use a short, readable wind-up if the attack is charged.
* Do not apply unintended passive gravity outside the active ability.

Visual sequence:

1. Dark rift appears.
2. Purple energy gathers at the center.
3. Spatial cracks expand outward.
4. Rift attack travels.
5. Impact implosion and particle burst.
6. Rift collapses and disappears.

### SECONDARY — EVENT HORIZON

Mechanics:

* Create a temporary gravitational sphere at the selected location.
* Pull valid enemies toward the center.
* Use a visible warning boundary.
* After the configured duration, trigger a void implosion.
* Apply configured damage and knockback.
* Wielder immunity to their own attack where specified.
* Do not pull players outside the intended ability range.

Visual sequence:

* Expanding black-violet circle.
* Rotating spatial particles.
* Converging energy.
* Gravity distortion visual.
* Implosion flash.
* Expanding impact ring.
* Complete cleanup.

## ❄️ FROSTBANE

Theme: Ice / Crystal / Frozen storm.

Color palette: Ice blue, white, pale cyan, and darker blue accents.

Visual identity:

* Crystal ice sword.
* Frost particles.
* Sharp ice-spike geometry.
* Cold mist.
* Crystalline impact sound.

### PRIMARY — GLACIAL LANCE

Mechanics:

* Fire a directional ice projectile.
* Use a visible ice-crystal trail.
* On impact, create an ice spike effect.
* Apply configured damage and slow effect.
* Add a short-lived slow zone if configured.
* Validate target and range.

Visual sequence:

1. Ice particles gather at sword tip.
2. Crystalline lance forms.
3. Projectile launches with a frost trail.
4. Impact produces ice shards.
5. Frost mist expands.
6. Effects disappear.

### SECONDARY — ABSOLUTE ZERO

Mechanics:

* Create a frost circle in the selected area.
* Display a clear danger radius.
* Gradually build ice crystals.
* Apply configured immobilization or slowing effect.
* Release a freezing shockwave.
* Use a reasonable duration and configurable damage.
* Avoid permanent world changes unless explicitly configured.

Visual sequence:

* Frost ring appears.
* Ice particles rise from the ground.
* Crystals form around the zone.
* Center freezes visually.
* Shockwave expands.
* Ice fragments burst outward.
* Effects clean up.

## ☀️ SOLARA

Theme: Solar flame / Radiance / Sun energy.

Color palette: White, gold, yellow, orange, and warm radiant highlights.

Visual identity:

* Sun-forged blade.
* Radiant gold core.
* Solar emblem.
* Bright but readable light effects.
* Strong beam and sunburst identity.

### PRIMARY — SOLAR PIERCE

Mechanics:

* Charge a directional solar attack.
* Fire a beam or piercing energy projectile.
* Apply configured damage.
* Show a visible beam direction.
* Use a brief warning if the ability has a wind-up.
* Validate line of sight and target range.

Visual sequence:

1. Sword emits golden light.
2. Solar energy gathers.
3. A thin targeting line appears.
4. Beam releases.
5. Bright impact flare occurs.
6. Radiant fragments fade.

### SECONDARY — SUNFALL

Mechanics:

* Select an impact area.
* Create a visible solar danger circle.
* A miniature sun forms above the area.
* Charge for a short configurable duration.
* Fire a vertical solar beam.
* Create an explosion/shockwave.
* Apply configured damage and knockback.
* Use clear warning timing.
* Prevent damage to the wielder where immunity is specified.

Visual sequence:

* Solar circle forms.
* Golden runes rotate.
* Sun forms above the area.
* Light intensifies.
* Vertical beam strikes.
* Shockwave expands.
* Final solar particles fade.

## 🔥 INFERNAL EDGE

Theme: Hellfire / Magma / Demonic energy.

Color palette: Dark red, orange, black, ember yellow, and molten highlights.

Visual identity:

* Volcanic sword.
* Molten cracks.
* Dark demonic guard.
* Fire and ash.
* Strong ground eruption effects.

### PRIMARY — HELLCHAIN

Mechanics:

* Launch a molten energy chain toward a valid target.
* Show the chain connecting the wielder to the target during the active ability.
* Apply configured damage and status effects.
* Use a visible chain impact.
* Prevent unintended permanent tethering.
* Remove the chain when the ability completes or is cancelled.

Visual sequence:

1. Molten energy gathers.
2. Chain launches.
3. Chain travels with ember trail.
4. Chain connects.
5. Fire particles travel along the link.
6. Impact bursts.
7. Chain disintegrates into embers.

### SECONDARY — INFERNO JUDGMENT

Mechanics:

* Create a large infernal area.
* Show warning ring and pillar locations.
* Summon fiery pillars in a readable sequence.
* Apply configured damage and knockback.
* Add magma/fire visual effects.
* Converge energy into a central explosion.
* Wielder immunity as specified.
* Clean up all temporary effects.

Visual sequence:

* Infernal circle forms.
* Molten runes appear.
* Pillars charge one by one.
* Fire erupts from the ground.
* Pillars converge toward the center.
* Massive explosion.
* Smoke and embers fade.

---

# 14. DAMAGE AND STATUS EFFECT RULES

Damage must be implemented server-side and must not rely on particles.

## True damage

For every ability that specifies true damage:

* Implement the intended armor-bypassing behavior where supported.
* Document how absorption, resistance, invulnerability, and other damage modifiers are handled.
* Do not silently change true damage into ordinary damage.
* Avoid double damage from overlapping event handlers.
* Validate damage targets.
* Respect configured friendly-fire or protected-player rules if the server has them.

## Status effects

* Apply only during the active ability.
* Use configurable duration and amplifier values where appropriate.
* Track effects that the ability owns.
* Do not remove unrelated player effects.
* Restore or clean up temporary state safely.
* Avoid leaving permanent buffs after disconnects or plugin reloads.

---

# 15. TARGETING AND HIT DETECTION

Create a consistent targeting system.

Support appropriate targeting methods:

* Ray tracing.
* Directional targeting.
* Area-of-effect radius.
* Projectile collision.
* Valid entity checks.
* Line-of-sight checks where required.

Targeting must not be based solely on a particle's location.

Requirements:

* Avoid hitting the wielder unintentionally.
* Avoid duplicate damage from the same attack phase.
* Prevent invalid entity references.
* Validate world and location.
* Respect range and ability-specific target rules.
* Handle multiple targets correctly.
* Handle unloaded or invalid targets.
* Do not allow attacks to target arbitrary players through walls unless explicitly intended.

---

# 16. ACTIVE ABILITY STATE MANAGEMENT

Use an ability manager or equivalent reliable state system.

Track:

* Owner.
* Sword.
* Ability.
* Start time.
* Current phase.
* Target.
* Temporary entities.
* Scheduled tasks.
* Active zones.
* Damage state.
* Cancellation state.

Every ability must have clear lifecycle behavior:

1. Activate.
2. Execute.
3. Complete.
4. Cancel if necessary.
5. Clean up.

When an ability ends, all associated resources must be removed.

Avoid static global state that can leak across reloads or players.

---

# 17. CONFIGURATION

Make the plugin configurable.

Use appropriate YAML configuration files.

Allow configuration of:

* Primary cooldown.
* Secondary cooldown.
* Damage.
* Range.
* Duration.
* Particle density.
* Sound volume.
* Sound pitch.
* Ability enabled/disabled state.
* Target rules.
* Friendly-fire behavior where appropriate.
* Status-effect duration.
* Admin permissions.
* Keybind defaults.
* Resource-pack settings where applicable.

Do not place every setting in one enormous unstructured file if a cleaner structure is possible.

Use safe defaults.

Validate configuration values and report invalid configuration entries clearly.

---

# 18. PLAYER FEEDBACK

Use action bars, titles, subtitles, and sounds only where useful.

Examples:

```text
🕸 COBWEAVER — SPIDER DOMINION
🌑 CRIMSON WHISP — CRIMSON PRISON
✨ LUMINA — WEAVING ASCENSION
🐉 ELYTH — DRAGONFALL
🌪 ATHERION — TEMPEST COLLAPSE
🗡 SHADE DAGGER — SHADOW EXECUTION
🛡 ANCIENT SWORD — ANCIENT CATACLYSM
☠ ELEMENTAL SWORD — CELESTIAL FIRE SWORD
🕳 VOIDREAVER — EVENT HORIZON
❄ FROSTBANE — ABSOLUTE ZERO
☀ SOLARA — SUNFALL
🔥 INFERNAL EDGE — INFERNO JUDGMENT
```

Use feedback for:

* Successful activation.
* Failed activation.
* Cooldown remaining.
* Invalid target.
* Ability completion.
* Missed ability.
* Important state transitions.

Do not spam the chat.

Do not show private cooldown boss bars to other players.

---

# 19. SWORD LORE

Every sword's lore must display:

* Sword name.
* Primary ability.
* Secondary ability.
* Primary cooldown.
* Secondary cooldown.
* Controls configurable through the sword menu.

Do not display a passive ability.

Do not claim an ability is passive.

Use readable formatting and consistent styling.

---

# 20. PERFORMANCE AND CLEANUP

Optimize the plugin for a real multiplayer server.

Avoid:

* Unbounded repeating tasks.
* Untracked temporary entities.
* Excessive particle spam.
* Repeated unnecessary world scans.
* Unvalidated player references.
* Memory leaks.
* Unremoved boss bars.
* Persistent temporary blocks.
* Duplicate listeners.
* Tasks that continue after ability completion.

Implement:

* Central task and effect cleanup.
* Safe player disconnect handling.
* Ability cancellation.
* World unload handling where relevant.
* Plugin disable cleanup.
* Cooldown cleanup.
* Temporary zone cleanup.
* Display Entity cleanup.
* Projectile cleanup.
* Mark and clone cleanup.

When the plugin reloads or disables, do not leave broken ability states behind.

Do not claim reload safety if the plugin does not actually support safe reload behavior. If a full server restart is recommended, document that clearly.

---

# 21. ADMIN SECURITY AND ITEM PROTECTION

Implement safe sword handling.

Requirements:

* Authorized give-sword commands.
* Permission checks.
* No unintended duplication.
* Correct item identification.
* Prevent spoofed item names from granting abilities.
* Use persistent item identifiers or equivalent reliable identification.
* Do not trust lore alone as an item identity.
* Prevent invalid items from activating abilities.
* Validate the sword in the player's hand.
* Ensure command inputs are validated.
* Handle inventory-full situations safely.
* Do not remove the wrong item from a player's inventory.
* Protect against unintended item consumption during ability activation.

If the player configures Drop Key or Offhand Swap as an ability input, ensure the control does not accidentally destroy or drop the sword.

---

# 22. VISUAL IMPLEMENTATION STANDARD

The visual quality must aim for premium custom Minecraft PvP.

Use the following design rules:

## Directional effects

A beam, dash, projectile, and sword strike must have a clear direction.

## Layered effects

Combine several complementary particle shapes rather than relying on one particle type.

## Timing

Synchronize animation phases with sound and mechanics.

## Color consistency

Each sword has a distinct color palette. Do not mix random colors without a design reason.

## Scale

Use appropriate visual scale. An ultimate can be large, but its size must not make the entire battlefield unreadable.

## Motion

Where appropriate, use:

* Spirals.
* Arcs.
* Rotations.
* Trails.
* Converging particles.
* Expanding shockwaves.
* Vertical movement.
* Directional bursts.

## Contrast

Make effects visible against common Minecraft environments, including dark caves, plains, and the Nether.

Do not rely only on extremely bright particles or constant screen-covering explosions.

---

# 23. TESTING REQUIREMENTS

Before claiming the plugin is complete, test:

* Plugin startup.
* Commands.
* Permissions.
* Sword giving.
* Item identification.
* Primary ability activation.
* Secondary ability activation.
* Cooldown enforcement.
* Boss bar visibility.
* Keybind configuration.
* Persistent settings.
* Invalid target behavior.
* Multiple players using abilities.
* Player disconnect during ability.
* Plugin disable cleanup.
* Reload behavior where supported.
* Resource-pack installation steps.
* Damage and status-effect behavior.
* Temporary entity cleanup.
* Water counter behavior.
* Overlapping ability zones.
* Performance with multiple active abilities.

Fix compilation errors and runtime exceptions.

Do not claim that a feature was tested if it was not actually tested.

---

# 24. FINAL DELIVERABLE

Provide a complete project that includes:

1. Source code.
2. Build configuration.
3. Plugin configuration.
4. Commands and permissions.
5. Resource-pack asset structure or included assets.
6. Installation instructions.
7. Configuration documentation.
8. Ability descriptions.
9. Testing instructions.
10. Known limitations.
11. Build output instructions.

The plugin must be structured so it can be extended later.

Do not omit major abilities or replace them with generic placeholders without explaining what remains unfinished.

# FINAL NON-NEGOTIABLE RULE

**ALL 12 SWORDS HAVE ONLY TWO ABILITIES: PRIMARY + SECONDARY.**

**THERE ARE ZERO PASSIVE ABILITIES.**

Do not add passive mechanics to any sword.

Every ability must be manually activated through the configured player control.

Make the visuals impressive, the combat readable, the mechanics reliable, and the plugin genuinely usable on a Minecraft server.
Kodari AI
KodariSep 25 at 9:53 pm 2
AdminSwords
A premium Minecraft PvP plugin featuring 12 unique admin swords, each with a primary and secondary manually-activated ability. Includes custom resource-pack textures, layered particle VFX, distinct sound design, configurable cooldowns with player-only boss bars, a keybind configuration GUI, persistent player settings, and robust server-side ability state management with full cleanup. Features an event-driven inventory GUI framework for menus and a centralized ability manager ensuring reliable targeting, damage, and status effects. All abilities are active-only with no passive mechanics, emphasizing readable combat indicators and polished visual feedback.

Plan:

  1. Review the public Altar and Hoplite pages for visual and gameplay references.

  2. Create the plugin project around the 12 swords, manual-only abilities, safe item identity, cooldowns, and configurable controls.

  3. Include build/configuration files and clearly document any implementation limits rather than claiming unimplemented mechanics.

Created the Paper 1.21.11 / Java 21 AdminSwords project with all 12 sword IDs and 24 manually activated ability paths. It includes tagged sword items, /sword give|menu|list, persisted per-player controls, configurable cooldowns, and player-only boss bars.

Research findings:

  • Altar SMP: altar.gg currently shows a domain-for-sale page, so I couldn’t inspect its visuals or assets.

  • Hoplite: Its public site highlights Battle Royale and Duels, server resource packs, and cosmetic progression. The project uses only general combat-readability cues; it includes no copied assets or branding.

The implementation is a playable foundation, not the full supplied design brief: true damage currently uses normal Bukkit damage, detailed ability stages and several specified mechanics are simplified, and no custom textures or resource pack are included. These limitations are documented in README.md. I haven’t run the build or runtime tests.

Dhruv Bahirgonde

what i mean is research altarsmp youtube vidoes and the swords in it for visual refrences and looks to do mine and then look at hoplite swords to then make my plugin with visuals and everything els

Kodari AI
KodariSep 25 at 11:02 pm 1

Understood—you want me to research AltarSMP’s swords and Hoplite’s swords as visual references, then use those ideas to build out your plugin—not make a generic sword plugin.

I couldn’t get YouTube’s search results to expose the actual videos, so send me the AltarSMP video or channel you mean, plus any Hoplite reference you have. I’ll use them for inspiration and create original designs. For truly distinct sword appearances, the plugin will likely need a companion resource pack; otherwise, visuals are limited to vanilla items and effects.

Dhruv Bahirgonde

https://www.youtube.com/watch?v=KmWfgDqW82Q and https://www.youtube.com/watch?v=ZTk59IxIpB4 the one i sent is just for visual ability refrences and also do custom sword models IGNORE HOPLITE IN THIS JUST DO ALTAR

Kodari AI
KodariSep 25 at 11:18 pm 1
  1. Research the two AltarSMP videos for sword designs and ability visuals.

  2. Apply those references to the existing plugin, including custom sword models and their visuals.

The links are reachable, but this workspace exposes neither their video frames nor captions, so I can’t verify AltarSMP’s exact sword designs or ability effects. I’m adding original themed models for the plugin’s existing swords, generating a resource-pack ZIP on startup, and supporting optional delivery from a hosted URL.

Added original custom-textured models for all 12 existing swords. The plugin now generates plugins/AdminSwords/adminswords-resource-pack.zip on startup and can prompt players to download it when they join. Upload the ZIP to a direct-download host and set its URL in resource-pack.url in config.yml.

I couldn’t access video frames or captions from those links here, so these models aren’t verified matches for AltarSMP. The existing ability effects are unchanged; screenshots or timestamps would let me match the references more closely.

Dhruv Bahirgonde

WWLL I JUST WANT AS GOOD AS VISUALS JUST LOOK AST THE WHOLE VIDOE

Kodari AI
KodariSep 25 at 11:26 pm 1

You’re right—I didn’t actually watch the videos, so the swords I added aren’t based on their visuals. I can’t view YouTube frames from those links in this workspace.

Upload the video files or screenshots/screen recordings showing the swords and their abilities, and I can use those as references to update the models and effects. The current visuals are original placeholders, not AltarSMP-matched.

Dhruv Bahirgonde

can yorself reseaarcv images form the ltaest season of altar and then make my plugin

Kodari AI
KodariSep 26 at 2:10 am 1
  1. Find recent AltarSMP season sword images and identify the visual themes.

  2. Update your plugin’s sword models and effects to match those references.

The searches and video pages didn’t provide viewable sword images, so I can’t honestly claim these match AltarSMP’s latest season. I’m upgrading the plugin’s existing pack with distinct, detailed designs for each sword theme and keeping the current ability effects intact.

Updated the resource-pack generator so all 12 swords get larger, individually themed textures—web, crimson vine, sun, dragon, wind, shadow, warden, poison, void, frost, solar, and infernal. The existing ability effects are unchanged.

I couldn’t verify these against AltarSMP’s latest season: the image searches and video pages didn’t expose viewable sword images or frames. These are original designs based on the themes already in your plugin, not confirmed copies of the season’s visuals.

Dhruv Bahirgonde

make it where all sowrds dont look the same but diffrent colords give all sowrd custom texture some are like blasde some are katana shade dagger is the dagger you might lumini could be a light spear byt a sword combination look make ke them all look diffrent not just in color but texture and then make abilitys have animation like these 4th one is a holagram of the weapon attracking so these are how good i want the asbilitys to look AS GOOD AS THESE NOT JUST PARTICLES IN THE RESCOURCE PACK YOU CURRENTLY MAD ADD ALL THESE CHANGES AND DEIGHN ABILITY MODELS LIIKE THESE THAT MATCH EACH SOWRD I GAVE YOU FOR SHADE_DAGGER MAKE DAGGERS ORBIT AND HAV A DARK TRIAL WHEN SHOT STUFF LIK THAT USE THESE IMAGES ONLT TO UNDERSTAND HOW GOOD THE MODELS HAVE TO BE AND HOW ITS NOT JUST PARTICLES BUT THIS MAKE SURE YOU DO EVERYTING THE PROMPT DESCRIBED

5 images attached
Kodari AI
KodariSep 26 at 2:31 am 2
  1. Give each existing sword a distinct silhouette and texture, including dagger and light-spear designs.

  2. Add weapon-shaped ability animations—especially Shade Dagger orbiting daggers, dark trails, and holographic weapon attacks—instead of relying on particles alone.

Updated the plugin’s visuals:

  • All 12 swords now have distinct silhouettes and details—not just recolored copies—including a compact Shade Dagger, a light-spear Lumina, a curved Atherion blade, a crescent Voidreaver, and broader, jagged, winged, or crystalline designs for others.

  • Successful abilities now send glowing holograms of their matching custom sword model forward with a themed trail.

  • Shade Dagger’s primary ability sends three daggers orbiting the player before they launch at the target, leaving a dark trail. Shadow Execution uses two orbiting daggers before its strike.

Players need to download and enable the generated resource pack to see the custom sword designs and holograms.

Kodari can make mistakes. Review important code before using.
Files
src
build.gradle
README.md
settings.gradle
Code
17 1,859
src/main/java/dev/kodari/adminswords/AdminSwordsPlugin.java
package dev.kodari.adminswords;

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

import java.io.IOException;
import java.util.logging.Level;

public final class AdminSwordsPlugin extends JavaPlugin {
    private PlayerSettings playerSettings;
    private SwordItems swordItems;
    private CooldownManager cooldowns;
    private AbilityEngine abilities;

    @Override
    public void onEnable() {
        saveDefaultConfig();
        try {
            getLogger().info("Generated sword resource pack: " + new ResourcePackGenerator(this).generate());
        } catch (IOException exception) {
            getLogger().log(Level.SEVERE, "Could not generate the sword resource pack.", exception);
        }
        playerSettings = new PlayerSettings(this);
        swordItems = new SwordItems(this);
        cooldowns = new CooldownManager(this);
        abilities = new AbilityEngine(this);
        AbilityListener listener = new AbilityListener(this);
        Bukkit.getPluginManager().registerEvents(listener, this);
        Bukkit.getPluginManager().registerEvents(new ResourcePackListener(this), this);
        SwordCommands commands = new SwordCommands(this);
        getCommand("sword").setExecutor(commands);
        getCommand("sword").setTabCompleter(commands);
        getCommand("cooldown").setExecutor(commands);
        getCommand("cooldown").setTabCompleter(commands);
    }

    @Override
    public void onDisable() {
        if (abilities != null) abilities.shutdown();
        if (cooldowns != null) cooldowns.shutdown();
        if (playerSettings != null) playerSettings.save();
    }

    public PlayerSettings playerSettings() { return playerSettings; }
    public SwordItems swordItems() { return swordItems; }
    public CooldownManager cooldowns() { return cooldowns; }
    public AbilityEngine abilities() { return abilities; }
}