itzzmeclaire_

AXOTEAMS - COMPLETE DEVELOPMENT PROMPT

Create a complete, production-ready premium Minecraft plugin named AxoTeams.

The plugin must be built to premium BuiltByBit-quality standards, with clean architecture, polished native Paper Dialog UI, persistent storage, configurable systems, proper validation, permissions, optimized performance, PlaceholderAPI support, and AJLeaderboards compatibility.

Do not provide pseudo-code, fake APIs, incomplete classes, TODO implementations, or simplified versions of requested features.

The final project must compile and run directly on Paper 1.21.11 with Java 21.

---

  1. CORE INFORMATION

Plugin:

AxoTeams

Author:

DevSolentz

Main package:

dev.axoryn.axoteams

Target:

Paper 1.21.11 Java 21

Use Paper's official API and native Dialog API.

Avoid NMS unless absolutely necessary.

Use Adventure Components for all Dialog text.

---

  1. "/TEAM" COMMAND

The main command is:

/team

Behavior depends on whether the player belongs to a team.

Player has no team

Open the Create Team Dialog.

Player already has a team

Open the Main Team Dialog.

---

  1. CREATE TEAM DIALOG

When a player without a team executes:

/team

open a native Paper Dialog.

Conceptually:

โ”Œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ” โ”‚ [SPYGLASS SPRITE] โ”‚ โ”‚ CREATE YOUR TEAM โ”‚ โ”‚ โ”‚ โ”‚ Enter your team name below. โ”‚ โ”‚ โ”‚ โ”‚ [ Team Name Text Input ] โ”‚ โ”‚ โ”‚ โ”‚ [ Confirm ] โ”‚ โ””โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”˜

The Dialog must contain:

  • Spyglass sprite
  • Text input
  • Confirm button

Use configurable sprite syntax:

<sprite:"minecraft:items":item/spyglass>

The actual implementation must convert the sprite syntax into the appropriate Adventure/Paper Dialog component.

---

  1. TEAM NAME VALIDATION

Configuration:

team-name: min-length: 3 max-length: 16 allowed-pattern: "^[a-zA-Z0-9_]+$"

Reject:

  • Empty names
  • Too-short names
  • Too-long names
  • Invalid characters
  • Duplicate names

Team-name uniqueness must be case-insensitive.

Therefore:

Phoenix phoenix PHOENIX

are considered the same team.

After successful creation:

  • Generate Team UUID
  • Create team
  • Creator becomes Owner
  • Level = 1
  • Kills = 0
  • Team PvP = configured default
  • Create empty homes
  • Create empty warps
  • Create empty Ender Chest
  • Save team
  • Close Dialog
  • Send configurable success message

---

  1. MAIN TEAM DIALOG

For a player already in a team:

/team

opens the main Team Dialog.

Display:

๐Ÿ›ก TEAM NAME

Level: 2 Kills: 184 / 300

Members: 8 / 20 Homes: 6 / 10 Warps: 6 / 10

Team PvP: OFF

Buttons:

Ender Chest Team PvP Team Home Team Warps Team Members

Each button must support configurable sprites and full hex formatting.

---

  1. MAIN DIALOG BUTTONS

Example:

<sprite:"minecraft:items":item/ender_chest> &#00B7FF&lEnder Chest

<sprite:"minecraft:items":item/iron_sword> &#FF0000&lTeam PvP

<sprite:"minecraft:items":item/compass> &#00B7FF&lTeam Home

<sprite:"minecraft:items":item/lead> &#9B59FF&lTeam Warps

<sprite:"minecraft:items":item/player_head> &f&lTeam Members

Do not replace sprites with ordinary Unicode emoji when sprites are configured.

---

  1. TEAM ENDER CHEST

Button:

Ender Chest

opens the team's private shared Ender Chest immediately.

Do not reopen the Dialog.

Access:

Owner = YES Admin = YES Member = NO

If a Member clicks it, show a configurable no-permission message.

The Ender Chest must be unique per team and persist across restarts.

---

  1. TEAM PVP

Team PvP is a direct toggle.

Example:

โš” Team PvP OFF

Click:

ON

Do not open another Dialog.

Do not reopen the Main Dialog.

Configuration:

team-pvp: default: false

When OFF:

  • Team members cannot damage each other.

When ON:

  • Team members can damage each other.

Persist the value.

---

  1. TEAM HOMES

Clicking:

Team Home

opens a dedicated Home Dialog.

There are exactly:

10 home slots

Unlock progression:

Level 1 = 3 Homes Level 2 = 6 Homes Level 3 = 10 Homes

Example:

โ”Œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ” โ”‚ TEAM HOMES โ”‚ โ”‚ โ”‚ โ”‚ Level 1 โ”‚ โ”‚ 3 / 10 Homes Unlocked โ”‚ โ”‚ โ”‚ โ”‚ ๐Ÿ  Home 1 โ”‚ โ”‚ ๐Ÿ  Home 2 โ”‚ โ”‚ ๐Ÿ  Home 3 โ”‚ โ”‚ ๐Ÿ”’ Home 4 โ”‚ โ”‚ ๐Ÿ”’ Home 5 โ”‚ โ”‚ ๐Ÿ”’ Home 6 โ”‚ โ”‚ ๐Ÿ”’ Home 7 โ”‚ โ”‚ ๐Ÿ”’ Home 8 โ”‚ โ”‚ ๐Ÿ”’ Home 9 โ”‚ โ”‚ ๐Ÿ”’ Home 10 โ”‚ โ”‚ โ”‚ โ”‚ [ Back ] โ”‚ โ””โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”˜

---

  1. HOME STATES

Unlocked but unset

Display:

๐Ÿ  Home 1 Not Set

[ Set Home ]

Configured

Display:

๐Ÿ  Home 1 Team Base

[ Teleport ] [ Replace ] [ Delete ]

Locked

Display:

๐Ÿ”’ Home 4

Unlocks at Team Level 2

Locked slots cannot be used.

---

  1. HOME PERMISSIONS

Owner:

Set Replace Delete Teleport

Admin:

Set Replace Delete Teleport

Member:

Teleport

---

  1. HOME CONFIRMATIONS

Every destructive action must use a confirmation Dialog.

Delete:

โ”Œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ” โ”‚ DELETE HOME โ”‚ โ”‚ โ”‚ โ”‚ Delete Team Home #1? โ”‚ โ”‚ โ”‚ โ”‚ [ Confirm ] [ Cancel ] โ”‚ โ””โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”˜

Replace:

โ”Œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ” โ”‚ REPLACE HOME โ”‚ โ”‚ โ”‚ โ”‚ Replace the location of Home #1? โ”‚ โ”‚ โ”‚ โ”‚ [ Confirm ] [ Cancel ] โ”‚ โ””โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”˜

---

  1. TEAM WARPS

Click:

Team Warps

to open a dedicated Warp Dialog.

There are exactly:

10 warp slots

Unlock progression:

Level 1 = 3 Warps Level 2 = 6 Warps Level 3 = 10 Warps

Example:

โ”Œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ” โ”‚ TEAM WARPS โ”‚ โ”‚ โ”‚ โ”‚ Level 1 โ”‚ โ”‚ 3 / 10 Warps Unlocked โ”‚ โ”‚ โ”‚ โ”‚ โš‘ Base โ”‚ โ”‚ โš‘ Mine โ”‚ โ”‚ โš‘ Farm โ”‚ โ”‚ ๐Ÿ”’ Warp 4 โ”‚ โ”‚ ๐Ÿ”’ Warp 5 โ”‚ โ”‚ ๐Ÿ”’ Warp 6 โ”‚ โ”‚ ๐Ÿ”’ Warp 7 โ”‚ โ”‚ ๐Ÿ”’ Warp 8 โ”‚ โ”‚ ๐Ÿ”’ Warp 9 โ”‚ โ”‚ ๐Ÿ”’ Warp 10 โ”‚ โ”‚ โ”‚ โ”‚ [ Create Warp ] โ”‚ โ”‚ [ Back ] โ”‚ โ””โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”˜

---

  1. WARP MANAGEMENT

Owner/Admin:

  • Create
  • Rename
  • Replace
  • Delete

Member:

  • Teleport

Warp names must be validated.

Destructive actions require confirmation Dialogs.

---

  1. TEAM MEMBERS DIALOG

Click:

Team Members

to open the member-list Dialog.

Each member must display their head using:

<head:%player%>

Example:

<head:OwnerName> &#00B7FFOwnerName

<head:AdminName> &#FF0000AdminName

<head:PlayerName> &fPlayerName

The head must dynamically resolve to the actual player's head.

If unavailable, use a configurable fallback sprite.

---

  1. TEAM RANKS

Ranks:

OWNER ADMIN MEMBER

Default configuration:

team-ranks: owner: color: "&#00B7FF" display-name: "Owner"

admin: color: "&#FF0000" display-name: "Admin"

member: color: "&f" display-name: "Member"

All rank colors must support full hex.

---

  1. TEAM INVITE

Command:

/team invite <player>

Only Owner/Admin.

Target receives:

โ”Œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ” โ”‚ TEAM INVITE โ”‚ โ”‚ โ”‚ โ”‚ PlayerName invited you to join โ”‚ โ”‚ TeamName โ”‚ โ”‚ โ”‚ โ”‚ [ Accept ] [ Decline ] โ”‚ โ””โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”˜

Configuration:

invites: expiration: 60s

Rules:

  • Target cannot already be in a team
  • Team cannot be full
  • Invitation expires
  • Duplicate active invitation prevented

---

  1. TEAM KICK

Command:

/team kick <player>

Confirmation:

โ”Œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ” โ”‚ KICK MEMBER โ”‚ โ”‚ โ”‚ โ”‚ Kick PlayerName from TeamName? โ”‚ โ”‚ โ”‚ โ”‚ [ Confirm ] [ Cancel ] โ”‚ โ””โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”˜

Owner cannot be kicked.

Admin cannot kick Owner.

---

  1. TEAM PROMOTE

Command:

/team promote <player>

Member โ†’ Admin.

Confirmation required.

---

  1. TEAM DEMOTE

Command:

/team demote <player>

Admin โ†’ Member.

Confirmation required.

Owner cannot be demoted.

---

  1. TEAM DISBAND

Command:

/team disband

Owner only.

Show strong confirmation:

โ”Œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ” โ”‚ DISBAND TEAM โ”‚ โ”‚ โ”‚ โ”‚ This will permanently delete: โ”‚ โ”‚ โ”‚ โ”‚ Members โ”‚ โ”‚ Homes โ”‚ โ”‚ Warps โ”‚ โ”‚ Ender Chest โ”‚ โ”‚ Team Statistics โ”‚ โ”‚ โ”‚ โ”‚ [ CONFIRM DISBAND ] โ”‚ โ”‚ [ Cancel ] โ”‚ โ””โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”˜

After confirmation:

  • Delete team
  • Remove members
  • Delete homes
  • Delete warps
  • Delete Ender Chest
  • Delete progression
  • Delete cooldown data
  • Save changes

---

  1. OWNER TRANSFER

Command:

/team transfer <player>

Owner only.

Confirmation:

โ”Œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ” โ”‚ TRANSFER OWNERSHIP โ”‚ โ”‚ โ”‚ โ”‚ Transfer ownership to PlayerName? โ”‚ โ”‚ โ”‚ โ”‚ You will become an Admin. โ”‚ โ”‚ โ”‚ โ”‚ [ Confirm ] [ Cancel ] โ”‚ โ””โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”˜

After confirmation:

Old Owner โ†’ Admin New Owner โ†’ Owner

---

  1. TEAM LEVEL SYSTEM

Initially 3 levels.

team-levels: 1: required-kills: 0 homes: 3 warps: 3

2: required-kills: 100 homes: 6 warps: 6

3: required-kills: 300 homes: 10 warps: 10

Everything must be configurable.

---

  1. TEAM KILL PROGRESSION

Team kills increase when a team member legitimately kills a player outside their team.

Example:

Team Alpha member kills PlayerX โ†’ +1 Team Kill

Prevent continuous farming of the same player.

Configuration:

kill-progression: enabled: true same-victim-cooldown: 10m

Track cooldown using:

Team UUID + Victim UUID

Example:

Team Alpha kills PlayerX โ†’ +1

Team Alpha kills PlayerX again within 10 minutes โ†’ +0

After cooldown โ†’ PlayerX can contribute again

Different victims are unaffected.

Do not count:

  • Self kills
  • Team-member kills
  • Non-player entities
  • Duplicate death events
  • Invalid deaths

Persist progression.

---

  1. LEVEL-UP

When a team levels up:

โœจ TEAM LEVEL UP!

Team Alpha has reached Team Level 2!

๐Ÿ  6 Homes unlocked. โš‘ 6 Warps unlocked.

Level 3:

โœจ TEAM LEVEL UP!

Team Alpha has reached Team Level 3!

๐Ÿ  All 10 Homes unlocked. โš‘ All 10 Warps unlocked.

Messages must be configurable.

---

  1. TEAM PROGRESS BAR

Display:

Team Level: 2

โ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–‘โ–‘โ–‘โ–‘ 184 / 300 Team Kills

Use configurable progress-bar characters and colors.

---

  1. PLACEHOLDERAPI

Implement PlaceholderAPI integration if PlaceholderAPI is installed.

Expansion identifier:

axoteams

Required placeholders:

%axoteams_name% %axoteams_kills% %axoteams_member_team_total% %axoteams_member_team_online% %axoteams_team_owner%

AxoTeams must still work without PlaceholderAPI.

PlaceholderAPI should be an optional/soft dependency.

---

  1. "%axoteams_name%"

Returns the player's team name.

With team:

Phoenix

Without team:

N/A

---

  1. "%axoteams_kills%"

Returns the player's team's total kills.

Example:

Team Phoenix = 284 kills

%axoteams_kills% โ†’ 284

No team:

0

This placeholder must return a numeric value.

---

  1. AJLEADERBOARDS SUPPORT

"%axoteams_kills%" must be fully compatible with AJLeaderboards.

It must expose the value as a proper numeric statistic.

AJLeaderboards must be able to:

  • Read team kills
  • Sort by team kills
  • Rank highest team kill totals
  • Refresh when team kills change

Example:

#1 PlayerA 1248 #2 PlayerB 982 #3 PlayerC 741

If three players are members of a team with 500 kills:

PlayerA โ†’ 500 PlayerB โ†’ 500 PlayerC โ†’ 500

Players without teams:

0

Do not return "N/A" for the leaderboard statistic.

