5k4g
📎 1 file 20,459 chars
📄
pasted-code-1790257232051.txt
txt 1203 lines
▶
# WTotems — Minecraft Plugin Development Specification

Build a production-ready Minecraft server plugin called **WTotems**.

WTotems is a custom PvP plugin centered around **10 unique craftable WTotems**. Each WTotem has:

* 1 passive ability
* 1 active ability
* A configurable active cooldown
* A unique visual/audio identity
* Per-totem statistics
* Custom chat/death messages

The plugin should feel polished, lightweight, highly configurable, and suitable for a real multiplayer PvP server.

---

# 1. CORE RULE — ONE CUSTOM WTOTEM PER PLAYER

A player may possess **ONLY ONE custom WTotem at a time**.

This restriction applies to:

* Main inventory
* Hotbar
* Offhand
* Pickups
* Crafting results
* Trading
* Containers
* Plugin-generated WTotems
* `/wtotems give`

The plugin must prevent bypassing the restriction through containers such as:

* Chests
* Barrels
* Shulker boxes
* Ender chests
* Other inventories/containers

If a player already owns a WTotem and somehow attempts to obtain another:

**The newly obtained WTotem must be discarded/destroyed.**

Do NOT remove or destroy the player's existing WTotem.

Show a configurable message such as:

`⚠ You can only have 1 WTotem at a time!`

### IMPORTANT:

Normal vanilla **Totem of Undying** items are completely unaffected.

Players may have:

* Multiple normal Totems of Undying
* One custom WTotem

The vanilla Totem of Undying must NEVER count toward the WTotem limit.

---

# 2. WTOTEMS

There are exactly 10 WTotems in the initial release.

Do not invent additional totems.

---

## 🔥 1. STRENGTH TOTEM

### Passive — Strength II

Player permanently receives:

**Strength II**

while the Strength Totem is active/equipped.

### Active — Berserk

When activated:

The player's next **5 melee hits** deal **Strength III-level damage**.

The effect is consumed after 5 valid melee hits.

Cooldown:

**30 seconds**

Do not allow ranged attacks to consume Berserk hits.

Make sure invalid attacks do not consume charges.

Track:

* Berserk activations
* Hits landed during Berserk
* Kills while using Strength Totem
* Damage dealt if practical

---

# ⚡ 2. SPEED TOTEM

### Passive — Speed I

Permanent:

**Speed I**

### Active — Dash

Dash the player forward approximately:

**6–8 blocks**

Cooldown:

**27 seconds**

The dash should:

* Move the player forward
* Respect basic collision/safety checks
* Avoid teleporting the player into solid blocks
* Have configurable particles/sound

Track:

* Dash activations
* Distance/dashes if practical
* Kills while equipped

---

# 🛡️ 3. GUARD TOTEM

### Passive — Resistance I

Permanent:

**Resistance I**

### Active — Iron Will

Duration:

**5 seconds**

During the ability, the player cannot be killed.

Apply a Turtle Master-style defensive effect equivalent to:

**Resistance IV + Slowness**

The player should still be able to participate in combat, but the ability is primarily defensive.

Cooldown:

**65 seconds**

This is one of the strongest abilities, so do NOT make its cooldown shorter than specified.

---

# 🎰 4. GAMBLER TOTEM

### Passive — Pickpocket

Every melee hit has a:

**5% chance**

to steal:

**$20,000–$50,000**

from the enemy's vault.

Use the server's available economy integration if present.

The passive may trigger against a specific target only once every:

**3 seconds**

Do not repeatedly trigger Pickpocket every hit.

If an economy plugin is unavailable, fail gracefully rather than crashing.

### Active — All In

Duration:

**6 seconds**

During All In, melee hits have a chance to lock one of the enemy's hotbar slots for:

**4 seconds**

A locked slot:

* Is NOT removed
* Is NOT dropped
* Cannot be selected/used while locked
* Should have a clear lock indicator

The affected player should see a visual indicator over/around the locked hotbar slot where technically possible.

Do not delete or modify the actual item.

Cooldown:

**45 seconds**

Track:

* Money stolen
* Pickpocket triggers
* All In activations
* Hotbar locks

---

# 🌪️ 5. WIND TOTEM

### Passive — Windborne

Permanent:

* Speed I
* Reduced fall damage

### Active — Updraft

Create a massive wind explosion centered on the activating player.

Radius:

**10–12 blocks**

Affected players are launched:

**15–20 blocks horizontally**

and:

**8–12 blocks upward**

The owner of the Wind Totem is completely unaffected.

The ability:

* Deals NO damage
* Does NOT destroy blocks
* Primarily exists for knockback/mobility/control

Cooldown:

**40 seconds**

Track Updraft activations and affected players.

---

# 🐙 6. OCTOPUS TOTEM

### Passive — Ink

When the player is hit:

There is a small configurable chance to create a brief blindness cloud.

The passive should have an internal cooldown to prevent excessive triggering.

### Active — Ink Cloud

Create an:

**8-block-radius**

ink cloud lasting:

**6 seconds**

Players inside:

* Have impaired vision
* Receive the configured blindness/vision effect

The owner:

* Can see normally
* Has enhanced visibility if technically possible

Cooldown:

**40 seconds**

The cloud should have strong visual identity using particles.

Track:

* Ink Cloud activations
* Players affected
* Passive Ink triggers

---

# 🐝 7. BEE TOTEM

### Passive

Whenever the owner is hit:

There is a configurable chance to spawn:

**1 bee**

The bee targets the player who hit the owner.

The bee should have reasonable temporary lifetime and should not create permanent entity buildup.

### Active — Bee Swarm

Summon a swarm of bees that attacks players who have hit the owner.

Duration:

**25 seconds**

Cooldown:

**50 seconds**

The system must prevent uncontrolled entity spam.

Track:

* Bees spawned
* Bee Swarm activations
* Players attacked
* Kills if practical

---

# 🐺 8. WOLF TOTEM

### Passive — Pack Instinct

Whenever the owner is hit:

There is a configurable chance to spawn:

**1 wolf**

The wolf targets the player who hit the owner.

Wolf properties:

* Wolf armor/custom appearance if available
* Strength II
* Speed II
* Increased health
* Targets the attacker
* Temporary lifetime

The wolf lasts:

**25 seconds**

### Active — Call of the Pack

Summon:

**11–20 armored wolves**

The wolves have:

* Wolf armor/custom appearance
* Strength II
* Speed II
* Increased health
* Aggro toward players who attack the owner

Duration:

**25 seconds**

Cooldown:

**70 seconds**

This is the longest cooldown in the plugin.

Implement an entity limit so multiple uses cannot cause server performance problems.

Track:

* Wolves summoned
* Pack activations
* Players attacked
* Kills

---

# 🧿 9. HEX / CURSE TOTEM

Use the final agreed concept as the **Hex/Curse Totem**.

### Passive — Hex

Every **4th melee hit** applies a random minor curse to the target.

Possible curses:

* Slowness
* Weakness
* Mining Fatigue
* Nausea

Duration:

**3 seconds**

Keep the effect relatively minor.

Implement a per-player internal cooldown so it cannot be abused through extremely fast attacks.

### Active — Bad Luck

Duration:

**6 seconds**

While active:

Whenever the enemy attempts to activate their custom ability, there is a:

**30% chance**

that the ability fails and its cooldown is consumed.

The ability should NOT activate.

This should only interact with custom WTotem abilities, not arbitrary Minecraft actions.

Cooldown:

**55 seconds**

Track:

* Hex triggers
* Bad Luck activations
* Abilities successfully disrupted

---

# 👁️ 10. HUNTER TOTEM

### Passive — Marked

The first player hit becomes:

**Hunted/Marked**

Duration:

**20 seconds**

The owner can see the target's approximate location/distance through walls within:

**25 blocks**

The target should have an obvious but clean indicator that they are hunted.

### Active — Executioner

Can primarily interact with the currently hunted target.

Duration:

**4 seconds**

Attacks against the hunted target apply a stacking:

**1-second Slowness**

If the target gets more than:

**20 blocks**

away, the active effect ends.

Cooldown:

**45 seconds**

Track:

* Players marked
* Hunted targets caught
* Executioner activations
* Hunted kills

---

# 3. COOLDOWNS

These cooldowns are intentional.

Do NOT reduce them.

| Totem    | Ability          | Cooldown |
| -------- | ---------------- | -------: |
| Strength | Berserk          |      30s |
| Speed    | Dash             |      27s |
| Guard    | Iron Will        |      65s |
| Gambler  | All In           |      45s |
| Wind     | Updraft          |      40s |
| Octopus  | Ink Cloud        |      40s |
| Bee      | Bee Swarm        |      50s |
| Wolf     | Call of the Pack |      70s |
| Hex      | Bad Luck         |      55s |
| Hunter   | Executioner      |      45s |

Minimum cooldown:

**27 seconds**

Maximum cooldown:

**70 seconds**

---

# 4. CRAFTING

All 10 WTotems must be **normally craftable through a crafting table**.

Recipes must be fully configurable.

Do NOT hardcode recipes.

Use a simple `recipes.yml`.

The configuration should be easy for a server owner to understand.

Preferred format:

```yaml
strength:
  recipe:
    - [GOLD_INGOT:2, AIR, BLAZE_ROD]
    - [GOLD_INGOT, NETHERITE_SCRAP, GOLD_INGOT]
    - [AIR, GOLD_INGOT:2, AIR]
```

Meaning:

* 3 rows
* 3 slots per row
* `AIR` = empty
* `ITEM` = one item
* `ITEM:AMOUNT` = specified quantity

Example:

`DIAMOND:3`

means 3 diamonds are required in that slot.

Recipe item type and quantity must both be configurable.

The plugin should validate recipes and provide a clear admin error if a material is invalid.

---

# 5. CRAFTING + ONE-TOTEM LIMIT

When a player crafts a WTotem:

### If they have no WTotem:

Give them the crafted WTotem normally.

### If they already have a WTotem:

The newly crafted WTotem is discarded.

Their existing WTotem remains untouched.

Display a configurable message.

Do not prevent the recipe from functioning in the crafting table itself.

---

# 6. WTotem ITEM

Each WTotem should have a unique custom item identity.

The item should have:

* Custom name
* Custom lore
* Custom model data support
* Persistent data identifier
* Optional glow
* Unique texture/model support

Do NOT identify WTotems solely by display name.

Use persistent data/NBT/PDC so renamed items cannot accidentally become WTotems.

Example:

```text
🔥 Strength Totem
```

Lore can show:

```text
Passive: Strength II
Active: Berserk
Cooldown: 30s
```

Make all text configurable.

---

# 7. EQUIPPING / ACTIVE WTOTEM

The plugin must know which WTotem belongs to the player.

The WTotem can be in:

* Inventory
* Hotbar
* Offhand

The player may only possess one.

Normal Totems of Undying do not count.

Add protection against moving a WTotem into prohibited container locations if that would bypass the one-totem system.

---

# 8. COMBAT PROTECTION

Add a configurable option:

```yaml
combat:
  prevent_totem_switching: true
```

If enabled, players cannot abuse inventory manipulation to switch WTotems during combat.

If only one WTotem is allowed anyway, the plugin should primarily prevent weird inventory/container exploits.

---

# 9. STATS

Do NOT create a mastery or level system.

There are:

**NO LEVELS.**

**NO XP.**

**NO MASTERY GRIND.**

Instead, track simple statistics for each totem.

Example:

```text
🔥 Strength Totem — Statistics

Kills: 47
Berserk Activations: 91
Hits During Berserk: 412
Damage Dealt: 18,420
```

Each totem should have statistics relevant to its mechanics.

Examples:

### Wolf

```text
🐺 Wolf Totem

Kills: 23
Pack Summons: 18
Wolves Summoned: 247
Players Attacked: 86
```

### Gambler

```text
🎰 Gambler Totem

Kills: 12
Money Stolen: $1,240,000
Pickpocket Triggers: 38
All In Activations: 21
Hotbar Locks: 17
```

Stats should persist across restarts.

---

# 10. COMMANDS

## Player commands

```text
/wtotems
```

Open the main WTotems GUI.

```text
/wtotems list
```

List all 10 WTotems.

```text
/wtotems info 
```

Show:

* Passive
* Active
* Cooldown
* Description
* Stats if appropriate

```text
/wtotems recipe 
```

Show the configured crafting recipe.

```text
/wtotems stats
```

Show the player's WTotem statistics.

```text
/wtotems cooldown
```

Show the player's active cooldown.

```text
/wtotems achievements
```

Optional simple achievement display if implemented, but do NOT turn achievements into a progression/level system.

## Admin commands

```text
/wtotems give  
/wtotems reload
/wtotems toggle  
/wtotems resetcooldown  [totem]
/wtotems clear 
/wtotems debug 
/wtotems inspect 
```

### `/wtotems inspect `

Display useful admin information:

```text
Player: Steve
WTotem: Wolf
Cooldown: 37s
Active Wolves: 7
Total Activations: 284
```

---

# 11. GUI

`/wtotems` should open a polished GUI.

Show all 10 WTotems.

Clicking a WTotem opens its information:

```text
🔥 STRENGTH TOTEM

Passive
Strength II

Active
Berserk

Next 5 melee hits
deal Strength III damage.

Cooldown
30 seconds

[View Recipe]
[View Stats]
```

Do not make the GUI required for normal gameplay.

It is an information/convenience system.

---

# 12. CHAT MESSAGES

All WTotem messages should be configurable.

Messages should be colorful, clean, and not spammy.

Examples:

### Equip

```text
🔥 WTotems » Strength Totem equipped.
```

```text
⚡ WTotems » Speed Totem equipped.
```

### Ability

```text
⚡ WTotems » Dash activated!
```

```text
🌪️ WTotems » Updraft unleashed!
```

```text
🐺 WTotems » The Pack has been summoned!
```

### Enemy notification

Only the affected player should receive important private notifications where appropriate.

Example:

```text
🧿 HEXED!
Your active ability has been disrupted.
```

### Cooldown

```text
✖ Your Wolf Totem is on cooldown for 42s.
```

Do not flood chat every tick.

---

# 13. TOTEM-SPECIFIC DEATH MESSAGES

If a WTotem was meaningfully involved in a kill, use a special death message.

Examples:

```text
🔥 Steve was slain by Alex using the Strength Totem.
```

```text
⚡ Steve couldn't escape Alex's Speed Totem.
```

```text
🐺 Steve was overwhelmed by Alex's Pack.
```

```text
🧿 Steve was HEXED by Alex.
```

```text
👁️ Steve was hunted down by Alex.
```

```text
🌪️ Steve was blown away by Alex's Wind Totem.
```

```text
🐙 Steve disappeared into Alex's Ink Cloud.
```

If no WTotem was involved, use the normal Minecraft death message.

Death messages should be configurable.

---

# 14. EFFECTS

Every WTotem should have a unique visual/audio identity.

Support configurable:

* Particles
* Sounds
* Effect duration
* Effect radius
* Colors where applicable
* Activation sound
* Cooldown sound if desired

Do not hardcode all presentation.

Example:

```yaml
effects:
  strength:
    sound: ENTITY_PLAYER_ATTACK_STRONG
    particles: FLAME

  speed:
    sound: ENTITY_PLAYER_ATTACK_SWEEP
    particles: CLOUD
```

---

# 15. WORLD CONFIGURATION

Allow server owners to disable WTotems in specific worlds.

Example:

```yaml
worlds:
  world: true
  world_nether: true
  world_the_end: false
```