Update the statistic immediately after valid team kills.

Do not require a restart.

---

  1. "%axoteams_member_team_total%"

Returns total members in the player's team.

Example:

Team Phoenix = 12 members

%axoteams_member_team_total% โ†’ 12

No team:

0

---

  1. "%axoteams_member_team_online%"

Returns currently online team members.

Example:

Team Phoenix Total = 12 Online = 7

Returns:

7

No team:

0

---

  1. "%axoteams_team_owner%"

Returns current Owner username.

Example:

Team Phoenix Owner = DevSolentz

Returns:

DevSolentz

Owner does not need to be online.

No team:

N/A

---

  1. PLACEHOLDER SUMMARY

%axoteams_name%

Team name or "N/A".

%axoteams_kills%

Team kills or "0".

%axoteams_member_team_total%

Total team members or "0".

%axoteams_member_team_online%

Online team members or "0".

%axoteams_team_owner%

Owner username or "N/A".

---

  1. FULL HEX COLOR SUPPORT

This is a mandatory requirement for every Dialog.

Support:

&#RRGGBB

Example:

&#00B7FF&lAXO TEAMS

Also support all legacy colors:

&0 &1 &2 &3 &4 &5 &6 &7 &8 &9 &a &b &c &d &e &f

Formatting:

&l &o &n &m &k &r

Hex colors must work in:

  • Dialog titles
  • Dialog descriptions
  • Labels
  • Buttons
  • Button descriptions
  • Team names
  • Rank names
  • Member names
  • Home names
  • Warp names
  • Progress bars
  • Status messages
  • Confirmation Dialogs
  • Error messages
  • Back buttons

Do not strip hex colors.

Create a centralized:

ColorUtil.parse(String text)

or equivalent.

---

  1. PER-CHARACTER HEX GRADIENT SUPPORT

Support different hex colors on individual characters.

Example:

&#00B7FF&lA&#19C0FF&lX&#32C9FF&lO &#4BD2FF&lT&#64DBFF&lE&#7DE4FF&lA&#96EDFF&lM&#AFF6FF&lS

Every character's color must remain intact.

Do not collapse gradients into a single color.

---

  1. SPRITE SUPPORT

All Dialogs must support configurable Minecraft/ItemsAdder-style sprites.

Examples:

<sprite:"minecraft:items":item/spyglass>

<sprite:"minecraft:items":item/ender_chest>

<sprite:"minecraft:items":item/compass>

<sprite:"minecraft:items":item/iron_sword>

<sprite:"minecraft:items":item/lead>

Player heads:

<head:%player%>

The sprite syntax must not simply appear as literal text.

It must be parsed into the appropriate Adventure Component representation.

---

  1. SPRITES INSIDE DIALOG BUTTONS

Sprites must work inside buttons wherever supported by the Paper Dialog API.

Examples:

<sprite:"minecraft:items":item/spyglass> &#00B7FF&lCreate Team

<sprite:"minecraft:items":item/ender_chest> &#00B7FF&lEnder Chest

<sprite:"minecraft:items":item/iron_sword> &#FF0000&lTeam PvP

<sprite:"minecraft:items":item/compass> &#00B7FF&lTeam Home

<sprite:"minecraft:items":item/lead> &#9B59FF&lTeam Warps

---

  1. CENTRALIZED SPRITE PARSER

Create a reusable:

SpriteUtil

or equivalent.

It must recognize:

<sprite:"namespace":path>

and convert it into the correct Adventure/Paper representation.

Support arbitrary namespaces and paths.

Do not hardcode only AxoTeams' default sprites.

---

  1. PLAYER HEAD PARSER

Support:

<head:%player%>

Example:

<head:DevSolentz> &#00B7FFDevSolentz

Resolve the correct player's head dynamically.

If unavailable, use:

sprites: fallback-head: '<sprite:"minecraft:items":item/player_head>'

Do not throw an exception if a head cannot be resolved.

---

  1. CONFIGURABLE DIALOG SPRITES

Add:

dialog-sprites: create-team: '<sprite:"minecraft:items":item/spyglass>' ender-chest: '<sprite:"minecraft:items":item/ender_chest>' team-pvp: '<sprite:"minecraft:items":item/iron_sword>' team-home: '<sprite:"minecraft:items":item/compass>' team-warps: '<sprite:"minecraft:items":item/lead>' team-members: '<sprite:"minecraft:items":item/player_head>' confirm: '<sprite:"minecraft:items":item/emerald>' cancel: '<sprite:"minecraft:items":item/barrier>' back: '<sprite:"minecraft:items":item/arrow>'

Every sprite must be replaceable without modifying Java code.

---

  1. CONFIGURABLE DIALOG COLORS

Add:

dialog-colors: primary: '&#00B7FF' secondary: '&#9B59FF' success: '&#00FF88' warning: '&#FFAA00' danger: '&#FF0000' neutral: '&f' muted: '&7'

These values must work throughout Dialog UI.

---

  1. COMPONENT RENDERING PIPELINE

Every configurable Dialog string must go through a centralized rendering system.

Pipeline:

YAML String โ†“ Legacy / Hex Color Parser โ†“ Sprite Parser โ†“ Adventure Component โ†“ Paper Dialog API

For example:

<sprite:"minecraft:items":item/spyglass> &#00B7FF&lCreate Team

must preserve both:

  • Sprite
  • Hex color
  • Bold formatting

---

  1. NO FEATURE-SPECIFIC PARSERS

Do not create one sprite parser for Create Team and another for Team Members.

Every Dialog must use the same component renderer.

Applies to:

  • Create Team
  • Main Team
  • Team Members
  • Team Homes
  • Team Warps
  • Team Invites
  • Confirmation
  • Disband
  • Transfer
  • Kick
  • Promote
  • Demote
  • Future Dialogs

---

  1. INVALID COLOR / SPRITE HANDLING

Malformed values must never crash the plugin.

Example:

&#GGGGGG

If invalid:

  • Log useful warning
  • Fall back safely
  • Continue rendering

If invalid sprite:

  • Log warning
  • Use fallback
  • Continue rendering

Never throw a server-breaking exception because of configuration formatting.

---

  1. MESSAGES.YML

All player-facing chat messages must be configurable.

Example:

prefix: "&#00B7FF&lAXO TEAMS &8ยป &r"

team-created: "%prefix%&fTeam &#00B7FF%team% &fhas been created." already-in-team: "%prefix%&cYou are already in a team." not-in-team: "%prefix%&cYou are not in a team." team-not-found: "%prefix%&cThat team does not exist." player-not-found: "%prefix%&cThat player could not be found." no-permission: "%prefix%&cYou don't have permission to do that." invalid-team-name: "%prefix%&cThat team name is invalid." team-name-taken: "%prefix%&cThat team name is already taken."

Support:

& &#RRGGBB

Do not hardcode player-facing messages in Java.

---

  1. PERMISSIONS

Implement:

axoteams.team axoteams.create axoteams.invite axoteams.kick axoteams.promote axoteams.demote axoteams.transfer axoteams.disband axoteams.home axoteams.home.manage axoteams.warp axoteams.warp.manage axoteams.enderchest axoteams.pvp

Team ranks must still be enforced internally.

Having a server permission must not automatically make someone Owner/Admin of a specific team.

---

  1. COMMAND STRUCTURE

Implement:

/team /team create <name>

/team invite <player> /team kick <player> /team promote <player> /team demote <player> /team transfer <player> /team disband

/team home /team home set <slot> /team home delete <slot> /team home teleport <slot>

/team warp /team warp create <name> /team warp delete <name> /team warp <name>

---

  1. TAB COMPLETION

Provide intelligent completion.

Player arguments:

  • Online players
  • Only valid targets

Home arguments:

1 2 3 ...

Only unlocked slots where appropriate.

Warp arguments:

  • Existing team warps

Do not suggest invalid options.

---

  1. REUSABLE CONFIRMATION SYSTEM

Create:

ConfirmationDialog

with:

title description confirmText cancelText confirmAction cancelAction

Use it for:

  • Kick
  • Promote
  • Demote
  • Disband
  • Transfer
  • Delete Home
  • Replace Home
  • Delete Warp
  • Replace Warp
  • Future destructive actions

Do not duplicate confirmation code.

---

  1. TEAM DATA MODEL

Each team should contain:

team: uuid: name: owner: level: 1 kills: 0 pvp: false

members: uuid: name: rank: MEMBER

homes: 1: world: x: y: z: yaw: pitch:

warps:

Base: world: x: y: z: yaw: pitch:

ender-chest: contents: []

Use UUIDs internally.

Do not rely only on player names.

---

  1. STORAGE

Use YAML initially.

Directory:

plugins/AxoTeams/

Files:

config.yml messages.yml teams/<team-uuid>.yml

Each team gets its own YAML file.

Do not store all teams in one giant YAML file.

Create a storage abstraction:

TeamStorage

with:

YamlTeamStorage

so SQLite/MySQL can be added later.

---

  1. CONFIGURATION

Create a professional "config.yml" containing at minimum:

team-name: min-length: 3 max-length: 16 allowed-pattern: "^[a-zA-Z0-9_]+$"

team: max-members: 20

team-pvp: default: false

invites: expiration: 60s

kill-progression: enabled: true same-victim-cooldown: 10m

team-ranks: owner: color: "&#00B7FF" display-name: "Owner"

admin: color: "&#FF0000" display-name: "Admin"

member: color: "&f" display-name: "Member"

team-levels: 1: required-kills: 0 homes: 3 warps: 3

2: required-kills: 100 homes: 6 warps: 6

3: required-kills: 300 homes: 10 warps: 10