The plugin should gracefully prevent abilities from functioning where disabled.

---

# 16. REGION / PROTECTION COMPATIBILITY

WTotems should respect normal server protection where possible.

Especially:

* Wind knockback
* Dash
* Teleport-like mechanics if added
* Entity spawning
* Block interaction

Do not destroy terrain with WTotem abilities.

WTotems should not bypass protected-region restrictions.

---

# 17. ENTITY SAFETY

Bee and Wolf abilities must be designed with server performance in mind.

Implement:

* Maximum active WTotem entities per player
* Temporary entity cleanup
* Automatic cleanup when duration ends
* Cleanup when owner disconnects
* Cleanup when entity becomes invalid

Do not allow players to create infinite wolves/bees.

Wolf active:

Maximum spawned by one activation:

**20**

---

# 18. CONFIGURATION FILES

Keep configuration organized.

Recommended files:

```text
config.yml
recipes.yml
messages.yml
effects.yml
stats.yml
```

`recipes.yml` handles recipes.

`messages.yml` handles all text.

`effects.yml` handles particles/sounds.

`config.yml` handles general plugin settings.

Do not force server owners to edit Java/code.

---

# 19. RELOAD

`/wtotems reload`

should safely reload:

* Recipes
* Messages
* Effects
* General settings
* Enabled/disabled totems

Do not require a server restart for normal configuration changes.

---

# 20. PERMISSIONS

Use permissions such as:

```text
wtotems.use
wtotems.admin
wtotems.give
wtotems.reload
wtotems.toggle
wtotems.resetcooldown
wtotems.clear
wtotems.debug
wtotems.inspect
```

Normal players should not have admin permissions.

---

# 21. PERFORMANCE

WTotems must be lightweight.

Avoid:

* Constant expensive repeating tasks
* Unnecessary scans of every player
* Uncontrolled entity creation
* Excessive particle spam
* Excessive database writes

Use efficient cooldown handling.

Stats should be saved safely and not written to disk on every single hit.

---

# 22. ANTI-EXPLOIT REQUIREMENTS

Prevent:

* Duplicating WTotems through crafting
* Duplicating WTotems through containers
* Moving WTotems into prohibited storage
* Bypassing the one-WTotem limit
* Renaming normal items to imitate WTotems
* Exploiting crafting shift-click
* Exploiting death drops
* Exploiting disconnect/reconnect
* Exploiting item movement events
* Exploiting plugin reloads
* Exploiting entity spawning

The one-WTotem rule must remain authoritative.

---

# 23. IMPORTANT DESIGN RULES

Do NOT:

* Add additional WTotems
* Add random RPG levels
* Add XP/mastery
* Add unnecessary currencies
* Add pay-to-win mechanics
* Change the specified cooldowns
* Give players permanent stacking combat bonuses beyond the defined passives
* Turn vanilla Totems of Undying into WTotems
* Make WTotems impossible to craft

WTotems should remain focused on:

**10 unique PvP abilities + crafting + stats + polished presentation.**

---

# 24. FINAL WTotem COOLDOWN TABLE

```text
🔥 Strength      30s
⚡ Speed          27s
🛡️ Guard         65s
🎰 Gambler       45s
🌪️ Wind          40s
🐙 Octopus       40s
🐝 Bee            50s
🐺 Wolf           70s
🧿 Hex            55s
👁️ Hunter         45s
```

Minimum: **27 seconds**

Maximum: **70 seconds**

---

# 25. QUALITY BAR

WTotems should feel like a polished premium PvP plugin.

Prioritize:

* Smooth combat
* Clear feedback
* Strong visual identity
* Configurability
* Performance
* Anti-exploit protection
* Clean GUI
* Clean chat
* Unique mechanics
* Fair counterplay

Do not overcomplicate the user experience.

The plugin should be easy for a server owner to configure while still feeling extremely polished to players.

Before considering the plugin complete, test:

1. Crafting all 10 WTotems
2. One-WTotem restriction
3. Container bypasses
4. Shift-click crafting
5. Death/rejoin behavior
6. Every passive
7. Every active
8. Every cooldown
9. Every special death message
10. Stats persistence
11. `/wtotems reload`
12. Entity cleanup
13. Disabled worlds
14. Invalid recipes
15. Vanilla Totem of Undying compatibility
16. Multiple players using the same WTotem simultaneously
17. Multiple players using different WTotems simultaneously

The final result should be **WTotems**, not a generic RPG ability plugin.
Kodari AI
KodariSep 24 at 1:41 pm 1
  1. Set up the Paper plugin, configurable items/recipes/messages, and persistent stats.

  2. Implement one-WTotem inventory protection, passives, actives, cooldowns, and temporary entity cleanup.

  3. Add player/admin commands and the information GUI.

[Generation stopped]

5k4g
📎 1 file 28,412 chars
📄
pasted-code-1790298243380.txt
txt 1624 lines
▶
# WTotems — Master Minecraft PvP Plugin Development Prompt

Build a complete, production-ready Minecraft PvP plugin called **WTotems**.

This is not supposed to be a basic MVP or a proof of concept. The finished plugin should feel like a **premium, polished PvP plugin that could be installed on a serious Minecraft server immediately**.

The goal is not to make the plugin unnecessarily huge. The goal is to make the specified systems **extremely well implemented, polished, reliable, configurable, visually satisfying, performant, and difficult to exploit**.

Do not add random gameplay systems just to increase the feature count.

If something is not explicitly specified, use a **simple, sensible, lightweight implementation** that fits the existing design rather than inventing new mechanics.

---

# CORE CONCEPT

WTotems adds exactly **10 custom craftable PvP WTotems**.

Each WTotem has:

* A unique identity
* A passive ability
* An active ability
* A configurable cooldown
* Unique visuals
* Unique sounds
* Unique chat feedback
* Individual statistics
* A custom item appearance
* A configurable crafting recipe

The 10 WTotems are:

1. 🔥 Strength
2. ⚡ Speed
3. 🛡️ Guard
4. 🎰 Gambler
5. 🌪️ Wind
6. 🐙 Octopus
7. 🐝 Bee
8. 🐺 Wolf
9. 🧿 Hex
10. 👁️ Hunter

There must be exactly 10 custom WTotems in V1.

Do not create additional WTotems.

---

# ONE CUSTOM WTOTEM PER PLAYER

A player may own/equip **only ONE custom WTotem at a time**.

This restriction applies to all 10 custom WTotems.

IMPORTANT:

The normal Minecraft **Totem of Undying is completely separate**.

A player may have:

* Multiple vanilla Totems of Undying
* One custom WTotem

at the same time.

A vanilla Totem of Undying must never count as a WTotem.

If a player already has a WTotem and obtains another WTotem:

* The new WTotem is discarded.
* The existing WTotem remains.
* Never replace the existing WTotem automatically.
* Give the player a configurable message explaining why the new WTotem was discarded.

This rule must be enforced everywhere possible, including:

* Normal crafting
* Shift-click crafting
* Crafting result movement
* Inventory movement
* Item pickups
* Dropping/picking up
* Chests
* Barrels
* Shulkers
* Ender chests
* Hoppers
* Trades
* Plugin-generated items
* `/give`
* Death drops
* Other common item acquisition methods

Do not rely on item names or lore to identify WTotems.

Use Minecraft's **PersistentDataContainer / persistent item data / unique internal IDs**.

For example:

```text
wtotems:strength
wtotems:speed
wtotems:guard
wtotems:gambler
wtotems:wind
wtotems:octopus
wtotems:bee
wtotems:wolf
wtotems:hex
wtotems:hunter
```

Renaming an item must not turn it into a WTotem.

Players must not be able to create fake WTotems by copying lore/name.

---

# WTOTEM ITEM DESIGN

Every WTotem item should feel like a special custom server item.

Each item should support:

* Unique display name
* Unique icon/material
* Clean lore
* Passive description
* Active description
* Cooldown
* Optional enchantment glow
* Custom Model Data
* Custom textures/models where supported
* Unique persistent item ID

Lore should be clean and readable rather than a giant wall of text.

Example style:

```text
🔥 Strength Totem

Passive
Strength II

Active
Berserk

Cooldown
30 seconds

Next 5 melee hits deal
increased damage.
```

The exact lore should be configurable.

---

# THE 10 WTOTEMS

## 1. 🔥 STRENGTH TOTEM

### Passive — Strength

The owner permanently has:

**Strength II**

while using the Strength Totem.

### Active — Berserk

Activate Berserk.

The next **5 valid melee hits** deal approximately **Strength III-level damage**.

Rules:

* Only valid melee attacks consume a Berserk hit.
* Ranged attacks do not consume charges.
* Invalid attacks do not consume charges.
* The ability should clearly show when Berserk is active.
* Give satisfying hit feedback while Berserk is active.
* After 5 valid hits, Berserk ends.
* Berserk cannot be abused through invalid attack events.

Cooldown:

**30 seconds**

Suggested statistics:

* Kills
* Berserk activations
* Hits during Berserk
* Damage dealt

Visual identity:

* Flame particles
* Aggressive impact effects
* Strong attack sound
* Short activation burst
* Distinctive Berserk hit feedback

Do not spam particles every hit unnecessarily.

---

# 2. ⚡ SPEED TOTEM

### Passive — Speed

Permanent:

**Speed I**

### Active — Dash

Dash the player forward approximately **6–8 blocks**.

Implement proper safety checks.

The dash should not intentionally:

* Clip through solid walls
* Teleport players into invalid locations
* Put players inside blocks
* Cause ridiculous fall/death situations

Check the path/landing position and use a safe movement implementation.

Make distance and strength configurable.

Cooldown:

**27 seconds**

Suggested statistics:

* Dash activations
* Distance dashed
* Kills

Visual identity:

* Electric/speed particles
* Short movement trail
* Fast activation sound
* Burst at activation
* Clear cooldown feedback

---

# 3. 🛡️ GUARD TOTEM

### Passive — Guard

Permanent:

**Resistance I**

### Active — Iron Will

Activate Iron Will.

Duration:

**5 seconds**

During this time:

* Player cannot be killed.
* Apply approximately Turtle Master-style defensive effects.
* Resistance IV
* Slowness

This is intentionally one of the strongest abilities.

Its strength is balanced primarily through its long cooldown.

The implementation must correctly handle:

* Extremely large damage
* Fire
* Fall damage
* PvP damage
* Environmental damage
* Other common damage sources

Do not leave permanent potion effects after the ability ends.

Cooldown:

**65 seconds**

Suggested statistics:

* Iron Will activations
* Damage prevented
* Kills

Visual identity:

* Protective particles
* Heavy defensive sound
* Shield-like visual burst
* Clear active-state indication

---

# 4. 🎰 GAMBLER TOTEM

## Passive — Pickpocket

Every valid melee hit has a:

**3% chance**

to trigger Pickpocket.

On a successful Pickpocket:

* Steal a random amount between **$2,000 and $8,000**
* Remove the money from the target's available balance.
* Give the stolen amount to the Gambler owner.
* Target can never go below `$0`.
* If target has less than `$2,000`, Pickpocket does not trigger.
* Same target can only trigger Pickpocket once every **5 seconds**.
* Ranged attacks do not trigger Pickpocket.
* There is **NO daily cap**.

The economy system must be optional.

If no compatible economy provider exists:

* Pickpocket should gracefully disable.
* Gambler's All In ability must still work.
* Plugin must not throw errors.
* Plugin must not crash.

Use the economy provider's proper balance APIs.

Never:

* Create money from nothing
* Allow negative balances
* Process the same theft twice
* Duplicate money during reconnects/reloads/death

Successful Pickpocket should have satisfying configurable feedback.

Example:

```text
🎰 WTotems » You pickpocketed $4,250 from Steve!
🎰 WTotems » Alex pickpocketed $4,250 from you!
```

Do not spam the target unnecessarily if Pickpocket fails.

## Active — All In

Duration:

**6 seconds**

During All In:

* Valid melee hits have a configurable chance to lock one enemy hotbar slot.
* Default lock duration: **4 seconds**.
* The item remains in the slot.
* The item is NOT removed.
* The item is NOT destroyed.
* The item is NOT dropped.
* The player cannot select/use the locked slot while it is locked.

The affected player should receive a clear visual indication of the locked slot where technically possible.

Prevent excessive stacking.

Use a configurable maximum number of simultaneously locked slots.

Clean all locks correctly if:

* Effect expires
* Player dies
* Player disconnects
* Plugin reloads
* Target becomes invalid

Cooldown:

**45 seconds**

Suggested statistics:

* Money stolen
* Pickpocket triggers
* All In activations
* Hotbar locks
* Players affected
* Kills

Visual identity:

* Casino/luck style
* Distinctive activation sound
* Coin/magic-style particles
* Clear slot-lock feedback
* Strong but clean All In activation effect

---

# 5. 🌪️ WIND TOTEM

### Passive — Windborne

Permanent:

* Speed I
* Reduced fall damage

### Active — Updraft

Create a large wind explosion centered around the owner.

Default:

* Radius: approximately 10–12 blocks
* Horizontal launch: approximately 15–20 blocks
* Vertical launch: approximately 8–12 blocks

The owner is unaffected.

The ability:

* Does not deal direct damage.
* Does not destroy blocks.
* Does not grief terrain.

Respect protection systems where possible.

Cooldown:

**40 seconds**

Suggested statistics:

* Updraft activations
* Players affected
* Players launched

Visual identity:

* Expanding wind ring
* Strong gust particles
* Large burst
* Wind sound
* Impact feedback on affected players

Make it look powerful without creating huge particle lag.

---

# 6. 🐙 OCTOPUS TOTEM

### Passive — Ink

When the owner is hit:

* Chance to create a small temporary blindness cloud.

Use an internal cooldown.

Do not allow rapid repeated triggering from fast attacks.

All relevant values should be configurable.

### Active — Ink Cloud

Create an **8-block-radius** cloud lasting:

**6 seconds**

Players inside receive impaired vision.

The owner gets enhanced visibility inside their own cloud.

The cloud:

* Does not destroy blocks.
* Does not permanently modify terrain.
* Must clean itself up.
* Should not constantly reapply effects unnecessarily.

Cooldown:

**40 seconds**

Suggested statistics:

* Passive triggers
* Cloud activations
* Players affected

Visual identity:

* Dark ink particles
* Cloud/fog effect
* Distinctive sound
* Clear cloud boundary
* Owner visibility should remain readable

---

# 7. 🐝 BEE TOTEM

### Passive — Bee Defense

Whenever the owner is hit:

* Chance to spawn one bee.
* Bee targets the attacker.

Use internal spawn limits.

Prevent players from generating unlimited bees.

### Active — Bee Swarm

Summon temporary bees.

Duration:

Approximately **25 seconds**

Bees attack players who have attacked the owner.

Implement:

* Per-player limits
* Optional global safety limit
* Ownership tracking
* Correct targeting
* Cleanup

Temporary bees must not become permanent pets.

Cooldown:

**50 seconds**

Suggested statistics:

* Bees spawned
* Swarm activations
* Players attacked
* Kills

Visual identity:

* Swarm effects
* Bee/buzzing sounds
* Small activation burst
* Clear swarm activation feedback

---

# 8. 🐺 WOLF TOTEM

### Passive — Pack Instinct

When owner is hit:

* Chance to spawn one temporary wolf.
* Wolf targets the attacker.

Temporary wolf:

* Strength II
* Speed II
* Increased health
* Approximately 25-second lifetime
* Custom/armored appearance where technically possible

### Active — Call of the Pack

Summon:

**11–20 wolves**

Maximum:

**20 wolves per activation**

Wolves:

* Strength II
* Speed II
* Increased health
* Target players who attack the owner
* Last approximately 25 seconds

This system MUST have strong performance protection.

Implement:

* Per-player wolf cap
* Global safety cap where appropriate
* Ownership tracking
* Duration tracking
* Cleanup
* Disconnect cleanup
* Death cleanup
* Reload cleanup
* Invalid entity cleanup
* Duplicate-spawn prevention

Do not allow Wolf Totem to create server lag.

Cooldown:

**70 seconds**

Suggested statistics:

* Wolves summoned
* Pack activations
* Players attacked
* Kills

Visual identity:

* Wolf spawn burst
* Pack-themed particles
* Howl when summoned
* Distinctive activation sound

---

# 9. 🧿 HEX / CURSE TOTEM

### Passive — Hex

Every **4th valid melee hit** applies one random minor curse for approximately **3 seconds**.

Possible curses:

* Slowness
* Weakness
* Mining Fatigue
* Nausea

Use an internal per-target cooldown.

Only valid melee hits count.

### Active — Bad Luck

Duration:

**6 seconds**

When an enemy attempts to activate their **custom WTotem ability**, there is a:

**30% chance**

that the activation is disrupted.

If disrupted:

* Ability fails.
* Ability cooldown is consumed.
* Target receives clear feedback.
* Hex owner receives feedback.

IMPORTANT:

Bad Luck ONLY affects custom WTotem active abilities.

It must NOT interfere with:

* Vanilla Totem of Undying
* Normal item use
* Commands
* Other plugins
* Unrelated Minecraft mechanics

Cooldown:

**55 seconds**

Suggested statistics:

* Hex triggers
* Bad Luck activations
* Abilities disrupted

Visual identity:

* Dark curse particles
* Eye/rune style effects
* Distinctive curse sound
* Strong visual when ability is disrupted

---

# 10. 👁️ HUNTER TOTEM

### Passive — Marked

The first player hit becomes:

**Hunted**

Duration:

**20 seconds**

While Hunted:

* Owner can see target's approximate location.
* Owner can see approximate distance.
* Tracking can work through walls.
* Tracking range approximately 25 blocks.

Do not reveal exact coordinates unless specifically configured.

Handle target:

* Death
* Disconnect
* World change
* Teleport
* Expiration

correctly.

Do not leave permanent marks.

### Active — Executioner

Duration:

**4 seconds**

Attacks against the hunted target apply stacking:

**1-second Slowness**

If target gets more than:

**20 blocks**

away:

* Effect ends.

Cooldown:

**45 seconds**

Suggested statistics:

* Players marked
* Hunted targets caught
* Executioner activations
* Hunted kills

Visual identity:

* Eye/tracking particles
* Target-mark effect
* Clear Hunted indicator
* Tracking feedback
* Distinctive Executioner activation

---

# COOLDOWNS

Default cooldowns:

```text
Speed     27s
Strength  30s
Wind      40s
Octopus   40s
Gambler   45s
Hunter    45s
Bee       50s
Hex       55s
Guard     65s
Wolf      70s
```

Minimum default active cooldown:

**27 seconds**

Maximum default active cooldown:

**70 seconds**

All cooldowns must be configurable.

---

# ACTIVE ABILITY ACTIVATION

Recommended default:

**Right-click while holding the WTotem.**

The system should:

1. Verify the item is a real WTotem.
2. Verify the player owns/equips it.
3. Verify the WTotem is enabled.
4. Verify the world allows WTotems.
5. Verify ability is not on cooldown.
6. Verify ability is not already active where applicable.
7. Activate ability.
8. Start cooldown.
9. Play visual/audio feedback.
10. Update statistics.

Invalid activation attempts should not consume cooldown.

Give useful feedback when activation fails.

---

# COOLDOWN UX

Players should always understand their ability state.

Show:

* Ready
* Active
* Cooldown
* Remaining cooldown

Use:

* Action bar
* GUI
* Sound
* Chat only when appropriate

Do not spam chat every second.

Example:

```text
⚡ WTotems » Dash ready!
```

or:

```text
⚡ WTotems » Dash is on cooldown for 12.4s.
```

---

# STATISTICS

There is NO:

* XP
* Leveling
* Mastery
* Skill tree
* RPG progression

Instead, every WTotem has its own statistics.

Example:

```text
🔥 Strength Totem

Kills: 47
Berserk Activations: 91
Hits During Berserk: 412
Damage Dealt: 128,421
```

Wolf example:

```text
🐺 Wolf Totem

Kills: 23
Pack Summons: 18
Wolves Summoned: 247
Players Attacked: 86
```

Stats must be:

* Per-player
* Per-WTotem
* Persistent
* Efficiently saved
* Viewable in GUI
* Viewable through `/wtotems stats`

Do not write to disk/database after every individual hit.

Use caching/batching where appropriate.

---

# GUI

`/wtotems` opens the main WTotems GUI.

It should feel like a polished server GUI.

Show all 10 WTotems.

Clicking a WTotem should show:

* Name
* Icon
* Passive
* Active
* Cooldown
* Description
* Recipe
* Statistics
* Equipped status

Improve the GUI with:

* Consistent layout
* Filler/border items
* Clean lore
* Totem-specific icons
* Cooldown indicators
* Equipped indicators
* Recipe presentation
* Stats presentation

Do not overcrowd it.

The GUI is for information/convenience.

Players should not need to keep it open to fight.

---

# COMMANDS

Player:

```text
/wtotems
/wtotems list
/wtotems info 
/wtotems recipe 
/wtotems stats
/wtotems cooldown
```

Admin:

```text
/wtotems give  
/wtotems reload
/wtotems toggle  
/wtotems resetcooldown  [totem]
/wtotems clear 
/wtotems debug 
/wtotems inspect 
```

`/wtotems inspect ` should show useful technical information including where relevant:

* Player
* Current WTotem
* Cooldown
* Active ability
* Temporary entities
* Internal ability state
* Relevant target
* Other useful debugging information

---

# PERMISSIONS

Implement:

```text
wtotems.use
wtotems.admin
wtotems.give
wtotems.reload
wtotems.toggle
wtotems.resetcooldown
wtotems.clear
wtotems.debug
wtotems.inspect
```

---

# RECIPES

All WTotems use normal crafting tables.

Use simple configurable 3x3 recipe syntax.

Example:

```yaml
strength:
  recipe:
    - [GOLD_INGOT:2, AIR, BLAZE_ROD]
    - [GOLD_INGOT, NETHERITE_SCRAP, GOLD_INGOT]
    - [AIR, GOLD_INGOT:2, AIR]
```

Rules:

`AIR` = empty

`ITEM` = quantity 1

`ITEM:2` = quantity 2

Example:

```yaml
speed:
  recipe:
    - [DIAMOND, FEATHER, DIAMOND]
    - [FEATHER, NETHER_STAR, FEATHER]
    - [DIAMOND, FEATHER, DIAMOND]
```

Recipe materials and quantities must be configurable.

Changing recipes must work through:

```text
/wtotems reload
```

No restart required.

---

# CONFIGURATION

Recommended files:

```text
config.yml
recipes.yml
messages.yml
effects.yml
stats.yml
```

Keep configuration clean and readable.

Balance-related values should be configurable, including:

* Cooldowns
* Durations
* Chances
* Ranges
* Damage
* Knockback
* Potion effects
* Entity limits
* Particle types
* Particle amounts
* Particle spread
* Sounds
* Sound volume
* Sound pitch
* Economy values
* Pickpocket chance
* Pickpocket cooldown
* All In lock chance
* All In lock duration
* Hex settings
* Hunter range
* World settings
* Messages
* GUI settings where appropriate

Do not expose pointless technical settings just for the sake of having more configuration.

---

# EFFECT CONFIGURATION

Create configurable effect presets.

Example:

```yaml
effects:
  strength:
    particles: FLAME
    sound: ENTITY_PLAYER_ATTACK_STRONG
    volume: 1.0
    pitch: 1.0

  speed:
    particles: ELECTRIC_SPARK
    sound: ENTITY_ENDER_DRAGON_FLAP
    volume: 1.0
    pitch: 1.2
```

Allow different effects for:

* Activation
* Passive trigger
* Impact
* Completion
* Failure
* Cooldown ready

where appropriate.

---

# WORLD SETTINGS

Allow WTotems to be enabled/disabled per world.

Example:

```yaml
worlds:
  world: true
  world_nether: true
  world_the_end: false
```

If disabled:

* Abilities cannot activate.
* Do not delete the player's WTotem.
* Handle the player's state safely.

---

# COMBAT SWITCHING

Configuration:

```yaml
combat:
  prevent_totem_switching: true
```

When enabled:

Prevent players from abusing combat inventory mechanics to rapidly switch WTotems.

Do not interfere with normal vanilla Totem of Undying behavior.

---

# CHAT & MESSAGES

Messages should be colorful, short and polished.

Examples:

```text
🔥 WTotems » Strength Totem equipped.
⚡ WTotems » Dash activated!
🐺 WTotems » The Pack has been summoned!
🧿 WTotems » HEXED! Your active ability has been disrupted.
```

All messages configurable.

Use appropriate:

* Colors
* Hex colors where supported
* Placeholders
* Action bar
* Titles
* Sounds

Do not spam players.

---

# CUSTOM DEATH MESSAGES

If a WTotem directly contributes to a kill, use a custom WTotem death message.

Examples:

```text
🔥 Steve was slain by Alex using the Strength Totem.
⚡ Steve couldn't escape Alex's Speed Totem.
🐺 Steve was overwhelmed by Alex's Pack.
🧿 Steve was HEXED by Alex.
👁️ Steve was hunted down by Alex.
🌪️ Steve was blown away by Alex's Wind Totem.
🐙 Steve disappeared into Alex's Ink Cloud.
```

If WTotems were not involved:

**Keep the normal Minecraft death message.**

Death messages must be configurable.

---

# PREMIUM VISUAL / AUDIO IDENTITY

This is extremely important.

Do NOT implement abilities as bare mechanics with a random particle and one generic sound.

Each Totem should feel like its own item.

Use combinations of:

* Particles
* Sounds
* Activation bursts
* Trails
* Impact effects
* Action bars
* Titles
* Target indicators
* Cooldown feedback
* Small animations
* Screen-readable effects where possible

Examples:

Strength should feel powerful.

Speed should feel fast.

Guard should feel defensive.

Gambler should feel lucky/risky.

Wind should feel explosive and airy.

Octopus should feel dark and ink-based.

Bee should feel chaotic and swarming.

Wolf should feel like a pack arriving.

Hex should feel cursed.

Hunter should feel like the player is being tracked.

Do not overdo the effects.

**Readable PvP combat is more important than particle spam.**

---

# PARTICLE QUALITY

Particles must be:

* Configurable
* Lightweight
* Intentional
* Totem-specific

Avoid massive particle loops.

Prefer:

* Short bursts
* Rings
* Trails
* Impact bursts
* Small ongoing effects only when necessary

Do not create hundreds/thousands of particles every tick.

---

# SOUND QUALITY

Every important ability should have appropriate sound feedback.

Configure:

* Sound
* Volume
* Pitch

Use different sounds for:

* Activation
* Success
* Impact
* Failure
* Special passive triggers

Do not play loud/repetitive sounds on every ordinary attack.

---

# EDGE CASES

Every ability must correctly handle:

* Player death
* Target death
* Player disconnect
* Target disconnect
* Teleport
* World change
* Server restart
* Plugin reload
* Unloaded chunks
* Invalid entities
* Missing targets
* Protected areas
* WTotem removal
* WTotem switching
* Ability expiration
* Repeated activation
* Already-active ability

Never leave behind:

* Permanent potion effects
* Ghost entities
* Stuck cooldowns
* Stuck hotbar locks
* Permanent tracking
* Orphaned scheduled tasks
* Broken inventory states

---

# BEE / WOLF ENTITY SYSTEM

Every temporary Bee/Wolf should be tracked as a WTotem-owned entity.

Store enough information to determine:

* Owner
* Spawn time
* Expiration time
* Target
* Totem type

Clean entities up when appropriate.

Prevent:

* Infinite spawning
* Entity duplication
* Permanent pets
* Ownerless entities
* Reload leftovers
* Disconnect leftovers

---

# PERFORMANCE

The plugin must be suitable for a busy PvP server.

Avoid:

* Full server scans every tick
* Full inventory scans every tick
* Excessive entity searches
* Excessive particles
* Excessive potion reapplication
* Database writes on every hit
* Large unnecessary repeating tasks

Use:

* Event-driven logic
* Efficient cooldown maps
* Scheduled cleanup
* Cached player state
* Batched stat saving

The system should support many players using different WTotems simultaneously without unnecessary server load.

---

# ANTI-EXPLOIT AUDIT

The final implementation must be tested against:

* Shift-click crafting
* Inventory dragging
* Double-click item movement
* Chests
* Barrels
* Shulkers
* Ender chests
* Hoppers
* Death
* Disconnect/reconnect
* Server restart
* `/give`
* Plugin-generated items
* Dropping/picking up
* Trading
* Cooldown manipulation
* Combat swapping
* Duplicate crafting results
* Fake WTotem items

The one-WTotem rule must remain reliable.

Vanilla Totems of Undying must remain completely unaffected.

---

# PROTECTION COMPATIBILITY

WTotems must not:

* Destroy terrain
* Grief blocks
* Bypass protected regions unnecessarily
* Intentionally bypass claims

Respect server/world protection systems where practical.

Abilities such as Wind/Updraft should not destroy blocks.

---

# RELOAD

Implement:

```text
/wtotems reload
```

Reload should safely update:

* Config
* Recipes
* Messages
* Effects
* Cooldowns
* World settings
* Totem toggles

Do not wipe:

* Player statistics
* Existing valid WTotems
* Player state unnecessarily

Do not leave old scheduled tasks/entities running after reload.

---

# DEBUGGING

`/wtotems debug ` should help staff diagnose problems.

Depending on Totem, display useful information such as:

```text
Player: Steve
WTotem: Strength
Cooldown: 14.2s
Active Ability: Berserk
Berserk Hits Remaining: 3
World: world
```

`/wtotems inspect ` should provide a broader overview of the player's WTotem state.

---

# CODE QUALITY

Write the plugin as production-quality code.

Prioritize:

* Clean architecture
* Modular Totem implementations
* Reusable ability/cooldown systems
* Reusable effect utilities
* Safe event handling
* Proper cleanup
* Clear naming
* Minimal duplicated logic
* Maintainability
* Performance

Do not create one giant class containing the entire plugin.

The 10 WTotems should be modular enough that future balancing/configuration is easy.

Do not over-engineer the plugin with unnecessary frameworks or complicated abstractions.

---

# FINAL QA PASS

Before considering the plugin finished, perform a complete review.

Verify:

* All 10 WTotems work.
* Every passive works.
* Every active works.
* Cooldowns work.
* One-WTotem restriction works.
* Vanilla Totems remain unaffected.
* Recipes work.
* Config reload works.
* Stats work.
* GUI works.
* Commands work.
* Permissions work.
* Death messages work.
* Particles work.
* Sounds work.
* Temporary entities clean up.
* Economy integration fails gracefully if unavailable.
* No obvious duplication exploits exist.
* No major performance problems exist.
* No permanent effects remain after disconnect/death/reload.
* Protected areas are respected where applicable.

Then perform a **second polish pass**.

Look specifically for anything that feels:

* Cheap
* Generic
* Clunky
* Confusing
* Visually unfinished
* Overly spammy
* Unnecessarily complicated
* Poorly optimized

Fix those issues.

Do not simply report them.

**Actually improve them.**

---

# MOST IMPORTANT DESIGN STANDARD

Do not stop when the mechanics technically function.

The target is:

**"This feels like a premium PvP plugin."**

Not:

**"This technically contains 10 abilities."**

The plugin should feel polished from the moment a player:

1. Crafts a WTotem.
2. Holds it in their inventory.
3. Equips it.
4. Opens `/wtotems`.
5. Reads its abilities.
6. Activates it for the first time.
7. Sees the particles.
8. Hears the sound.
9. Gets the cooldown feedback.
10. Uses it during PvP.
11. Views their statistics.
12. Encounters another player using a different WTotem.

Every part of that experience should feel intentional.

At the same time, **do not add unnecessary gameplay mechanics**.

The existing design is the gameplay.

Your job is to make that design **exceptionally well implemented**.

Final V1 WTotems:

🔥 Strength
⚡ Speed
🛡️ Guard
🎰 Gambler
🌪️ Wind
🐙 Octopus
🐝 Bee
🐺 Wolf
🧿 Hex
👁️ Hunter
Kodari AI
KodariSep 25 at 1:14 am 6
  1. Set up the Paper plugin, its configurable items/recipes, and persistent per-player statistics.

  2. Implement the ten abilities, cooldowns, cleanup, and one-WTotem inventory protections.

  3. Add /wtotems, the information/stats GUI, permissions, and reload support.

Created the WTotems Paper plugin with exactly 10 custom PDC-identified totems. It includes configurable recipes, active abilities and cooldowns, persistent per-player stats, a browsing GUI, player/admin commands, optional Vault economy support, and inventory protections against duplicate custom totems.

5k4g
📎 1 file 16,169 chars
📄
pasted-code-1790299058494.txt
txt 949 lines
▶
# WTotems — Visual & Presentation Overhaul

Take the existing WTotems plugin and give it a complete **visual, audio, UI and presentation overhaul**.

Do NOT change the core gameplay mechanics, cooldowns, balancing, recipes, stats or ability behavior unless a tiny implementation change is necessary to improve presentation.

The purpose of this pass is to make WTotems look and feel like a **premium, professionally designed Minecraft PvP plugin**.

Do not settle for basic particles + random sounds.

Every Totem should have a recognizable visual language.

---

# 1. OVERALL VISUAL DIRECTION

WTotems should have a consistent visual identity across:

* Items
* GUI
* Particles
* Sounds
* Action bars
* Titles
* Chat
* Ability activation
* Ability impact
* Cooldowns
* Statistics
* Death messages

Everything should feel like it belongs to the same plugin.

Use the Totem's emoji/icon and theme consistently.

The player should be able to recognize which WTotem is being used **without reading a giant message**.

Visuals should be:

* Clean
* Smooth
* Satisfying
* PvP-readable
* Distinctive
* Lightweight
* Configurable

Avoid ugly particle spam.

---

# 2. TOTEM IDENTITY SYSTEM

Give every WTotem its own visual identity.

### 🔥 Strength

Theme:
**Power / Rage / Fire**

Visual language:

* Flames
* Red/orange-style effects where supported
* Sharp impact bursts
* Short aggressive trails
* Heavy attack sounds
* Strong activation pulse

Berserk activation should feel like the player has entered a temporary combat state.

Each Berserk hit should have a small, satisfying impact effect without flooding the screen.

---

### ⚡ Speed

Theme:
**Lightning / Velocity / Movement**

Visual language:

* Electric particles
* Fast streaks
* Small lightning-style bursts
* Speed trails
* Quick sharp sounds

Dash should have:

1. Small charge-up cue
2. Instant movement burst
3. Short trail
4. Landing/arrival effect

The effect should communicate speed rather than simply spawning particles at the player.

---

### 🛡️ Guard

Theme:
**Defense / Protection / Fortress**

Visual language:

* Shield/protection particles
* Circular defensive ring
* Heavy activation sound
* Short protective pulse

When Iron Will activates:

* Create a strong activation burst.
* Show a subtle defensive aura while active.
* Give clear feedback when it ends.

The player should immediately understand:

**"I'm protected right now."**

---

### 🎰 Gambler

Theme:
**Luck / Casino / Risk**

Visual language:

* Coin-like effects
* Lucky/chance visuals
* Sparkles
* Distinctive casino-style sounds

Pickpocket:

* Small success effect around the attacker.
* Coin-style sound.
* Clear money feedback.

All In:

* More dramatic activation.
* Brief "jackpot" style effect.
* Clear indication when a hotbar slot becomes locked.
* Do not make the UI confusing.

Gambler should feel completely different from Strength/Speed/etc.

---

### 🌪️ Wind

Theme:
**Air / Force / Explosion**

Visual language:

* Circular wind rings
* Expanding gust
* Spiral effects
* Strong wind sound

Updraft should have a noticeable buildup and then a large burst.

Suggested sequence:

**Charge → Wind ring → Explosion → Player launch**

Do not use a giant amount of particles every tick.

---

### 🐙 Octopus

Theme:
**Ink / Darkness / Ocean**

Visual language:

* Dark ink cloud
* Mist
* Bubble-like accents where appropriate
* Smooth cloud expansion
* Underwater-style audio

Ink Cloud should visually expand outward rather than simply appearing instantly.

Make the owner visually readable inside their own cloud.

---

### 🐝 Bee

Theme:
**Swarm / Nature / Chaos**

Visual language:

* Small swarm particles
* Buzzing sounds
* Honey/flower-style accents where appropriate
* Tiny activation bursts

Bee Swarm activation should feel like:

**"Oh shit, there's a swarm coming."**

Keep it readable and don't create enormous particle spam around every bee.

---

### 🐺 Wolf

Theme:
**Pack / Hunt / Wild**

Visual language:

* Pack-style spawn burst
* Subtle aura around summoned wolves
* Wolf howl when the pack appears
* Strong group activation effect

When Call of the Pack activates, make the wolves feel like they are **arriving as a coordinated pack**, not just appearing randomly.

If technically possible, synchronize a short howl/visual burst across spawned wolves.

---

### 🧿 Hex

Theme:
**Curse / Magic / Forbidden Power**

Visual language:

* Dark magical particles
* Rings
* Floating glyph/rune-style effects where possible
* Distinctive curse sound
* Sharp effect when an ability is disrupted

When Hex triggers:

**small curse effect → target reaction**

When Bad Luck blocks an ability:

**stronger disruption effect → clear feedback**

The effect should immediately communicate:

**"Something just went wrong because of Hex."**

---

### 👁️ Hunter

Theme:
**Tracking / Target / Predator**

Visual language:

* Eye-style particles
* Target marker
* Tracking trail
* Subtle directional indicators

When someone becomes Hunted:

* Show a clear marking effect.
* Give the Hunter owner a short confirmation.
* Give the target an appropriate indication that they have been marked, if configured.

Executioner should have a much stronger activation effect.

The Hunter should feel like a **predator locking onto a target**.

---

# 3. ABILITY ACTIVATION ANIMATIONS

Every active ability should have a short visual activation sequence where appropriate.

Do NOT make every ability instantly appear with no feedback.

Use short sequences such as:

### Activation

```text
Small preparation effect
        ↓
Sound
        ↓
Main visual burst
        ↓
Ability begins
```

Keep these sequences short enough that they don't interrupt PvP.

Do not add long cinematic animations that make players wait.

---

# 4. PARTICLE DESIGN

Do not randomly spam one particle type.

Build intentional particle patterns.

Examples:

### Rings

Use for:

* Guard
* Wind
* Hex
* Octopus

### Bursts

Use for:

* Strength
* Bee
* Wolf
* Ability impacts

### Trails

Use for:

* Speed
* Hunter
* Wind

### Auras

Use for:

* Guard
* Berserk
* Active states

### Target markers

Use for:

* Hunter
* Hex

Particle amounts, radius, duration, spread and types should be configurable.

---

# 5. PARTICLE PERFORMANCE

This is extremely important.

Visual quality must NOT come at the cost of server performance.

Avoid:

* Hundreds/thousands of particles per tick
* Large particle spheres every tick
* Repeated full-area particle scans
* Unnecessary particle entities
* Permanent particle loops

Use lightweight scheduled effects.

Prefer short bursts over enormous continuous effects.

The visual system should remain performant with many players fighting simultaneously.

---

# 6. SOUND DESIGN

Give every Totem its own sound identity.

Use separate sounds where appropriate for:

* Equip
* Activation
* Passive trigger
* Impact
* Success
* Failure
* Cooldown ready
* Ability ending

Sounds should complement the visuals.

Avoid using the same sound for every ability.

Allow configuration of:

```yaml
sound:
  type: ENTITY_...
  volume: 1.0
  pitch: 1.0
```

Do not make sounds painfully loud.

Avoid repetitive sound spam.

---

# 7. ACTION BAR SYSTEM

Create a polished action-bar feedback system.

Examples:

```text
🔥 BERSERK ACTIVE   ⚔ 3 HITS
```

```text
⚡ DASH READY
```

```text
⚡ DASH — 12.4s
```

```text
🧿 BAD LUCK ACTIVE
```

```text
👁️ HUNTED — 18m
```

Action bars should update intelligently.

Do not send a new message every tick if nothing changed.

---

# 8. TITLE / SUBTITLE EFFECTS

Use titles sparingly for major moments.

Good examples:

### Wolf

```text
🐺
THE PACK
```

### Guard

```text
🛡️
IRON WILL
```

### Wind

```text
🌪️
UPDRAFT
```

### Hex

```text
🧿
HEXED
```

Titles should be short.

Do not use titles for every passive trigger.

Avoid covering the player's screen constantly.

---

# 9. COOLDOWN FEEDBACK

Make cooldowns visually satisfying.

When an ability becomes ready:

* Small sound
* Optional particle burst
* Action bar notification

Example:

```text
⚡ WTotems » DASH READY
```

Do not repeatedly announce it.

When an ability is on cooldown, give the remaining time through action bar or a concise message.

---

# 10. EQUIP EXPERIENCE

Equipping a WTotem should feel special.

When a player equips a WTotem:

* Small visual effect
* Short sound
* Action bar/chat message
* Optional title for first-time equip

Example:

```text
🔥 WTotems
STRENGTH TOTEM EQUIPPED
```

Do not play the full effect every time the item moves between inventory slots.

Only trigger when the actual equipped WTotem state changes.

---

# 11. GUI VISUAL OVERHAUL

Make `/wtotems` look like a professionally designed server menu.

Use:

* Consistent spacing
* Clean borders
* WTotem-specific icons
* Status indicators
* Cooldown indicators
* Stats formatting
* Recipe presentation
* Decorative elements

Example item lore structure:

```text
🔥 Strength Totem

PASSIVE
Strength II

ACTIVE
Berserk

COOLDOWN
30 seconds

Your Stats
Kills: 47
Berserks: 91
```

Use visual hierarchy.

Important information should be easy to find.

Do not make every line the same style.

---

# 12. TOTEM SELECTION SCREEN

When a player clicks a Totem:

Show:

* Large Totem icon
* Name
* Passive
* Active
* Cooldown
* Description
* Recipe
* Personal statistics
* Equipped state

Add a clear indication of the player's current WTotem.

Example:

```text
✔ CURRENTLY EQUIPPED
```

or an equivalent visual indicator.

---

# 13. RECIPE GUI

Make recipe viewing visually clean.

Show the actual 3×3 recipe layout.

Display:

* Item icons
* Quantities
* Result
* Totem name

Do not just dump the YAML recipe into chat.

---

# 14. STATISTICS UI

Statistics should feel like part of the plugin rather than debug information.

Use clean formatting.

Example:

```text
🔥 STRENGTH TOTEM

Combat
Kills .............. 47
Damage ............. 128,421

Abilities
Berserk Activations 91
Berserk Hits ....... 412
```

Use consistent formatting across all 10 Totems.

---

# 15. CHAT VISUAL IDENTITY

Create a consistent WTotems message format.

Examples:

```text
🔥 WTotems » Berserk activated!
⚡ WTotems » Dash activated!
🐺 WTotems » The Pack has arrived!
🎰 WTotems » You stole $4,250!
🧿 WTotems » HEXED!
👁️ WTotems » Target marked.
```

Make the Totem icon part of the identity.

Keep messages short.

Avoid giant paragraphs in chat.

---

# 16. COMBAT READABILITY

This is one of the highest priorities.

Effects must look impressive without making PvP unreadable.

Never let:

* Wolf particles
* Bee particles
* Wind effects
* Ink
* Hex effects

completely obscure the combat area.

Use controlled particle density.

Important gameplay information must remain visible.

---

# 17. TARGET FEEDBACK

When an ability affects another player, make the affected player understand what happened.

Examples:

### Hex

```text
🧿 Your ability was HEXED!
```

### Hunter

```text
👁️ You are HUNTED.
```

### Gambler

```text
🎰 $4,250 was pickpocketed!
```

### Wind

Give strong visual/audio knockback feedback.

### Octopus

Make the cloud visually obvious.

Feedback should be configurable where appropriate.

---

# 18. DEATH MESSAGE PRESENTATION

Keep WTotem death messages stylish.

Use the Totem identity.

Examples:

```text
🔥 Steve was slain by Alex using the Strength Totem.
🐺 Steve was overwhelmed by Alex's Pack.
🌪️ Steve was blown away by Alex's Wind Totem.
🧿 Steve was HEXED by Alex.
👁️ Steve was hunted down by Alex.
```

Normal Minecraft death messages remain unchanged when WTotems were not involved.

---

# 19. CUSTOM MODEL / RESOURCE PACK SUPPORT

Design the item system so that custom models can be added later without rewriting the plugin.

Support:

* Custom Model Data
* Unique item IDs
* Configurable item material
* Configurable model data

Do not require a resource pack for the plugin to function.

The default experience should still look good without one.

---

# 20. VISUAL CONFIGURATION

Make visual effects configurable.

For each Totem where appropriate, support configuration for:

```yaml
particles:
  type: FLAME
  amount: 20
  radius: 2.0
  duration: 10
  spread: 0.5

sound:
  type: ENTITY_PLAYER_ATTACK_STRONG
  volume: 1.0
  pitch: 1.0
```

Do not force server owners to edit Java code to change visual effects.

---

# 21. VISUAL STATE CLEANUP

Every temporary visual effect must have proper cleanup.

No:

* Permanent particles
* Permanent potion effects
* Ghost effects
* Stuck action bars
* Stuck titles
* Stuck tracking indicators
* Stuck target markers
* Stuck hotbar-lock indicators

Handle cleanup on:

* Ability end
* Death
* Disconnect
* World change
* Teleport
* WTotem change
* Plugin reload
* Server shutdown

---

# 22. VISUAL PERFORMANCE

Test the plugin with multiple players using WTotems simultaneously.

The visual system should scale reasonably.

Do not create:

* One giant repeating task per player
* One particle task per entity
* Excessive per-tick calculations

Where possible, centralize scheduled visual updates and use efficient tracking.

---

# 23. POLISH THE SMALL DETAILS

Look for small moments that make the plugin feel expensive.

Examples:

* Tiny burst when a cooldown becomes ready.
* Slight impact effect on Berserk hits.
* Small coin effect when Pickpocket succeeds.
* Wind ring expanding before Updraft.
* Pack howl synchronized with Wolf activation.
* Curse burst when Hex activates.
* Target marker appearing smoothly for Hunter.
* Small defensive pulse when Guard activates.
* Bee swarm having a recognizable arrival effect.
* Ink cloud expanding instead of instantly appearing.