dialog-colors: primary: '&#00B7FF' secondary: '&#9B59FF' success: '&#00FF88' warning: '&#FFAA00' danger: '&#FF0000' neutral: '&f' muted: '&7'

dialog-sprites: create-team: '<sprite:"minecraft:items":item/spyglass>' ender-chest: '<sprite:"minecraft:items":item/ender_chest>' team-pvp: '<sprite:"minecraft:items":item/iron_sword>' team-home: '<sprite:"minecraft:items":item/compass>' team-warps: '<sprite:"minecraft:items":item/lead>' team-members: '<sprite:"minecraft:items":item/player_head>' confirm: '<sprite:"minecraft:items":item/emerald>' cancel: '<sprite:"minecraft:items":item/barrier>' back: '<sprite:"minecraft:items":item/arrow>'

sprites: fallback-head: '<sprite:"minecraft:items":item/player_head>'

---

  1. ARCHITECTURE

Use clean modular architecture:

dev.axoryn.axoteams โ”‚ โ”œโ”€โ”€ AxoTeamsPlugin โ”‚ โ”œโ”€โ”€ command โ”‚ โ”œโ”€โ”€ TeamCommand โ”‚ โ””โ”€โ”€ TeamTabCompleter โ”‚ โ”œโ”€โ”€ team โ”‚ โ”œโ”€โ”€ Team โ”‚ โ”œโ”€โ”€ TeamMember โ”‚ โ”œโ”€โ”€ TeamRank โ”‚ โ”œโ”€โ”€ TeamManager โ”‚ โ”œโ”€โ”€ TeamLevelManager โ”‚ โ””โ”€โ”€ TeamProgressionManager โ”‚ โ”œโ”€โ”€ storage โ”‚ โ”œโ”€โ”€ TeamStorage โ”‚ โ””โ”€โ”€ YamlTeamStorage โ”‚ โ”œโ”€โ”€ dialog โ”‚ โ”œโ”€โ”€ TeamCreateDialog โ”‚ โ”œโ”€โ”€ TeamMainDialog โ”‚ โ”œโ”€โ”€ TeamHomeDialog โ”‚ โ”œโ”€โ”€ TeamWarpDialog โ”‚ โ”œโ”€โ”€ TeamMemberDialog โ”‚ โ”œโ”€โ”€ TeamInviteDialog โ”‚ โ””โ”€โ”€ ConfirmationDialog โ”‚ โ”œโ”€โ”€ listener โ”‚ โ”œโ”€โ”€ TeamCombatListener โ”‚ โ”œโ”€โ”€ TeamDeathListener โ”‚ โ””โ”€โ”€ TeamPlayerListener โ”‚ โ”œโ”€โ”€ home โ”‚ โ””โ”€โ”€ TeamHomeManager โ”‚ โ”œโ”€โ”€ warp โ”‚ โ””โ”€โ”€ TeamWarpManager โ”‚ โ”œโ”€โ”€ inventory โ”‚ โ””โ”€โ”€ TeamEnderChestManager โ”‚ โ”œโ”€โ”€ placeholder โ”‚ โ””โ”€โ”€ AxoTeamsPlaceholderExpansion โ”‚ โ”œโ”€โ”€ leaderboard โ”‚ โ””โ”€โ”€ AxoTeamsKillStatistic โ”‚ โ”œโ”€โ”€ config โ”‚ โ””โ”€โ”€ ConfigManager โ”‚ โ””โ”€โ”€ util โ”œโ”€โ”€ ColorUtil โ”œโ”€โ”€ SpriteUtil โ”œโ”€โ”€ ComponentUtil โ”œโ”€โ”€ LocationUtil โ””โ”€โ”€ TextUtil

Do not create a single giant Java class.

---

  1. PERFORMANCE

The plugin must be optimized.

Requirements:

  • No unnecessary repeating tasks
  • No full-team scan on every event
  • UUID-based lookups
  • Cached active team data
  • Expired invite cleanup
  • Expired kill cooldown cleanup
  • Safe asynchronous saving where appropriate
  • Never access unsafe Bukkit APIs asynchronously
  • No memory leaks
  • Proper shutdown saving
  • Prevent duplicate event handling

---

  1. EDGE CASES

Handle:

  • Player disconnects during invite
  • Player disconnects while Dialog is open
  • Team disbanded while another player has Dialog open
  • Owner goes offline
  • Owner transfer
  • Admin attempts to kick Owner
  • Admin attempts to demote Owner
  • Player already belongs to another team
  • Team full
  • Team-name collision
  • Invalid location
  • Deleted world
  • Corrupt team file
  • Server restart
  • Duplicate death events
  • Same-victim farming
  • Locked home
  • Locked warp
  • Missing home
  • Missing warp
  • Offline owner
  • Offline members
  • Invalid sprite configuration
  • Invalid color configuration
  • Missing player head
  • Placeholder called for player with no team

Normal player mistakes must never produce ugly server-breaking exceptions.

---

  1. OWNER LEAVING

Owner going offline must NOT automatically transfer ownership.

Only explicit ownership transfer should change the Owner.

Do not delete a team because its Owner is offline.

---

  1. PLUGIN.YML

Generate a valid Paper plugin descriptor:

name: AxoTeams version: ${version} main: dev.axoryn.axoteams.AxoTeamsPlugin api-version: '1.21' author: DevSolentz description: Premium team management system with Paper Dialog UI.

Register:

/team

If PlaceholderAPI is optional, declare it as a soft dependency.

---

  1. BUILD SYSTEM

Use Gradle or Maven.

Target:

Java 21 Paper 1.21.11

Include:

README.md LICENSE build.gradle or pom.xml src/ config.yml messages.yml

The complete project must compile without errors.

---

  1. CODE QUALITY

The final source must contain:

  • No fake APIs
  • No pseudo-code
  • No TODO implementations for core features
  • No missing classes
  • No missing imports
  • No compilation errors
  • No duplicated systems
  • No hardcoded player-facing messages
  • No hardcoded progression values
  • No hardcoded rank colors
  • Proper null handling
  • Proper exception handling
  • Clean architecture
  • Maintainable code
  • Useful JavaDoc where appropriate

---

  1. FINAL DELIVERABLE

Deliver the complete AxoTeams source project.

It must run directly on:

Paper 1.21.11 Java 21

The final plugin must include:

/team Team Creation Dialog Team Main Dialog Team Ender Chest Team PvP 10 Team Homes 3 Homes at Level 1 6 Homes at Level 2 10 Homes at Level 3 10 Team Warps 3 Warps at Level 1 6 Warps at Level 2 10 Warps at Level 3 Team Members Dialog Dynamic Player Heads Owner/Admin/Member ranks Team Invites Kick Promote Demote Transfer Ownership Disband Team Levels Team Kill Progression Anti Kill Farming Persistent YAML Storage Confirmation Dialogs PlaceholderAPI integration AJLeaderboards-compatible team kills Full legacy colors Full &#RRGGBB hex colors Per-character hex gradients Minecraft/ItemsAdder-style sprites Dynamic player-head sprites Configurable Dialog sprites Configurable Dialog colors

Required placeholders:

%axoteams_name% %axoteams_kills% %axoteams_member_team_total% %axoteams_member_team_online% %axoteams_team_owner%

The Dialog system must preserve sprites + hex colors + formatting simultaneously through the Adventure Component โ†’ Paper Dialog rendering pipeline.

The finished result must be a fully functional premium production plugin, not a proof of concept.

Kodari AI
KodariSep 13 at 4:35 am 3
AxoTeams
Premium team management plugin for Paper 1.21.11 with native Dialog UI. Features team creation, persistent YAML storage, 10 configurable homes and warps with level-based unlocks, shared Ender Chest, Team PvP toggle, member management with Owner/Admin/Member ranks, invites, kick/promote/demote/transfer/disband commands, kill progression with anti-farming cooldowns, level-up system, PlaceholderAPI integration, AJLeaderboards-compatible kill statistics, full hex color and sprite support, and centralized component rendering pipeline.
  1. Build the Gradle/Paper project and configuration resources.

  2. Create the team domain, YAML storage, managers, commands, listeners, and PlaceholderAPI integration.

  3. Create the native Paper Dialog UI flow, shared rendering utilities, and confirmation actions.

  4. Add metadata, README, and license.

Implemented the AxoTeams project with:

  • Gradle Java 21 / Paper 1.21.11 setup

  • plugin.yml, config.yml, messages.yml

  • Team creation, ranks, invites, promotion, demotion, kicking, transfer, and disbanding

  • Per-team YAML persistence

  • Team homes and warps with level-based unlocks

  • Shared team Ender Chest

  • Team PvP toggle

  • Kill progression with anti-farming cooldowns

  • Team level progression

  • Paper Dialog UI flows

  • Configurable colors, sprites, and messages

  • PlaceholderAPI expansion

  • Team combat and death listeners

  • Tab completion

  • README and LICENSE

itzzmeclaire_

<sprite:"minecraft:items":item/amethyst_shard> aise type ka sprite minimessage ko supported kr our sare buttons ko black mt kr insteat &7 kr our homes dialog mein zane ke bad udhsr click karne se set hoga home and setted wale pe click karega toh tp hoga with 5 second cooldown in actionbar (configurable) and same with warps

Kodari AI
KodariSep 13 at 6:30 am 3
  1. MiniMessage sprites aur button colors ko existing dialog rendering mein update karna.

  2. Homes dialog mein un-set home par click se set, set home par click se 5-second configurable actionbar cooldown ke saath teleport karna.

  3. Warps dialog par wahi cooldown/actionbar behavior apply karna aur config/messages align karna.

  1. MiniMessage sprite support added, including tags like <sprite:"minecraft:items":item/amethyst_shard>.

  2. All dialog buttons now default to &7 instead of black.

  3. Unset home buttons set the home location when clicked; set homes teleport after a configurable 5-second actionbar countdown.

  4. Warps use the same teleport countdown behavior.

  5. Added configuration:

YAML
teleport:
  cooldown: 5s
  actionbar: '&eTeleporting in &f%seconds%&e seconds...'

The cooldown and actionbar text can now be changed in config.yml.

itzzmeclaire_

Sprtite plugin e suppirt kare aisa kr our sare dialogs buttons ka colour &7 kr our sabkuch configurable kr

Kodari AI
KodariSep 13 at 6:35 am 2
  1. Sprite/plugin rendering: tags aur resource-pack sprite format ko configurable banayunga.

  2. Dialog styling: har button ka default color &7 karunga, with per-dialog/config override.

  3. Existing home/warp teleport settings ko config-driven rakhkar messages, cooldown aur actionbar placeholders align karunga.

  • Sprite tags เค…เคฌ configurable เคนเฅˆเค‚, เคœเฅˆเคธเฅ‡:

    YAML
    dialog-sprites:
      amethyst: '<sprite:"minecraft:items":item/amethyst_shard>'
    

    เค‡เคจเฅเคนเฅ‡เค‚ dialogs เคฎเฅ‡เค‚ use เค•เคฟเคฏเคพ เคœเคพ เคธเค•เคคเคพ เคนเฅˆเฅค

  • เคธเคญเฅ€ dialog buttons เค•เคพ default color เค…เคฌ configurable &7 เคนเฅˆเฅค

  • Button tooltip color เค”เคฐ width เคญเฅ€ configurable เคนเฅˆเค‚:

    YAML
    dialog-buttons:
      color: '&7'
      tooltip-color: '&7'
      width: 220
    
  • Existing teleport cooldown เค”เคฐ actionbar เคญเฅ€ config เคธเฅ‡ เคจเคฟเคฏเค‚เคคเฅเคฐเคฟเคค เคนเฅˆเค‚เฅค

  • Button labels เคธเฅ‡ hardcoded &a, &c, &e, &f colors เคนเคŸเคพเค•เคฐ เคธเคญเฅ€ buttons เค•เฅ‹ configured default color เคชเคฐ เค•เคฐ เคฆเคฟเคฏเคพ เค—เคฏเคพ เคนเฅˆเฅค

  • Sprite rendering Paper/MiniMessage syntax เค•เฅ‡ เคธเคพเคฅ compatible เคนเฅˆ; เค•เคฟเคธเฅ€ external Sprite plugin dependency เค•เฅ€ เค†เคตเคถเฅเคฏเค•เคคเคพ เคจเคนเฅ€เค‚ เคนเฅˆเฅค

Kodari can make mistakes. Review important code before using.
Files
src
build.gradle
LICENSE
README.md
settings.gradle
Code
24 1,102
src/main/java/dev/axoryn/axoteams/AxoTeamsPlugin.java
package dev.axoryn.axoteams;

import dev.axoryn.axoteams.command.TeamCommand;
import dev.axoryn.axoteams.config.ConfigManager;
import dev.axoryn.axoteams.dialog.DialogService;
import dev.axoryn.axoteams.listener.TeamCombatListener;
import dev.axoryn.axoteams.listener.TeamDeathListener;
import dev.axoryn.axoteams.placeholder.AxoTeamsPlaceholderExpansion;
import dev.axoryn.axoteams.storage.TeamStorage;
import dev.axoryn.axoteams.storage.YamlTeamStorage;
import dev.axoryn.axoteams.team.TeamManager;
import org.bukkit.Bukkit;
import org.bukkit.plugin.java.JavaPlugin;

public final class AxoTeamsPlugin extends JavaPlugin {
    private ConfigManager configManager;
    private TeamStorage storage;
    private TeamManager teamManager;
    private DialogService dialogService;

    @Override
    public void onEnable() {
        saveDefaultConfig();
        configManager = new ConfigManager(this);
        configManager.saveMessages();
        storage = new YamlTeamStorage(this);
        teamManager = new TeamManager(this, storage, configManager);
        teamManager.load();
        dialogService = new DialogService(this, teamManager, configManager);
        TeamCommand command = new TeamCommand(this, teamManager, dialogService, configManager);
        getCommand("team").setExecutor(command);
        getCommand("team").setTabCompleter(command);
        Bukkit.getPluginManager().registerEvents(dialogService, this);
        Bukkit.getPluginManager().registerEvents(new TeamCombatListener(teamManager), this);
        Bukkit.getPluginManager().registerEvents(new TeamDeathListener(teamManager, configManager), this);
        if (Bukkit.getPluginManager().isPluginEnabled("PlaceholderAPI")) {
            new AxoTeamsPlaceholderExpansion(this, teamManager).register();
        }
    }

    @Override
    public void onDisable() {
        if (teamManager != null) teamManager.saveAll();
    }

    public TeamManager teams() { return teamManager; }
    public ConfigManager cfg() { return configManager; }
}