These small details matter.

Do not turn them into large gameplay mechanics.

---

# 24. CONSISTENCY

Create a consistent design language across the entire plugin.

The same:

* Font/color formatting
* Message structure
* GUI hierarchy
* Cooldown presentation
* Statistic presentation
* Item lore style
* Action-bar style

should be used everywhere.

But each Totem should still feel visually unique.

The goal is:

**One WTotems identity + ten distinct Totem identities.**

---

# 25. FINAL VISUAL QA

After implementing the visual overhaul, test every Totem individually.

For each one check:

* Item appearance
* Lore
* Equip effect
* Passive effect
* Active activation
* Active duration
* Impact effect
* Sound
* Action bar
* Cooldown
* Cooldown-ready feedback
* GUI
* Statistics
* Death message
* Target feedback
* Cleanup

Then test several different WTotems fighting simultaneously.

Make sure the screen remains readable.

If something looks:

* Generic
* Empty
* Cheap
* Spammy
* Confusing
* Repetitive
* Visually disconnected
* Unnecessarily loud

improve it.

Do not simply report the issue.

**Actually fix it.**

---

# FINAL STANDARD

Do not think:

> "What is the minimum number of particles I need to make this work?"

Think:

> "If a player sees this ability for the first time, does it look like a professionally made custom PvP plugin?"

The goal is:

**WTotems should look memorable before the player even understands the mechanics.**

Keep gameplay unchanged.

Keep performance strong.

Keep PvP readable.

But make the presentation feel **premium, intentional, satisfying and unique.**
Kodari AI
KodariSep 25 at 1:24 am 3
  1. Map the plugin’s totem, ability, item, and GUI presentation paths.

  2. Improve shared item, equip, message, and cooldown presentation without changing gameplay.

  3. Add lightweight, distinct visual/audio feedback to the ability triggers.

  4. Polish the totem menus, statistics, and recipes; verify cleanup and consistency.

Task 1 is mapped. I’m updating the shared presentation layer next: clearer item lore, identity-branded cooldown/activation feedback, and equip cues only when the selected held totem actually changes.

Implemented the WTotems presentation overhaul across shared feedback, abilities, and menus:

  • Refined item lore; added totem-branded activation and cooldown action bars, ready sounds, and equip cues when the selected totem changes.

  • Added restrained, distinct effects for Berserk hits, Dash, Guard, Updraft, Ink Cloud, Bee/Wolf arrivals, Pickpocket, Hex, and Hunter marks. Particle amount, spread, and ring radius scale are configurable.

  • Reworked the recipe menu to show the 3×3 ingredients and result; made equipped status player-specific and organized stats into combat and ability sections.

  • Kept ability mechanics, cooldowns, and balancing unchanged.

I haven’t run live Minecraft visual or multiplayer performance QA, so those still need in-game verification.

5k4g
📎 1 file 17,205 chars
📄
pasted-code-1790302882943.txt
txt 954 lines
▶
# WTotems — Implementation Correction & Premium Polish Pass

The current implementation is functional, but it is NOT matching the intended WTotems experience closely enough.

This is not a request to randomly redesign the plugin or add more gameplay mechanics.

This is a **correction + polish pass** to bring the implementation back in line with the original WTotems concept.

The biggest issue is that some implementation decisions technically work but completely miss the identity of the plugin.

WTotems should feel like a polished, custom Minecraft PvP system built around **Totems of Undying**.

Do not treat the custom WTotems as generic custom items.

---

# 1. CORE IDENTITY — EVERYTHING CUSTOM MUST BE A TOTEM

This is the most important correction.

## Every WTotem item must use:

```text
Material.TOTEM_OF_UNDYING
```

as its actual Minecraft item material.

Do NOT use:

* diamonds
* netherite
* paper
* sticks
* custom placeholder items
* generic icons
* another material with a Totem texture
* an arbitrary custom item that only LOOKS like a Totem

The actual base item must be the Minecraft **Totem of Undying**.

The plugin is called:

**WTotems**

because the custom items ARE Totems.

A player holding a WTotem should literally see the familiar Minecraft Totem of Undying item in their inventory, with the WTotem's custom identity coming from:

* custom name
* lore
* custom model data/resource-pack support if enabled
* particles
* sounds
* GUI
* effects
* ability behavior
* stats
* visual presentation

But the underlying item material is still:

```text
TOTEM_OF_UNDYING
```

---

# 2. VANILLA TOTEM VS WTOTEM

There are two completely separate concepts.

## Vanilla Totem of Undying

A normal Minecraft Totem of Undying must remain completely vanilla.

It must:

* work normally
* trigger its normal resurrection effect
* stack/behave according to vanilla rules
* NOT count as a WTotem
* NOT trigger WTotem mechanics
* NOT be blocked by the one-WTotem system
* NOT be modified by WTotem abilities

Players can have multiple normal vanilla Totems.

## WTotem

A WTotem is also:

```text
TOTEM_OF_UNDYING
```

but has a unique internal WTotem identity stored using a reliable method such as:

* PersistentDataContainer
* NamespacedKey
* internal WTotem ID

Example internal IDs:

```text
strength
speed
guard
gambler
wind
octopus
bee
wolf
hex
hunter
```

NEVER identify a WTotem using display name or lore alone.

---

# 3. WTOTEMS MUST BE DROPPABLE

This is another major correction.

A WTotem should behave like a normal Minecraft item.

Players MUST be able to:

* drop WTotems
* pick WTotems up
* move WTotems between inventory slots
* move them between hotbar slots
* move them into containers where appropriate
* trade them
* throw them on the ground
* retrieve them
* die and drop them according to normal item/drop rules

Do NOT make WTotems permanently bound to the player.

Do NOT cancel normal item dropping just because it is a WTotem.

Do NOT make the WTotem undroppable.

Do NOT force it into a specific slot unless explicitly configured.

---

# 4. ONE WTOTEM PER PLAYER — CORRECT INTERPRETATION

The rule is:

> A player may possess only ONE custom WTotem at a time.

It does NOT mean:

> The WTotem cannot be dropped.

Example:

Player has:

```text
🔥 Strength Totem
```

They drop it on the ground.

They no longer possess it.

Another player can pick it up.

The original player can then obtain another WTotem.

---

## If a player already possesses a WTotem

Example:

Player currently owns:

```text
🔥 Strength Totem
```

They somehow obtain:

```text
⚡ Speed Totem
```

The newly obtained Speed Totem is discarded.

The Strength Totem remains.

This applies to obtaining/creating additional WTotems through:

* crafting
* pickup
* commands
* containers
* trades
* plugin-generated items
* other supported acquisition methods

Do NOT delete the player's existing WTotem.

Do NOT replace the existing WTotem.

Discard the NEW duplicate WTotem.

---

# 5. IMPORTANT — TRACK POSSESSION CORRECTLY

The one-WTotem rule must scan/consider all relevant inventory locations.

At minimum:

* main inventory
* hotbar
* offhand
* armor slots if applicable
* cursor
* crafting output
* container interactions
* item pickups
* plugin-generated acquisition

Be extremely careful with:

* shift-clicking
* drag events
* crafting
* hopper/container movement
* death drops
* reconnecting
* inventory closing
* reloads

Do not create duplicate WTotems through inventory edge cases.

---

# 6. CRAFTING MUST PRODUCE AN ACTUAL TOTEM

Every recipe must output:

```text
TOTEM_OF_UNDYING
```

with the correct WTotem internal ID.

Example:

```text
🔥 Strength Totem
```

is literally a Minecraft Totem of Undying item with:

```text
Material = TOTEM_OF_UNDYING
PDC wtotems:id = strength
```

Do not output a different material.

---

# 7. THE XP-BAR HUD / STATS DISPLAY MUST ACTUALLY EXIST

The current implementation appears to have stats accessible through commands, but the intended experience includes a **visible WTotems HUD above the XP bar**.

Implement this properly.

The HUD should appear in the normal Minecraft area above the XP bar / action-bar region.

It should be clean, compact, and configurable.

Example:

```text
🔥 Strength Totem
Berserk: READY
Kills: 47
```

or during cooldown:

```text
🔥 Strength Totem
Berserk: 18s
Kills: 47
```

Do NOT constantly spam chat.

Do NOT replace the entire Minecraft UI with a giant scoreboard.

The HUD should feel like a polished PvP overlay.

---

# 8. HUD DESIGN

The HUD should dynamically show information relevant to the player's currently equipped WTotem.

Example:

```text
🔥 STRENGTH
Berserk: READY
Kills: 47
```

When activated:

```text
🔥 STRENGTH
BERSERK ACTIVE
Hits: 3/5
```

During cooldown:

```text
🔥 STRENGTH
Berserk: 21s
```

For Speed:

```text
⚡ SPEED
Dash: READY
Dashes: 32
```

For Wolf:

```text
🐺 WOLF
Pack: 42s
Wolves: 8
```

For Hunter:

```text
👁 HUNTER
Target: Steve
Distance: 18m
Executioner: READY
```

For Gambler:

```text
🎰 GAMBLER
All In: READY
Stolen: $84,000
```

For abilities with no meaningful target/state information, show the relevant cooldown + a useful stat.

---

# 9. HUD MUST BE CONFIGURABLE

Add configuration for the HUD.

For example:

```yaml
hud:
  enabled: true

  update_interval: 5

  show_totem_name: true
  show_ability: true
  show_cooldown: true
  show_stats: true

  format:
    ready: "&aREADY"
    cooldown: "&c{time}s"
    active: "&6ACTIVE"
```

Allow the exact displayed format to be configured.

Do not hardcode the HUD permanently.

Players/admins should be able to disable it if desired.

---

# 10. THE HUD MUST NOT BE A REAL SCOREBOARD OBJECTIVE UNLESS NECESSARY

Do not create an ugly sidebar scoreboard just to satisfy "stats display."

The intended visual is the compact PvP HUD near the XP bar.

Use the appropriate Bukkit/Paper API mechanism for the target Minecraft version.

The final result should look intentional, not like debug information.

---

# 11. WOLF TOTEM — THE WOLVES NEED ACTUAL ARMOR

This is another obvious implementation miss.

The Wolf Totem is specifically supposed to create visually special armored wolves.

The wolves currently appear to just be normal wolves with modified stats.

That is not enough.

The summoned wolves need to visibly wear armor.

Implement an actual armored appearance using the appropriate supported Minecraft/Paper mechanism for the server version.

The armor must be visible to players.

---

# 12. WOLF ARMOR

Make the armor configurable.

Example:

```yaml
wolf:
  armor:
    enabled: true

    material:
      helmet: IRON_HELMET
      chestplate: IRON_CHESTPLATE
      leggings: IRON_LEGGINGS
      boots: IRON_BOOTS
```

If the server/version supports more visually appropriate wolf armor mechanics, use them appropriately.

The key requirement is:

> Players must visibly see that these are special combat wolves.

They should not look like ordinary vanilla wolves.

---

# 13. WOLF VISUAL IDENTITY

The wolves should have a clear WTotem identity.

On spawn:

* spawn particles
* short summon sound
* wolves appear in a coordinated burst
* howl/summon audio
* subtle particle trail/aura where appropriate

During combat:

* wolves visibly attack their target
* target receives clear feedback
* wolves remain visually identifiable as temporary WTotem wolves

When the pack expires:

* short disappearance effect
* sound
* particles
* cleanup

Do NOT leave permanent wolves behind.

---

# 14. WOLF ENTITY DATA

Every WTotem wolf should have internal tracking data.

Track things such as:

```text
wtotems:wolf
wtotems:owner
wtotems:expires
wtotems:totem_type
```

Do not rely solely on the wolf's name.

This prevents conflicts with normal player wolves.

---

# 15. NORMAL PLAYER WOLVES MUST NEVER BE AFFECTED

This is extremely important.

If a player already owns normal Minecraft wolves, WTotems must NOT:

* modify their stats
* give them temporary armor
* remove their armor
* delete them
* make them target random players
* count them as WTotem wolves

Only plugin-created WTotem wolves should receive WTotem behavior.

---

# 16. WOLF CLEANUP

Temporary WTotem wolves must be removed when appropriate:

* duration expires
* owner dies if configured
* owner disconnects
* world changes if necessary
* plugin reload
* server shutdown
* entity becomes invalid

Do not leave ghost wolves.

Do not leave permanent entities.

Do not create entity buildup.

---

# 17. REVIEW ALL 10 TOTEMS FOR THE SAME PROBLEM

Do a full implementation audit.

Do not only fix the Wolf Totem.

For EVERY WTotem verify:

### Item

* Actual material = TOTEM_OF_UNDYING
* Correct internal WTotem ID
* Correct name
* Correct lore
* Correct appearance
* Droppable
* Pick-up-able
* One-WTotem enforcement works

### Passive

* Correctly activates
* Correct restrictions
* Correct cooldown/internal cooldown
* Correct cleanup

### Active

* Correct activation
* Correct cooldown
* Correct targeting
* Correct visual feedback
* Correct sound
* Correct particles
* Correct cleanup

### Stats

* Correct counters
* Persistent
* Efficient storage
* Displayed in `/wtotems stats`
* Relevant stats available through HUD

---

# 18. VISUAL QUALITY CHECK

The plugin should NOT feel like:

> "Someone coded ten abilities and attached them to items."

It should feel like:

> "This is an actual PvP plugin with a coherent visual identity."

Every Totem needs:

* unique activation effect
* unique particles
* unique sound profile
* unique HUD identity
* unique GUI identity
* unique target feedback where relevant
* polished cooldown feedback

Use the previously defined visual identities.

### Strength

Fire / rage / impact

### Speed

Lightning / velocity / movement

### Guard

Shield / fortress / protection

### Gambler

Casino / coins / luck / risk

### Wind

Air / shockwave / force

### Octopus

Ink / darkness / ocean

### Bee

Swarm / buzzing / honey / nature

### Wolf

Pack / hunt / wild / howling

### Hex

Curse / dark magic / glyphs

### Hunter

Tracking / predator / target lock

---

# 19. GUI MUST SHOW THE ACTUAL TOTEM

The `/wtotems` GUI should display the actual WTotem item representation.

Since every WTotem is based on:

```text
TOTEM_OF_UNDYING
```

the GUI should use the corresponding WTotem item with its custom name/lore/model.

Do not use unrelated materials as fake icons.

---

# 20. RECIPE GUI

When using:

```text
/wtotems recipe 
```

or clicking recipe information in the GUI, show the actual 3x3 crafting recipe.

Example:

```text
[ GOLD x2 ][ AIR ][ BLAZE ROD ]
[ GOLD    ][ NETHERITE SCRAP ][ GOLD ]
[ AIR ][ GOLD x2 ][ AIR ]
```

and show:

```text
Result:
🔥 Strength Totem
```

The result item must visibly be the WTotem.

---

# 21. ITEM LORE

Each WTotem should have polished lore.

Example structure:

```text
🔥 Strength Totem

§7A WTotem infused with raw power.

§6Passive
§fStrength II

§6Ability
§fBerserk
§7Your next 5 valid melee hits
§7deal Strength III-level damage.

§8Cooldown: 30s
```

Do not overload the lore.

Make it readable.

---

# 22. ITEM DROP / PICKUP FEEDBACK

When a WTotem is picked up, give a subtle message/effect if enabled.

Example:

```text
🔥 WTotems » Strength Totem acquired.
```

When a duplicate WTotem is rejected:

```text
§cWTotems » You already have a WTotem.
§7Your current Totem was kept.
```

The new item should be discarded.

Make these messages configurable.

---

# 23. DO NOT CONFUSE VANILLA TOTEMS WITH WTOTEMS

This must be tested heavily.

Test:

```text
Player has 5 vanilla Totems
+
1 Strength WTotem
```

This is valid.

Player can continue having:

```text
5 vanilla Totems
```

while also having:

```text
1 WTotem
```

If they obtain:

```text
Speed WTotem
```

while already holding:

```text
Strength WTotem
```

Speed is rejected.

Vanilla Totems are untouched.

---

# 24. DROPPING TEST

Explicitly test:

1. Player obtains Strength Totem.
2. Player presses Q.
3. Strength Totem drops.
4. Player can pick it back up.
5. Another player can pick it up.
6. Original player no longer possesses a WTotem after dropping it.
7. Original player can then obtain a different WTotem.
8. The dropped Totem remains a valid WTotem.
9. Its internal ID survives dropping/picking up.

This must work.

---

# 25. DEATH TEST

Test:

1. Player has a WTotem.
2. Player dies.
3. If normal drop rules allow it, the WTotem drops normally.
4. It remains a valid WTotem item.
5. Another player can pick it up.
6. The dead player does not somehow retain a hidden WTotem.
7. No duplicate is created.

Also verify vanilla Totem behavior separately.

---

# 26. RELOAD TEST

Run:

```text
/wtotems reload
```

while players have WTotems.

Nothing should break.

Verify:

* WTotem IDs remain valid
* cooldowns are handled correctly
* HUD continues working
* temporary wolves are cleaned/recovered correctly
* active effects do not become permanent
* no duplicate WTotems
* no ghost entities
* no stuck tasks
* no stuck hotbar locks
* configuration updates safely

---

# 27. "PREMIUM" DOES NOT MEAN MORE FEATURES

Do NOT respond to this request by adding:

* mastery
* levels
* XP
* extra currencies
* quests
* random progression
* unnecessary menus
* extra abilities
* filler mechanics

The existing 10 WTotems and their mechanics are already defined.

The goal is to make the implementation feel **finished**.

---

# 28. FINAL QUALITY BAR

Before considering the plugin finished, ask:

### Item identity

> "If I look at my inventory, does this obviously feel like a special Totem of Undying?"

### Gameplay

> "Do the abilities feel responsive and intentional?"

### HUD

> "Can I understand my Totem and cooldown without opening a menu?"

### Visuals

> "Can I immediately tell which WTotem is being used?"

### Wolves

> "Do these look like special WTotem combat wolves rather than normal wolves?"

### Polish

> "Does every interaction have appropriate feedback?"

### Reliability

> "Can I abuse inventory, death, reload, pickup, crafting, containers, or reconnects to duplicate/break WTotems?"

The final result should pass all of these.

---

# FINAL REQUIREMENT

Do not simply patch the individual bugs mentioned above.

Perform a complete implementation audit of the existing WTotems plugin against the intended specification.

Preserve the already-approved:

* 10 WTotems
* passive abilities
* active abilities
* cooldowns
* stats
* recipes
* one-WTotem rule
* commands
* permissions
* configuration system
* anti-exploit requirements

But correct any implementation that contradicts the intended WTotems identity.

The most important corrections are:

**1. Every WTotem is an actual `TOTEM_OF_UNDYING`.**

**2. WTotems are normal droppable/pickup-able items.**

**3. One-WTotem means one possessed custom Totem, NOT an undroppable item.**

**4. Vanilla Totems remain completely separate and vanilla.**

**5. The WTotem HUD/stats display above the XP bar must actually be implemented and polished.**

**6. Wolf Totem wolves must visibly wear armor and look like special temporary combat wolves.**

**7. The entire plugin needs a final premium polish pass rather than merely being mechanically functional.**

Do not stop at "it works."

Make it feel like **WTotems**.
Kodari AI
KodariSep 25 at 2:32 am 5
  1. Audit the WTotem item identity, acquisition/drop enforcement, recipes, and GUI.

  2. Review ability feedback, stats, and HUD; add the configurable XP-bar HUD.

  3. Audit wolf armor, identity, visuals, and lifecycle cleanup.

  4. Patch the verified issues while preserving the existing 10 totems and mechanics.

  1. Custom items now always use the Totem of Undying; dropping, pickup, cursor handling, container transfers, and duplicate rejection are corrected.

  2. I’m adding the configurable action-bar HUD and wiring it to the existing ability state and stats.

  3. Then I’ll audit and patch the wolf presentation and cleanup against the current entity APIs.

Implemented the main WTotems correction pass:

  • WTotem items now use only TOTEM_OF_UNDYING, and are identified by both their material and PDC ID. Drops and normal transfers into storage are allowed; duplicate pickups are discarded, while crafting, pickup, and inventory transfers reject a second WTotem. Vanilla Totems remain unaffected.

  • The existing GUI and crafting recipes use the corrected item factory, so their WTotem icons and results are actual Totems.

  • Added a configurable action-bar HUD with totem identity, ability readiness/cooldown, and relevant stats.

  • WTotem wolves now use visible WOLF_ARMOR, have PDC owner/type/expiry tags, and are cleaned up on expiry, owner death/disconnect, world changes, and shutdown. Normal wolves are not included in plugin tracking.

  • Fixed audit findings: Bee/Wolf summon stats were double-counted, Octopus affected-player stats were missing, and an unsuccessful Speed dash no longer consumes cooldown or increments its dash count.

The HUD and wolf armor settings are in config.yml; pickup and duplicate feedback remain configurable. Live server scenarios such as death drops, reconnects, and inventory edge cases still need runtime testing.

5k4g
📎 1 file 18,057 chars
📄
pasted-code-1790303634686.txt
txt 969 lines
▶
I WTotems — Final UI/UX, WorldGuard & Interaction Polish Pass
This is a new implementation pass for the existing WTotems plugin.

Do NOT rebuild the entire plugin from scratch.

Do NOT redesign the 10 WTotem mechanics.

Do NOT add new gameplay systems.

Instead, take the existing implementation and bring its interaction, UI/UX, WorldGuard compatibility, Totem behavior, and overall polish to a production-quality standard.

The goal is:

Maximum polish without visual clutter.
WTotems should feel extremely clean and responsive during PvP.


1. WTOTEM VS VANILLA TOTEM — HARD SEPARATION
Every WTotem is still physically based on:

TOTEM_OF_UNDYING

However, a custom WTotem must NOT behave as a normal vanilla Totem of Undying.

Use a reliable internal identifier such as:

PDC:
wtotems:id = strength
wtotems:id = speed
...

Never identify WTotems using display name or lore alone.


Vanilla Totems
A normal vanilla:

TOTEM_OF_UNDYING

with no WTotem identifier must remain completely vanilla.

Do not modify:

resurrection
activation
item behavior
inventory behavior
stacking
usage
Players can own multiple vanilla Totems.


WTotems
A WTotem must:

remain a TOTEM_OF_UNDYING
be droppable
be pick-up-able
be movable
be storable
be tradable
survive normal item movement
retain its WTotem identity
BUT:

WTotems must NOT trigger vanilla Totem resurrection.
If the player would normally trigger a Totem of Undying using a custom WTotem, cancel/prevent the vanilla Totem behavior.

The custom WTotem system controls its own abilities.

Do not let a Strength/Speed/Wolf/etc. WTotem accidentally save a player from death through vanilla Totem mechanics.

Vanilla Totems must still work normally.


2. ONE WTOTEM RULE
The existing rule remains:

A player can possess only ONE custom WTotem.
This does NOT mean WTotems are soulbound.

A player can:

obtain WTotem
↓
drop WTotem
↓
no longer possess WTotem
↓
obtain another WTotem

If the player already owns:

🔥 Strength Totem

and obtains:

⚡ Speed Totem

the NEW Speed Totem is discarded.

The existing Strength Totem remains untouched.


3. WORLDGUARD INTEGRATION
Add proper WorldGuard support.

If WorldGuard is installed, WTotems must respect WorldGuard protection.

Do NOT simply check:

"Is the player inside a WorldGuard region?"
That is not enough.

A player may be inside a region where they are allowed to build.

Instead, determine whether the player is actually permitted to modify/use that area.


4. WTOTEM USAGE IN PROTECTED AREAS
By default:

A player should only be able to activate/use WTotem abilities where they are allowed to build/break.
In practical terms, if the player is inside an area where WorldGuard prevents them from modifying the environment, WTotem activation should be blocked.

Example:

Spawn
WorldGuard region:

Build: DENIED

Player attempts:

🔥 Berserk
⚡ Dash
🐺 Call of the Pack
🌪 Updraft

The ability should NOT activate.

No:

cooldown consumption
summoned entities
ability damage/effects
fake activation animation
misleading sound
Instead:

⚠ WTotems » You cannot use WTotems in this protected area.


5. WORLDGUARD PERMISSION CHECK
The check must use the actual player/region permission context.

Respect:

region ownership
members
groups
priorities
applicable WorldGuard flags
bypass permissions
Do not blindly deny everyone inside every region.

If a player has legitimate permission to build/use the region, WTotems should be allowed.


6. WORLDGUARD BYPASS
WorldGuard bypass users should not accidentally be blocked.

If a player has appropriate WorldGuard bypass/access, respect it.

The integration should rely on WorldGuard's proper permission/query APIs rather than hardcoded assumptions.


7. WORLDGUARD CONFIGURATION
Make the integration configurable.

Example:

worldguard:
enabled: true

require_build_permission: true
require_break_permission: true

deny_message: "&c⚠ &fWTotems » You cannot use WTotems in this protected area."

If WorldGuard is not installed:

WTotems continues working normally.

Do NOT make WorldGuard a hard dependency unless explicitly required.


8. WHAT SHOULD BE BLOCKED
The WorldGuard restriction should apply to WTotem actions that represent the player's combat/ability interaction.

At minimum:

active WTotem abilities
WTotem ability activation
temporary combat entities created by WTotems
abilities affecting players/areas
abilities that would otherwise bypass a protected area's intended restrictions
Examples:

Strength → Berserk
Speed → Dash
Guard → Iron Will
Gambler → All In
Wind → Updraft
Octopus → Ink Cloud
Bee → Bee Swarm
Wolf → Call of the Pack
Hex → Bad Luck
Hunter → Executioner

Do not let players use WTotems as a way to bypass protected spawn/safe-zone rules.


9. DO NOT BREAK NORMAL ITEM INTERACTION
WorldGuard protection must NOT make WTotems permanently unusable as inventory items.

Players should still be able to:

move them
drop them
pick them up
store them
trade them
The restriction is about WTotem usage/activation, not possession.


10. PERSISTENT HUD — CLEAN, NOT ANNOYING
The WTotem HUD should be persistent.

However, it must be extremely lightweight.

Do NOT make the entire screen constantly animate.

Do NOT flicker the action bar.

Do NOT recreate the entire HUD every tick.

The HUD should remain in a stable position.

Example:

🔥 STRENGTH
Berserk 18s
Kills 47

Then:

🔥 STRENGTH
Berserk 17s
Kills 47

The interface should feel like the same UI updating.


11. HUD MUST NOT FLICKER
This is a hard requirement.

Avoid implementation patterns where:

clear HUD
send HUD
clear HUD
send HUD

happens repeatedly.

Use efficient updates.

The player should perceive a stable HUD.

Only the information that changed should visually change.


12. HUD CONTENT
Keep it compact.

Persistent information should be limited to useful information:

current WTotem
active ability
cooldown/status
one or two useful stats
Example:

🐺 WOLF
Pack 41s
Wolves 18

Do NOT permanently display:

every stat
every passive
every mechanic
every cooldown
long descriptions
The GUI can provide detailed information.

The HUD is for combat awareness.


13. EVENT-DRIVEN UI
This is where the UI/UX should become much more polished.

Permanent UI:

Minimal.
Important events:

Temporary, noticeable, polished.

Ability activation
When activating:

🔥 BERSERK
ACTIVE

Briefly show a clean notification.

Then remove it.

The persistent HUD remains.


Cooldown started
Brief notification:

🔥 Berserk activated
Cooldown: 30s

Then disappear.

The persistent HUD continues showing:

Berserk 29s


Ability ready
When cooldown reaches zero:

🔥 BERSERK READY

Briefly display it.

Then return to normal.

Do not repeatedly flash it.


WTotem pickup
When obtaining a WTotem:

🔥 Strength Totem acquired

Short and clean.


WTotem denied
If the player already owns a WTotem:

⚠ WTotems » You already have a WTotem.

Explain that the newly obtained Totem was discarded if appropriate.


14. CONTEXTUAL UI
Different situations can temporarily modify the HUD.

For example:

Hunter target
👁 HUNTER
Target: Steve
Distance: 18m
Executioner READY

Wolf active
🐺 WOLF
Pack ACTIVE
Wolves: 11

Strength Berserk
🔥 STRENGTH
BERSERK ACTIVE
Hits: 3/5

Once the temporary state ends, return to the normal HUD.


15. HUD TRANSITIONS
When changing states:

READY
↓
ACTIVATED
↓
ACTIVE
↓
COOLDOWN
↓
READY

The transitions should be subtle.

Avoid huge animations.

Avoid constant flashing.

The user should always know the state without being distracted from combat.


16. GUI UX
The /wtotems GUI should be treated as the full information interface.

The HUD is the quick combat interface.

The GUI provides:

all 10 WTotems
passive
active ability
cooldown
recipe
stats
equipped state
visual identity
configuration/status where appropriate

17. GUI ITEM STATES
Make item states obvious.

For example:

Currently owned
🔥 Strength Totem
✓ EQUIPPED

Not owned
⚡ Speed Totem
Available

Disabled Totem
🐝 Bee Totem
DISABLED

Do not use confusing icons or unnecessary decoration.


18. RECIPE UI
Recipe viewing should be visual.

Show the actual 3x3 recipe.

The output should be the actual WTotem item.

Remember:

Material = TOTEM_OF_UNDYING

Do not display a fake item as the result.


19. ITEM TOOLTIP / LORE
Make WTotem lore compact and readable.

Example:

🔥 Strength Totem

§7A WTotem infused with raw power.

§6Passive
§fStrength II

§6Ability
§fBerserk
§7Your next 5 valid melee hits
§7deal Strength III-level damage.

§8Cooldown: 30s

Avoid huge walls of text.


20. VISUAL EFFECT PHILOSOPHY
The visual system should follow:

Subtle when idle. Strong when activated.
Do not cover the player in permanent particles.

Idle:

very small
low frequency
Totem-specific
Activation:

stronger
short
recognizable
Cooldown:

minimal
Ready:

one small feedback pulse

21. TOTEM-SPECIFIC VISUAL LANGUAGE
Keep the already-established identities.

Strength:

fire
impact
Speed:

electricity
movement streak
Guard:

shield
protection
Gambler:

coins
luck
Wind:

gust
expanding ring
Octopus:

ink
mist
Bee:

swarm
pollen
Wolf:

pack
howl
Hex:

curse
rune
Hunter:

target
tracking
Do not introduce massive permanent auras.


22. ABILITY ACTIVATION SEQUENCES
Major abilities should have a short sequence:

Preparation
↓
Activation
↓
Main effect
↓
Short aftermath

For example:

Wind
small spiral
↓
expanding ring
↓
gust
↓
players launch
↓
particles fade

Wolf
summon ring
↓
pack spawn
↓
howl
↓
wolves attack

Hex
rune
↓
curse pulse
↓
target disruption
↓
rune disappears

Keep sequences short.


23. PERFORMANCE
UI and visual polish must NOT come at the expense of server performance.

Avoid:

per-tick HUD recreation
unnecessary packet spam
massive particle counts
one repeating task per player for no reason
one repeating task per wolf
permanent visual entities
unnecessary world scans
Prefer:

centralized schedulers
event-driven effects
cached player state
efficient countdown handling
short-lived tasks
proper cleanup

24. VISUAL QUALITY SETTINGS
Support:

visuals:
particle_quality: MEDIUM
particle_view_distance: 32

Possible quality levels:

LOW
MEDIUM
HIGH

LOW reduces particle counts.

MEDIUM is the default.

HIGH provides the intended full effect.

The default must still look good.


25. WORLDGUARD + UI FEEDBACK
If an ability is blocked by WorldGuard:

Do NOT show the normal activation animation.

Do NOT play the successful activation sound.

Do NOT start the cooldown.

Instead:

⚠ WTotems » You cannot use WTotems in this protected area.

The persistent HUD remains unchanged.

Example:

Before attempt:

🔥 STRENGTH
Berserk READY

Player tries in protected area.

After denial:

🔥 STRENGTH
Berserk READY

It stays READY.

This makes it immediately obvious that the ability was not consumed.


26. ABILITY FAILURE UX
The same principle applies to other legitimate failure cases.

If an ability cannot activate because of:

WorldGuard
invalid target
missing target
internal restriction
cooldown
disabled Totem
give a short, useful response.

Do not silently consume the ability.

Do not consume cooldown unless the activation actually occurred.


27. WTOTEM DROPPING
WTotems must remain normal inventory items.

Players can press:

Q

and drop them.

The plugin must NOT cancel the drop simply because the item is a WTotem.

The WTotem retains its PDC identity after being dropped.

Another player can pick it up.


28. PROTECTED AREA DOES NOT MEAN ITEM LOCK
WorldGuard restrictions must NOT cause:

"You are in spawn, therefore your WTotem cannot be moved."
That is incorrect.

The player can still possess/move/store/drop the item.

Only WTotem ability usage is restricted.


29. VANILLA TOTEM TEST MATRIX
Explicitly test:

Test A
Player has:

5 Vanilla Totems
+
1 WTotem

Valid.

Test B
Player uses vanilla Totem.

Vanilla behavior works.

Test C
Player attempts to trigger a WTotem as a vanilla resurrection item.

Vanilla resurrection does NOT happen.

Test D
Player drops WTotem.

Works.

Test E
Player picks WTotem up.

Works.

Test F
Player already owns WTotem and obtains another.

New WTotem discarded.

Existing WTotem remains.


30. WORLDGUARD TEST MATRIX
Test:

Protected spawn
Build/break denied.

WTotem abilities blocked.

Allowed region
Build/break allowed.

WTotem abilities work.

Region member
If member has appropriate build permissions:

WTotems work.

WorldGuard bypass
WTotems work.

No WorldGuard installed
WTotems work normally.

Region overlap
Use WorldGuard's actual region/priority/query behavior.

Do not invent custom region logic.


31. RELOAD SAFETY
Run:

/wtotems reload

while:

HUD is visible
player is on cooldown
ability is active
wolves exist
bees exist
targets are marked
hotbar locks exist
After reload:

HUD remains correct
cooldown state remains valid
temporary entities are handled safely
no duplicate tasks
no duplicate effects
no ghost UI
no broken WTotems

32. FINAL UX PRINCIPLE
WTotems should have two layers of UI.

Layer 1 — Persistent
Minimal:

🔥 STRENGTH
Berserk 18s
Kills 47

Always available.

Layer 2 — Event-driven
Temporary:

🔥 BERSERK ACTIVATED

or:

🔥 BERSERK READY

or:

⚠ PROTECTED AREA

or:

🔥 STRENGTH TOTEM ACQUIRED

These appear only when something important happens.

This creates a polished interface without turning the screen into a mess.


33. FINAL QUALITY BAR
Before calling this pass complete, test WTotems as an actual player.

Ask:

Can I tell what Totem I have?
Can I tell whether my ability is ready?
Can I tell when it is active?
Can I tell when it is on cooldown?
Does the UI stay stable?
Does important information appear when needed?
Does it disappear when no longer needed?
Can I still clearly see PvP?
Can I use my WTotem where I am actually allowed to?
Does WorldGuard protection prevent ability abuse?
Does a WTotem remain a real Totem item?
Does a WTotem avoid accidentally triggering vanilla Totem resurrection?
Can I still drop and trade it?
Does a vanilla Totem remain completely unaffected?
If all of these are true, the WTotem interaction layer is finished.


FINAL INSTRUCTION
Do not add more gameplay.

Do not add more progression.

Do not make the plugin unnecessarily complicated.

Focus on:

stable HUD + contextual UI + clean GUI + WorldGuard integration + correct Totem behavior + lightweight visual feedback + performance.

The intended feeling is:

Everything is visible when I need it, beautiful when something happens, and completely out of the way when nothing is happening.
That is the final WTotems UI/UX standard.

SMALL TOTEM TEXTURE / VISUAL IDENTIFICATION
Add a lightweight visual identity system so every WTotem is immediately recognizable when another player is holding or using it.

The WTotems must still use the real TOTEM_OF_UNDYING item as their base material, but their appearance should have subtle custom visual differences.

Requirements
Give each of the 10 WTotems a small, distinct texture/model variation.
The variation should be easy to recognize at a glance but not oversized, flashy, or cluttered.
Keep the normal Totem silhouette recognizable.
Do NOT turn WTotems into giant custom objects.
Do NOT add floating 3D cores, giant icons, or permanent holograms.
The visual difference should work both:

in the player's hand
when another player is holding the WTotem
inside inventories/GUIs where possible
Visual Identity Examples
Use subtle design accents matching each ability:

🔥 Strength → small flame/red accent
⚡ Speed → small lightning/electric accent
🛡 Guard → small shield/metal accent
🎰 Gambler → small coin/luck accent
🌪 Wind → small wind/swirl accent
🐙 Octopus → small ink/tentacle accent
🐝 Bee → small bee/honey accent
🐺 Wolf → small wolf/claw accent
🧿 Hex → small curse/glyph accent
👁 Hunter → small eye/target accent
The exact textures can be designed cleanly around the existing Totem shape.

OPTIONAL RESOURCE-PACK SUPPORT
If the server uses a resource pack, support custom item models/textures for each WTotem.

Use the internal WTotem ID/PDC to determine the model.

Example concept:

TOTEM_OF_UNDYING
├── wtotem_strength
├── wtotem_speed
├── wtotem_guard
├── wtotem_gambler
├── wtotem_wind
├── wtotem_octopus
├── wtotem_bee
├── wtotem_wolf
├── wtotem_hex
└── wtotem_hunter

If no resource pack is installed, the plugin must still function normally using the standard Totem appearance plus names, lore, particles, and UI.

THIRD-PERSON RECOGNITION
When a player is holding a WTotem, other players should be able to identify which WTotem it is from its small visual design.

Do not rely exclusively on the item name or lore.

The visual identity should remain readable during PvP without obstructing the screen.

ACTIVATION STATES
Optionally support a very subtle temporary visual state while the WTotem's active ability is being used:

Idle → subtle custom texture
Ready → subtle visual accent
Activated → brief stronger visual effect
Cooldown → normal/subdued appearance

Do not constantly animate the item.

The goal is:

"I can instantly tell which WTotem that player has, but it still looks like a Minecraft Totem."

Keep this lightweight, performant, and compatible with the existing WTotem PDC/ID system.
Kodari AI
KodariSep 25 at 2:47 am 4
  1. Fix WTotem identity, vanilla resurrection separation, and one-WTotem ownership.

  2. Add optional WorldGuard permission checks to ability activation.

  3. Polish the persistent HUD, event feedback, and GUI/recipe presentation.

  4. Add lightweight Totem-specific visual identity and verify reload/performance cleanup.

  1. Totems: Custom WTotems are blocked from vanilla resurrection by their PDC identity; normal vanilla Totems remain unchanged. Existing duplicate handling preserves the player’s current WTotem and leaves dropping, pickup, and trading available.

  2. WorldGuard: Added optional WorldGuard 7 support with build/break permission checks, owner/member context, and bypass handling. Denied activations return before cooldowns or effects; related passives, area effects, and temporary-mob damage are also gated. Settings and denial text are configurable, and the plugin remains usable without WorldGuard.

  3. HUD and GUI: Routed pickup, activation, cooldown, and ready notices through a temporary action-bar layer over the persistent HUD; stale HUDs clear when no longer applicable. The GUI now distinguishes owned/available and enabled/disabled Totems. Its existing 3×3 recipe display and real Totem output are retained.

  4. Visuals and reload: Added LOW/MEDIUM/HIGH particle quality and configurable view distance. Totems receive distinct CustomModelData IDs 1001–1010 for resource-pack overrides; without a matching pack, they retain the normal Totem appearance. /wtotems reload still preserves active state and does not schedule duplicate tasks.

Limitations: No resource-pack texture assets were added, and this pass wasn’t tested on a live server.

5k4g

shift + right click to activate the active ability can u add texture assests too :3

Kodari AI
KodariSep 25 at 3:07 am 1
  1. Trace how active abilities are selected and activated, then add shift-right-click activation.

  2. Check the existing item/resource setup and add matching texture assets if the project supports them.

Shift-right-click activation is in place, and the item lore reflects the new control. I’m checking how this project distributes custom models and textures before adding the assets.

Shift + right-click now activates a held totem, and its lore shows the new control.

I added a Minecraft 1.21.4 resource-pack layout with model mappings for all ten totems. Generate the PNG textures with python resource-pack/generate_textures.py, then distribute the resource-pack folder to players; automatic pack hosting isn’t configured.

5k4g

umm shift click doesnt work + wtotem should also work as normal totems pops aswell and lwk does wtever normal totem do and do the active skill key to shift + click any click right or left test it too

Kodari AI
KodariSep 25 at 3:20 am 1

Plan:

  1. Read the current totem listener/item logic and fix active-skill click detection.

  2. Preserve normal totem-of-undying behavior while allowing skill activation on either hand.

  3. Check the changes against left- and right-click event paths.

Fixed the click handling: sneak + left/right-click activates the ability, including left-clicking an entity, and works with the totem in either hand. Shift-clicking an entity won’t also hit it.

Removed the cancellation that stopped WTotems from popping, so they now use the normal totem-of-undying resurrection behavior. Updated the item lore to show both click options.

I couldn’t run a live Minecraft server test here, but the interaction and attack event paths are handled.

5k4g

need a detailed lore for active and passive abilities and also like some stuff dont work so make that worka nd also make this more better and more features to make this better and so also in gambling token it doesnt tell the user or the guys whos slot is gettin locked like which slot is gettin locked also tell when active ability is used 7 people got affected by your ability yk wt i mean

Kodari AI
KodariSep 25 at 4:17 am 3
  1. Add detailed lore for each totem’s active and passive abilities.

  2. Improve ability-use feedback, including the gambling token’s locked-slot message and affected-player count.

  3. Trace and fix concrete ability issues in the existing implementation.

  1. Added per-totem passive/active descriptions to item lore and the details GUI, with the current shift-click controls shown.

  2. Next, I’m tracing ability feedback so successful effects can report who was affected, and Gambler can name the locked hotbar slot to both players.

  1. Ability activations now give a chat confirmation; Wind, Octopus, and Gambler report unique player counts, and Gambler names the locked slot to both players. I’m checking the ability flows for specific broken behavior rather than guessing at fixes.1. Added detailed passive and active ability lore for all ten totems in both item tooltips and the info menu.

  2. Abilities now confirm activation in chat. Wind, Octopus, and Gambler report how many unique players were affected; Gambler tells both players the exact hotbar slot number that was locked.

  3. Fixed Hunter’s Executioner: moving out of range no longer cancels the ability early. It can still affect the marked target if they return within range before the ability expires.

I couldn’t test these changes on a live Minecraft server.

5k4g

also how do i add custom texture pack in this

Kodari AI
KodariSep 25 at 4:28 am 1

The project already has a resource-pack setup. To use your own totem art:

  1. Make each totem image a transparent PNG and place it here: resource-pack/assets/wtotems/textures/item/

  2. Use these exact filenames so the existing models find them: totem_strength.png, totem_speed.png, totem_guard.png, totem_gambler.png, totem_wind.png, totem_octopus.png, totem_bee.png, totem_wolf.png, totem_hex.png, and totem_hunter.png.

  3. Keep the existing model and item-mapping JSON files. They connect the totems’ custom model data values (1001–1010) to those textures. The included generator creates simple default artwork; running it again overwrites the PNGs, so don’t run it after replacing them with your own.

  4. Zip the pack so pack.mcmeta and assets/ are at the root of the ZIP, not inside an extra resource-pack/ folder. The pack metadata is set for Minecraft 1.21.4.

  5. Upload the ZIP somewhere players’ clients can download it directly over HTTPS. Set the URL in the server’s server.properties:

    Properties
    resource-pack=https://your-host.example/wtotems.zip
    

    Restart the server; players will be prompted to download it. To require the pack, set require-resource-pack=true.

For a quick local preview, put the resource-pack folder in your client’s .minecraft/resourcepacks folder, enable it in Minecraft, then press F3+T to reload.

5k4g

here are 5 of em ima give u rest 5 rq dont do anything js yk

5 images attached
Kodari AI
KodariSep 25 at 5:01 am 1

Got these five. Send the other five when you’re ready—I won’t change anything yet.

5k4g

Strength Cracked stone-fist chest plate, ember particles rising (not floating dots), double-layer flame aura (orange core + red outer) Speed Motion-blur streak lines trailing behind arms, blue lightning fork wraps around the whole body instead of one bolt on chest Guard Actual riveted armor plating texture on torso, shield icon raised/embossed with metallic highlight, small chips/dents for wear Gambler Tilted top hat sitting ON the head (not painted on chest), scattered gold coins + dice orbiting, one green glowing eye for "luck" Wind Twin wind-ribbons wrapping fully around the totem in a figure-8, feather/leaf particles instead of dots Wolf Actual pointed wolf ears extending from head silhouette, glowing paw print on chest, fur-tuft texture on shoulders Hunter Single large glowing red eye dead-center (bigger, creepier), crosshair-like cracks radiating from it, dark red mist instead of sparks Hex Rotating hexagon ring around the head like a halo, rune symbols glowing on the arms, deep purple/magenta gradient body Octopus Tentacles replace the arms entirely (curling outward), suction-cup dots on tentacle undersides, teal-to-purple gradient Bee Actual small wings on the back, black/yellow banding wraps the whole torso (not just a patch), tiny sparkle trail like pollen

5 images attached
Kodari AI
KodariSep 25 at 5:01 am 1

Got the design notes for all ten totems and these five images. I won’t make changes yet—send the rest whenever you’re ready.

5k4g

gave u all 10th btw

Kodari AI
KodariSep 25 at 5:02 am 1

Got it—I’ve got the designs for all ten totems now. I’ll hold off on making changes until you tell me to start.

5k4g

add all these texture pack in my plugin

Kodari AI
KodariSep 25 at 5:05 am 1

Plan:

  1. Replace the placeholder sprites with detailed, custom pixel-art designs for all ten totems.

  2. Keep the generator dependency-free and preserve the existing resource-pack texture paths.

  3. Generate each PNG by running the pack’s texture-generation script.

Updated resource-pack/generate_textures.py to draw all ten totems as detailed, transparent 32×32 pixel-art textures, matching your design notes.

Run this to create the PNG files:

Shell
python resource-pack/generate_textures.py

It writes them to resource-pack/assets/wtotems/textures/item/. Include the resource-pack folder in the resource-pack ZIP you distribute to players.

5k4g

change the abilities to Strength Berserker Taking damage builds rage stacks; at max stacks your next hit deals bonus damage + knocks back — punishes people who trade with you Speed Duelist / gap closer Dash through an enemy = bonus damage + they're briefly slowed, so it's a real engage tool, not just repositioning

Guard Anti-combo tank Brief crowd-control immunity (can't be slowed/stunned) + reflects part of melee damage — hard counters combo-focused attackers Gambler High-risk wildcard On activation: 50% massive buff (crit+haste), 50% brief vulnerability — genuinely risky to pop mid-fight, rewards good timing Wind Space control Knock enemies away + self slow-fall — use it to escape a gank or peel someone off a teammate Octopus Area denial / setup Ink cloud blinds+slows enemies inside it; you can grapple INTO the cloud to jump someone standing in it Bee Harasser / zone-out Bees apply stacking poison and specifically target whoever last hit you — forces enemies to disengage or keep eating damage Wolf Focus-fire / peel Wolves prioritize attacking whoever is hitting you, actively defending you in a fight instead of just existing Hex Anti-heal / sustain check Cursed target has healing reduced and curse jumps if they hit someone else — hard counters healers/regen builds Hunter Assassin / execute Marked target takes bonus true damage below 30% HP + you get a speed boost while chasing them — built for finishing kills

i want u to make it better like the dash and sm shi works in a pvt srvr but not in public + its not good as i wanted it lowered my expectation so much also i need like a change in the position of hud as it is clashing with my combat timer plugin and gettin bugged so yh and yh make every feature better and dont code first ask first

The plugin uses player.teleport() for the dash, and calls a WorldGuard region check (canUseTotems) before every single ability, not just dash. Two likely culprits, both explain "works private, breaks public":

WorldGuard version mismatch — WorldGuardSupport.java loads WorldGuard via reflection at startup. If your public server runs a different WorldGuard build than this was compiled against, that load silently fails (just logs one line to console, easy to miss), and canUseTotems() then returns false for every player, in every world, permanently — blocking all 10 totems entirely.

Anti-cheat/combat plugins on public server cancel teleports — dash() calls player.teleport(safe), and if any other plugin (anti-cheat, combat-tag, etc.) cancels that teleport event, it just returns false with zero error — private servers usually run fewer plugins so this never surfaces there.

Bug 2: HUD clash with your combat timer

Kodari AI
KodariSep 25 at 11:04 am 1

I won’t change or code anything until we agree on the approach. I’ve got the new ability designs; before implementation, please answer these:

  1. Public server: What Minecraft version and server software does it run (Paper/Spigot), and which anti-cheat, combat-tag, and WorldGuard plugins are installed? When dash fails, does the ability activate but you don’t move, or does nothing happen? If you can, send the related console errors too.

  2. HUD: What is the HUD currently shown as—action bar, boss bar, scoreboard, or something else? Which combat-timer plugin is it clashing with, and where would you like the totem HUD instead?

  3. Controls: Should active abilities still use sneak + left- or right-click, as before?

  4. Balance: Are you happy for me to choose reasonable durations, ranges, stack limits, and cooldowns for the redesigned abilities, or do you have specific values in mind?

Once you reply, I’ll outline the changes for your approval before touching the code.

5k4g

paper 1.21.11 yh installd and not js dash nthing works like fr dude nthing works properly

currently shown as action bar , celest combat pro

3 yh

4th yh js balanced af

Kodari AI
KodariSep 25 at 11:09 am 1

I’ll review the ability checks and action-bar HUD first, then propose a concrete fix and balanced ability behavior for you to approve. I won’t edit anything until you approve the plan.For Paper 1.21.11, with WorldGuard installed, sneak + click controls, and Celest Combat Pro using the action bar, here’s the plan I recommend. I haven’t changed any files.

The code confirms two things worth addressing: WorldGuard checks can block all abilities if its integration fails to load, and the default region checks require both build and block-break permission. Also, the totem HUD writes to the action bar every tick, so it can compete directly with Celest’s combat timer. I can’t confirm which is causing the public-server failures without its startup logs and region settings.

  1. Make ability failures visible and fix the activation flow: audit active and passive ability paths, make denials explain the reason, and ensure a failed activation doesn’t consume its cooldown. Make WorldGuard’s effect on abilities clear and configurable rather than letting a failed integration silently make everything unusable.

  2. Replace the abilities with your designs: Strength rage stacks; Speed’s enemy-piercing engage dash; Guard’s crowd-control resistance and melee reflection; Gambler’s clearly announced 50/50 buff or vulnerability; Wind’s knockback and slow-fall; Octopus’s ink cloud and grapple engage; Bee’s poison pressure on your last attacker; Wolf’s defense against your last attacker; Hex’s anti-heal curse that jumps when its target hits someone; Hunter’s low-health execute mark and chase speed. I’ll choose balanced values and add feedback so players can tell when effects trigger.

  3. Move the totem HUD off the action bar: use a configurable boss bar for the totem HUD, leaving the action bar available for Celest Combat Pro. Keep the existing HUD text/settings where practical.

  4. Keep sneak + click controls and verify the project’s activation paths and build after the changes. I can’t live-test it on your server, so clearer in-game messages and diagnostics will help identify any remaining server-specific blocks.

If you approve this plan—including the boss bar HUD—reply “approve” and I’ll make the changes.

5k4g

approve and also seprarate every totem file so it works more in better way like 10 new files rather than a single file with 100k lines of code

Kodari AI
KodariSep 25 at 11:45 am 6
  1. Split the totem implementations into separate files without changing behavior.

  2. Rework the ten abilities and activation checks, including clearer failure feedback.

  3. Move the totem HUD to a boss bar so it stops competing with Celest Combat Pro’s action bar.

The activation paths currently spend cooldowns even when an ability fails, and the WorldGuard integration can deny every totem if its optional hook fails to load. I’m fixing those shared blockers while moving combat behavior into the individual ability files and replacing the old effects with your designs.

Implemented the approved redesign.

  • Split ability logic into ten files: StrengthAbility, SpeedAbility, GuardAbility, GamblerAbility, WindAbility, OctopusAbility, BeeAbility, WolfAbility, HexAbility, and HunterAbility. Updated the menu descriptions to match.

  • Reworked the abilities around your designs: rage strikes, an anti-teleport-check velocity dash, Guard’s control immunity and damage reflection, Gambler’s 50/50 roll, Wind’s knockback and slow fall, Octopus’s ink cloud and grapple, Bee poison and Wolf targeting, Hex’s healing curse, and Hunter’s execute and chase speed.

  • Failed activations no longer consume cooldowns. WorldGuard integration failures now log a warning instead of blocking all totems; region permission enforcement is opt-in with worldguard.enforce_permissions.

  • Moved the continuous totem HUD to a boss bar so it no longer overwrites Celest Combat Pro’s action bar. Sneak + click controls remain.

I haven’t live-tested this on your public server, so I can’t confirm how its other plugins interact with the new dash or effects.

5k4g

changes Strength (Rampage) — next 3 hits guaranteed crit + lifesteal heal Speed (Blink Strike) — dash now phases through thin walls, hit right after = bonus dmg + heavy stun-like slow Guard (Fortress) — full damage immunity + 100% reflected as true damage Gambler (Jackpot) — 3-way roll: Jackpot (huge buff + steals item), Win, or Bust Wind (Tempest) — bigger knockback + brief full invulnerability to escape ganks Octopus (Kraken) — cloud now roots (not just slows), grapple pulls you in AND slams AoE damage Bee (Hive Mind) — swarm size bumped to ~15-25 bees, stings stack real poison Wolf (Alpha Call) — pack size bumped to ~20-30 wolves, rally speed boost when defending you Hex (Doom) — curse jumps on hit; if it expires unspread, it detonates true damage on the cursed player Hunter (Death Mark) — marked target Glows through walls; guaranteed true-damage execute during Executioner window

yh wolf and bees should be large in numbers :3 alr now make it

Kodari AI
KodariSep 26 at 3:18 am 5
  1. Strength: add Rampage’s three guaranteed critical hits with lifesteal.

  2. Speed: phase through thin walls, then reward a quick follow-up hit with bonus damage and a heavy slow.

  3. Guard: grant full damage immunity and reflect all incoming damage as true damage.

  4. Gambler: add Jackpot, Win, and Bust outcomes, including Jackpot’s item steal.

  5. Wind: increase knockback and add brief full invulnerability.

  6. Octopus: root targets in the cloud and make the grapple pull-and-slam for AoE damage.

  7. Bee: increase the swarm to 15–25 and make stings stack poison.

  8. Wolf: increase the pack to 20–30 and add a rally speed boost while defending you.

  9. Hex: spread the curse on hit; detonate for true damage if it expires unspread.

  10. Hunter: show the mark through walls and add a guaranteed true-damage execute window.

Starting with Strength.

  1. Strength: Rampage now empowers the next three melee hits with 1.5× critical damage and 25% lifesteal. Next: Speed.

  1. Speed: added a phase through detected thin walls, a 1.2-second follow-up window, 1.5× damage, and a three-second heavy slow. Next: Guard.

  1. Guard: Fortress now cancels all incoming damage and reflects 100% of melee damage directly as true damage. Next: Gambler.

  1. Gambler: replaced the 50/50 with equal Jackpot/Win/Bust rolls; Jackpot grants stronger buffs and steals one ordinary inventory item on the next hit. Next: Wind.

  1. Wind: Tempest now knocks enemies back harder and grants 1.5 seconds of full damage immunity. Next: Octopus.

  1. Octopus: the ink cloud now roots enemies in place; a second activation pulls you toward a cloud target and lands a configurable AoE slam. Next: Bee.

  1. Bee: Hive Mind now summons a random 15–25 bees (subject to configured caps), and their hits stack poison up to Poison V. Next: Wolf.

  1. Wolf: Alpha Call now summons 20–30 wolves (with matching caps), and defending you gives the pack a five-second Speed III rally. Next: Hex.

  1. Hex: Doom now detonates for 6 true damage if its curse expires without being passed on; a curse that spreads will not detonate. Next: Hunter.

Implemented the ten redesigned abilities and updated their in-game names and descriptions:

  1. Strength — Rampage: Your next 3 melee hits deal 1.5× damage and heal you for 25% of damage dealt.

  2. Speed — Blink Strike: Dash through walls up to 1 block thick; hit within 1.2 seconds for 1.5× damage and a 3-second heavy slow.

  3. Guard — Fortress: For 5 seconds, incoming damage is cancelled and melee attackers take 100% of that damage as true damage.

  4. Gambler — Jackpot: Activation rolls Jackpot, Win, or Bust. Jackpot gives strong buffs and steals one ordinary item on your next hit.

  5. Wind — Tempest: Increased knockback and 1.5 seconds of full damage immunity.

  6. Octopus — Kraken: The cloud roots enemies; grappling pulls you toward a target, then slams nearby enemies for AoE damage.

  7. Bee — Hive Mind: Summons 15–25 bees; repeated stings stack Poison V.

  8. Wolf — Alpha Call: Summons 20–30 wolves; they gain Speed III for 5 seconds when rallying to your defense.

  9. Hex — Doom: The curse transfers when its holder hits another player. If it expires without spreading, it detonates for 6 true damage.

  10. Hunter — Death Mark: Marked targets glow through walls; during Executioner, a hit that takes the target below 30% health triggers a lethal true-damage execute.

The bee and wolf counts are configurable and capped at 25 and 30 per owner. I haven’t live-tested these changes on your public server. Speed uses a short teleport only to cross a detected thin wall, so an anti-cheat that cancels teleports could still block that part of the dash.

Kodari can make mistakes. Review important code before using.
Files
resource-pack
src
build.gradle
settings.gradle
Code
41 3,681
src/main/java/com/wtotems/WTotemsPlugin.java
package com.wtotems;

import org.bukkit.Bukkit;
import org.bukkit.configuration.file.YamlConfiguration;
import org.bukkit.entity.Player;
import org.bukkit.plugin.java.JavaPlugin;

import java.io.File;

public final class WTotemsPlugin extends JavaPlugin {
    private TotemItems items;
    private TotemStats stats;
    private TotemManager manager;
    private TotemRecipes recipes;
    private java.util.function.Predicate<Player> worldGuard;
    private boolean worldGuardInstalled;

    @Override
    public void onEnable() {
        saveDefaultConfig();
        ensureResource("messages.yml");
        ensureResource("recipes.yml");
        worldGuardInstalled = Bukkit.getPluginManager().isPluginEnabled("WorldGuard");
        if (worldGuardInstalled) {
            try {
                worldGuard = loadWorldGuardSupport();
            } catch (ReflectiveOperationException | ClassCastException | LinkageError exception) {
                getLogger().warning("WorldGuard integration is unavailable; WTotems will remain usable. " + exception.getMessage());
            }
        }
        items = new TotemItems(this);
        stats = new TotemStats(this);
        manager = new TotemManager(this);
        recipes = new TotemRecipes(this, items);
        recipes.reload();
        Bukkit.getPluginManager().registerEvents(new TotemListener(this), this);
        WTotemsCommand command = new WTotemsCommand(this);
        getCommand("wtotems").setExecutor(command);
        getCommand("wtotems").setTabCompleter(command);
        Bukkit.getScheduler().runTaskTimer(this, manager::tick, 20L, 20L);
        Bukkit.getScheduler().runTaskTimer(this, stats::save, 6000L, 6000L);
        getLogger().info("WTotems enabled with exactly 10 custom WTotems.");
    }

    @Override
    public void onDisable() {
        if (manager != null) manager.cleanup();
        if (stats != null) stats.save();
    }

    public void reloadPlugin() {
        reloadConfig();
        YamlConfiguration messages = YamlConfiguration.loadConfiguration(new File(getDataFolder(), "messages.yml"));
        recipes.reload();
        manager.reloadMessages(messages);
    }

    private void ensureResource(String name) {
        if (!new File(getDataFolder(), name).exists()) saveResource(name, false);
    }

    public TotemItems items() { return items; }
    public TotemStats stats() { return stats; }
    public TotemManager manager() { return manager; }
    public TotemRecipes recipes() { return recipes; }

    public boolean worldGuardEnabled() {
        return worldGuardInstalled && getConfig().getBoolean("worldguard.enabled", true);
    }

    public boolean canUseTotems(Player player) {
        if (!worldGuardEnabled() || !getConfig().getBoolean("worldguard.enforce_permissions", false)) return true;
        if (worldGuard == null) return true;
        try {
            return worldGuard.test(player);
        } catch (RuntimeException | LinkageError exception) {
            worldGuard = null;
            getLogger().warning("WorldGuard checks failed; WTotems will remain usable. " + exception.getMessage());
            return true;
        }
    }

    @SuppressWarnings("unchecked")
    private java.util.function.Predicate<Player> loadWorldGuardSupport() throws ReflectiveOperationException {
        return (java.util.function.Predicate<Player>) Class.forName("com.wtotems.WorldGuardSupport")
                .getConstructor(WTotemsPlugin.class).newInstance(this);
    }
}