--- 📎 Attached 1 file(s):
File: aspectsmps3.txt
prompt = r"""ASPECT SMP SEASON 3 — COMPLETE PLUGIN DEVELOPMENT PROMPT Instructions for Kodari
Build a complete, working Minecraft server plugin for Aspect SMP Season 3. Do not only create a demo, mockup, or partial implementation. Implement every feature below, connect all commands and GUIs to the real game logic, and test that the features work together.
IMPORTANT DEVELOPMENT RULES
First inspect the existing project and identify its Minecraft server version, Java version, build system, and installed APIs. Keep compatibility with the project's actual target. If these details are missing, ask me before choosing versions or dependencies.
Use clean, maintainable code and split features into sensible classes/managers (aspects, abilities, cooldowns, lives, recipes, GUI, commands, persistence, effects).
Every command, ability, passive, recipe, GUI button, life rule, and unlock rule listed below must be implemented—not merely displayed.
Store player data persistently. Aspect, kills/unlocks, lives, trusted players, cooldown timestamps, and other required player state must survive server restarts, crashes, and stop/start cycles.
Make the plugin lightweight for a server with only 2 GB RAM. Avoid repeating tasks for every player when one shared task will work. Do not spam the console, especially for passive abilities. Log important errors clearly and provide useful admin feedback.
Add tab completion for every command and subcommand. Check permissions and validate all arguments. Give clear messages for invalid input, missing targets, insufficient permissions, cooldowns, and locked abilities.
Use the prefix §4§lAspect SMP§r §7» (dark red and bold “Aspect SMP” prefix) for plugin messages. Keep colours consistent with each Aspect.
Add appropriate particles and sound effects to abilities, terrain attacks, crafting/revival actions, and the start sequence. Effects must be optimised and must not create excessive lag.
Do not silently omit a feature if an API/dependency is unavailable. Explain the limitation and offer the best compatible implementation. Do not claim a feature is complete unless it is implemented.
Make important values configurable where sensible, such as cooldowns, damage, effect durations, lives, and ability unlock thresholds.
ASPECTS AND ABILITIES
Every Aspect has a name, colour theme, icon/texture, default item, passive (if specified), Ability 1, Ability 2, and Terrain Attack (only for Aspects that explicitly have one below). Use the listed dye as the default Aspect item. Give each Aspect its own identifiable icon in GUIs/action bars. Use custom resource-pack textures if the project supports them; otherwise provide a clear fallback icon and explain how to install the resource pack.
ELECTRIC ASPECT
Colour: Yellow. Default item: Yellow Dye. Icon: Thunderbolt.
Passive: While the weather is a thunderstorm, the owner receives Strength I.
Ability 1 — “Thunderbolt”: Strike the targeted enemy with 10 thunder/lightning strikes in one attack, dealing 19 total damage. Do not accidentally damage the owner. Validate the target and prevent unintended repeated damage beyond the stated total.
Ability 2 — “Speedy”: Strike the owner with a friendly visual lightning effect and give the owner Speed VII for 10 seconds. The lightning effect must not damage the owner.
Terrain Attack: Show every online player the yellow title “The Field Is Charged” and subtitle “Electric Terrain Are Now Stronger”. Give all Electric Aspect users within the defined affected area Strength II for 1 minute. If no radius was specified in the original design, make the radius configurable and document its default.
DARK ASPECT
Colour: Black. Default item: Black Dye. Icon: Dark Eye.
Passive: Strength I at night; Weakness I during the day.
Ability 1: Spawn a hollow, empty 10×10 obsidian enclosure around/near the target area. It lasts 20 seconds and then disappears. Track the exact blocks placed by this ability and restore them safely afterward; do not delete blocks that were already there or overwrite player-built blocks permanently. If a safe enclosure cannot be made at the target location, cancel with a message.
Ability 2: Apply Nausea II, Blindness II, and Slowness II for 7 seconds to players within 10 blocks of the owner, excluding the owner. Respect the trust system.
FIGHTING ASPECT
Colour: Red. Default item: Red Dye. Icon: Red Punch.
Passive: Permanent Strength I while this Aspect is active.
Ability 1: Give the owner Strength III for 5 seconds.
Ability 2: Dash the owner forward and launch enemies hit along the dash path away from the owner. Avoid damaging or launching the owner. Stop safely at walls and respect trusted players.
DRAGON ASPECT
Colour: Blue. Default item: Blue Dye. Icon: Blue Dragon.
Ability 1: Launch a visual projectile into the sky and cause meteors to fall onto the ground for 5 seconds. Meteors should have visible warning/effect particles and should not cause uncontrolled terrain damage. Make terrain damage configurable and default it to off.
Ability 2: Create a dark-blue circle of particles that launches players within 10 blocks away from the owner. Exclude the owner and trusted players.
ICE ASPECT
Colour: Light Blue. Default item: Light Blue Dye. Icon: Snowflake.
Ability 1: Shoot 3 ice spikes toward the targeted enemy, dealing 15 total damage. Prevent the three spikes from accidentally multiplying the intended damage unless that is explicitly configured.
Ability 2: Tell the owner: “Hit a player to freeze them”. Arm the ability, then freeze the next valid player the owner hits so the victim cannot move for 5 seconds. End the freeze automatically and safely. Do not freeze the owner or trusted players.
FAIRY ASPECT
Colour: Pink. Default item: Pink Dye. Icon: Pink Particles.
Ability 1: Heal the owner by 3 hearts (6 health points), without exceeding maximum health.
Ability 2: Charge for 3 seconds, then fire a beam toward the location/direction of the owner's crosshair and deal 32 damage to a valid target hit by the beam. Show charging and beam effects. Cancel if the owner is invalid/dead or the ability cannot be completed.
PSYCHIC ASPECT
Colour: Pink. Default item: Pink Dye. Icon: Pink Spiral.
Ability 1: Tell the owner: “Hit a player to control them”. Arm the ability; when the owner hits a valid player, apply a short, controlled effect that moves/steers the target toward the location the owner is looking at. Do not teleport the target through blocks or into unsafe locations. The original specification does not state a duration, so make it configurable and choose a sensible documented default.
Ability 2: Make players within 30 blocks glow. Do not make the owner a target of their own ability. Respect trust.
GRASS ASPECT
Colour: Lime. Default item: Lime Dye. Icon: Green Leaf/Clover.
Ability 1: Hit/knock an enemy back slightly and deal 17 damage.
Ability 2: Give the owner Strength II for 5 seconds.
Terrain Attack: Give all Grass Aspect players within 50 blocks Strength II for 30 seconds.
WATER ASPECT
Colour: Light Blue. Default item: Light Blue Dye. Icon: Water Drop.
Passive: Permanent Dolphin's Grace I. Also give Strength I while the owner is in water or when the weather is rainy.
Ability 1: Allow the owner to ride a generated water wave for 5 seconds. The wave disappears after 5 seconds. Clean up only blocks/entities/effects created by the ability; do not permanently destroy existing builds.
Ability 2 — “Rain Dance”: Change the world weather to rain and give all Water Aspect users Strength I. Make the affected worlds and duration configurable; document the default duration if one is required by the API.
COSMIC ASPECT
Colour: Black. Default item: Black Dye. Icon: Space.
Passive: None.
Ability 1: Pull the enemy toward the owner, but only if the enemy is in the owner's crosshair/target line of sight. Do not pull the owner or trusted players.
Ability 2: Create a circular particle shield around the owner that knocks enemies away. Exclude the owner and trusted players.
FIRE ASPECT
Colour: Orange. Default item: Orange Dye. Icon: Orange Fire.
Passive: Gain Strength while in the Nether and Weakness while standing in water. Use configurable effect levels; default to Strength I and Weakness I if levels were not otherwise specified.
Ability 1: Create a circle of orange particles and burn players within 10 blocks, excluding the owner and trusted players.
Ability 2: Shoot a fireball toward the direction of the owner's crosshair, dealing 19 damage to a valid target. Prevent unintended fire spread and terrain damage by default.
TITAN ASPECT
Colour: Brown. Default item: Brown Dye. Icon: Large Foot.
Ability 1: Set the owner's scale/size to 0.4 for 10 seconds, then restore their original scale. Use a compatible scale API if the server supports one; if it does not, explain the dependency or fallback needed instead of pretending the feature works.
Ability 2: Tell the owner: “Hit a player to Giant Curse them”. Arm the ability; when the owner hits a valid player, set the victim's scale/size to 3.0. Since the original duration is not specified, make the effect duration configurable and document its default. Restore the victim's previous scale when the effect expires or when required by the plugin's cleanup logic.
AIR ASPECT
Colour: White. Default item: White Dye. Icon: Wind.
Ability 1: Dash the owner forward 20 blocks, stopping safely if a wall or unsafe destination is encountered.
Ability 2: Spawn a tornado that pulls players within 20 blocks into the tornado, spins/lifts them upward, and throws them outward/upward. Avoid trapping players indefinitely and exclude the owner and trusted players.
GHOST ASPECT
Colour: Purple. Default item: Purple Dye. Icon: Ghost.
Ability 1: Play a dragon sound and apply Slowness IV to players within 20 blocks for 10 seconds. Exclude the owner and trusted players.
Ability 2: Tell the owner: “Hit a player to make a bond with them”. Arm the ability; when the owner hits a valid player, bond the two players. If the Aspect owner dies while the bond is active, the bonded player also dies. Prevent recursive death handling, clear expired/invalid bonds safely, and persist bond data if bonds are meant to survive restarts. If the bond duration is not specified, make it configurable and document its default.
STEEL ASPECT
Colour: Gray. Default item: Gray Dye. Icon: Steel.
Ability 1: Tell the owner: “Hit a player to steal a random item from their inventory”. Arm the ability; when the owner hits a valid player, select one random non-empty inventory slot and transfer that item stack to the owner. Do not delete items if the owner cannot carry them; drop leftovers safely or cancel with a clear message. Exclude trusted players.
Ability 2: Give the owner Resistance II for 20 seconds.
ABILITY UNLOCKS AND COOLDOWNS
All abilities are locked by default.
Ability 1 unlocks after the player reaches 5 kills.
Ability 2 unlocks after the player reaches 10 kills. This is the intended rule; use it consistently wherever unlocks are checked.
Terrain Attacks unlock when both regular abilities are unlocked (10 kills), unless this threshold is changed in the config.
Ability 1 cooldown: 5 minutes.
Ability 2 cooldown: 5 minutes.
Terrain Attack cooldown: 10 minutes.
Cooldowns must be saved as persistent timestamps and must not reset if the player disconnects, rejoins, or the server restarts.
Display clear locked/cooldown/ready status. Do not let commands or alternate activation paths bypass unlocks or cooldowns.
Make sure ability activation checks: player has an Aspect, ability is unlocked, cooldown is finished, player is alive, and the target is valid. Also check trust rules.
Abilities activated by a hit must arm correctly, expire after a configurable timeout, and be consumed only by a valid hit.
LIVES SYSTEM
Starting lives: 5 per player.
Maximum lives: 10.
Death penalty: lose 1 life.
When a player kills another player, the killer receives the victim's lost life, subject to the configured maximum of 10. Do not create lives from nothing if the killer is already at max; define a safe, documented rule for the excess life.
At 0 lives, put the player in spectator mode and keep them in spectator mode; they must not be able to move around in the void. Do not leave them falling endlessly. Make the spectator spawn/holding location configurable.
“Banned after: 0 lives” means the player is eliminated at zero lives. Do not permanently ban them automatically unless the config explicitly enables bans; the base behaviour should be spectator/elimination.
/aspect revive <player> revives a player with 3 lives.
/revive must require the player to be holding a Revival Beacon. It opens a GUI listing eliminated/banned players by head. Clicking a player's head revives that player with 3 lives, consumes one Revival Beacon, closes the GUI, and gives confirmation messages. Validate the item and player state again when the GUI click occurs.
Prevent duplicate life loss/gain from one death event. Correctly handle PvP kills, non-player deaths, void deaths, disconnects, and server restarts.
Persist life values and elimination state.
CUSTOM ITEMS AND RECIPES Use exact shaped recipes with the ingredient counts below. If an ingredient layout is not specified, choose a sensible shaped layout and document it. Avoid recipe collisions and provide clear recipe names/keys.
Aspect Crown Template — craftable only 4 times per world/server lifetime in total:
4 Prismarine Shards
1 Heart of the Sea
4 Netherite Ingots Track the total number crafted persistently. Prevent crafting a fifth template even after restart. If crafting events can happen concurrently, protect the limit against duplicate crafting.
Aspect Crown — craftable only once in total:
4 Aspect Crown Templates
4 Netherite Blocks
1 Nether Star Track the total craft count persistently and prevent a second crown after restart.
Aspect Life — default item: Red Dye.
4 Red Dye
4 Ancient Debris
Centre slot empty. Implement the recipe in a valid 3×3 shaped grid, following this ingredient requirement and documenting the chosen pattern. Do not silently add another ingredient.
Revival Beacon — default item: Beacon.
4 Aspect Lives
4 Diamonds
1 Heart of the Sea. Create a shaped recipe and ensure “Aspect Life” custom items can be distinguished from ordinary Red Dye using persistent item metadata, not just display name/lore.
CUSTOM ITEM HANDLING
Custom items must have persistent identifiers so renamed or similar-looking vanilla items cannot spoof them.
/aspect customitem give <player> <item name> gives the requested supported custom item.
/aspect withdraw removes the player's current Aspect and gives them that Aspect's default dye item in their inventory. If inventory is full, safely drop the item or provide another documented safe behaviour.
/aspect set <player> <aspectname> assigns the chosen Aspect and removes/replaces previous Aspect effects and state correctly.
/aspect reroll <player> assigns a random Aspect and removes the old Aspect's passive effects/state before applying the new one.
Reassigning or withdrawing an Aspect must clean up temporary effects, armed abilities, bonds, size changes, and any other Aspect-specific state belonging to the old Aspect.
Prevent duplicate active Aspects on one player unless the design explicitly permits it.
COMMANDS Implement all commands below with permissions, argument validation, clear messages, and tab completion.
Player commands:
/ability1 — use Ability 1 for the player's current Aspect.
/ability2 — use Ability 2 for the player's current Aspect.
/terrainattack — use the player's Aspect Terrain Attack if it has one and it is unlocked.
/aspect ability1 — same behaviour as /ability1.
/aspect ability2 — same behaviour as /ability2.
/aspect trust <playername> — trust a player. Aspect abilities cannot target that trusted player, and the owner cannot hit them while they remain trusted.
/aspect trust list — list trusted players.
/aspect untrust <playername> — remove a player from the trust list and allow normal PvP/Aspect targeting again.
/revive — use a held Revival Beacon and open the eliminated-player GUI.
Admin commands (permission-protected):
/aspect reroll <playername> — assign a random Aspect and clean up old Aspect state.
/aspect lives withdraw <number> — withdraw the specified number of lives from the executing player's own life balance, unless the sender has an explicit admin permission to target another player. Validate that the result cannot go below zero.
/aspect revive <playername> — revive an eliminated player with 3 lives.
/aspect customitem give <playername> <item name> — give a custom item.
/aspect set <playername> <aspectname> — assign a specific Aspect.
/aspect withdraw — remove the sender's Aspect and give its default item.
/aspect gui — open an Aspect information GUI showing every Aspect, its abilities, passive, terrain attack (if any), colours, and related custom items. Ordinary players must not be able to take display items. Only operators or authorized admins may take items, and only when explicitly allowed by the admin GUI mode.
/aspect reload — reload configuration safely without wiping player data, recipe limits, lives, unlocks, or cooldowns.
/aspect start — begin the SMP start sequence and assign every eligible player a random Aspect. Prevent accidental repeated starts or duplicate assignment unless an authorized force option is used.
GUI AND VISUAL PRESENTATION
Every plugin message starts with the red/bold Aspect SMP prefix described above.
At server start/SMP start, play a custom totem-pop-style animation using the SMP logo texture if a logo image/resource pack is supplied. Use that logo as the custom totem/animation icon where technically supported. If the image is not available in the project, request it or provide exact resource-pack placement/instructions; do not invent a claim that the supplied logo was embedded.
/aspect gui must be an information-only GUI for regular players. Clicking an Aspect shows its description, passive, Ability 1, Ability 2, Terrain Attack (where applicable), unlock requirements, and cooldowns. Prevent taking items from the GUI, shift-click duplication, number-key swapping, dragging, and other inventory exploits.
/revive GUI lists only eligible eliminated players and uses their player heads. Clicking a head attempts revival safely and consumes the beacon only on successful revival.
Add tasteful particles and sounds without causing excessive entity/task load.
Keep the GUI layout clear and consistent with each Aspect's colour.
ACTION BAR Update the action bar without spamming chat. Use the player's Aspect icon/name and lives/unlock/cooldown information.
When abilities are locked, show a format similar to: <Aspect Icon> <Aspect Name> Aspect | Ability 1: Locked 🔒 | Ability 2: Locked 🔒 | Aspectian Lives: <lives>
When unlocked, show: <Aspect Icon> <Aspect Name> Aspect | Ability 1: <Ready/Cooldown: time> | Ability 2: <Ready/Cooldown: time> | Lives: <lives>
Use the real current state. Show terrain-attack status somewhere suitable if possible. Avoid displaying “Ready” when the ability is locked or cooling down. If a player has no Aspect, show a clear neutral message.
PERSISTENCE AND RELIABILITY
Save data when important state changes and use safe shutdown saving. Prefer a reliable storage format suited to the project (for example, SQLite or carefully managed YAML/JSON). Do not block the main server thread with heavy file operations.
Persist: Aspect assignments, kills/unlocks, lives, eliminated status, trusted players, cooldown end timestamps, global recipe craft counts, and any temporary states that must survive a restart.
On startup, validate stored data and recover gracefully from malformed/missing files. Never wipe all player data just because one record is invalid.
Clean up temporary blocks, tasks, potion effects, entity references, and player-size changes when effects expire, players leave, an Aspect changes, or the plugin disables.
Prevent duplicate listeners, repeated scheduled tasks
What server platform/version and Java version should this target (for example, Paper 1.21.x with Java 21)? The attached requirements ask me to confirm those before choosing compatibility or dependencies.
Complete plugin?
What should the plugin do? Describe its main features, commands, and any permissions you want, and I’ll build it from scratch.
Missing required fills coming at compiling fix
I can build it from scratch, but I still need to know what the plugin should do. The initialization notes describe the workflow, not the plugin’s features—send its purpose, commands, and any permissions you want.
📄
pasted-code-1791700825682.txt
txt
169 lines
▶
prompt = r"""ASPECT SMP SEASON 3 — COMPLETE PLUGIN DEVELOPMENT PROMPT Instructions for Kodari
Build a complete, working Minecraft server plugin for Aspect SMP Season 3. Do not only create a demo, mockup, or partial implementation. Implement every feature below, connect all commands and GUIs to the real game logic, and test that the features work together.
IMPORTANT DEVELOPMENT RULES
First inspect the existing project and identify its Minecraft server version, Java version, build system, and installed APIs. Keep compatibility with the project's actual target. If these details are missing, ask me before choosing versions or dependencies.
Use clean, maintainable code and split features into sensible classes/managers (aspects, abilities, cooldowns, lives, recipes, GUI, commands, persistence, effects).
Every command, ability, passive, recipe, GUI button, life rule, and unlock rule listed below must be implemented—not merely displayed.
Store player data persistently. Aspect, kills/unlocks, lives, trusted players, cooldown timestamps, and other required player state must survive server restarts, crashes, and stop/start cycles.
Make the plugin lightweight for a server with only 2 GB RAM. Avoid repeating tasks for every player when one shared task will work. Do not spam the console, especially for passive abilities. Log important errors clearly and provide useful admin feedback.
Add tab completion for every command and subcommand. Check permissions and validate all arguments. Give clear messages for invalid input, missing targets, insufficient permissions, cooldowns, and locked abilities.
Use the prefix §4§lAspect SMP§r §7» (dark red and bold “Aspect SMP” prefix) for plugin messages. Keep colours consistent with each Aspect.
Add appropriate particles and sound effects to abilities, terrain attacks, crafting/revival actions, and the start sequence. Effects must be optimised and must not create excessive lag.
Do not silently omit a feature if an API/dependency is unavailable. Explain the limitation and offer the best compatible implementation. Do not claim a feature is complete unless it is implemented.
Make important values configurable where sensible, such as cooldowns, damage, effect durations, lives, and ability unlock thresholds.
ASPECTS AND ABILITIES
Every Aspect has a name, colour theme, icon/texture, default item, passive (if specified), Ability 1, Ability 2, and Terrain Attack (only for Aspects that explicitly have one below). Use the listed dye as the default Aspect item. Give each Aspect its own identifiable icon in GUIs/action bars. Use custom resource-pack textures if the project supports them; otherwise provide a clear fallback icon and explain how to install the resource pack.
ELECTRIC ASPECT
Colour: Yellow. Default item: Yellow Dye. Icon: Thunderbolt.
Passive: While the weather is a thunderstorm, the owner receives Strength I.
Ability 1 — “Thunderbolt”: Strike the targeted enemy with 10 thunder/lightning strikes in one attack, dealing 19 total damage. Do not accidentally damage the owner. Validate the target and prevent unintended repeated damage beyond the stated total.
Ability 2 — “Speedy”: Strike the owner with a friendly visual lightning effect and give the owner Speed VII for 10 seconds. The lightning effect must not damage the owner.
Terrain Attack: Show every online player the yellow title “The Field Is Charged” and subtitle “Electric Terrain Are Now Stronger”. Give all Electric Aspect users within the defined affected area Strength II for 1 minute. If no radius was specified in the original design, make the radius configurable and document its default.
DARK ASPECT
Colour: Black. Default item: Black Dye. Icon: Dark Eye.
Passive: Strength I at night; Weakness I during the day.
Ability 1: Spawn a hollow, empty 10×10 obsidian enclosure around/near the target area. It lasts 20 seconds and then disappears. Track the exact blocks placed by this ability and restore them safely afterward; do not delete blocks that were already there or overwrite player-built blocks permanently. If a safe enclosure cannot be made at the target location, cancel with a message.
Ability 2: Apply Nausea II, Blindness II, and Slowness II for 7 seconds to players within 10 blocks of the owner, excluding the owner. Respect the trust system.
FIGHTING ASPECT
Colour: Red. Default item: Red Dye. Icon: Red Punch.
Passive: Permanent Strength I while this Aspect is active.
Ability 1: Give the owner Strength III for 5 seconds.
Ability 2: Dash the owner forward and launch enemies hit along the dash path away from the owner. Avoid damaging or launching the owner. Stop safely at walls and respect trusted players.
DRAGON ASPECT
Colour: Blue. Default item: Blue Dye. Icon: Blue Dragon.
Ability 1: Launch a visual projectile into the sky and cause meteors to fall onto the ground for 5 seconds. Meteors should have visible warning/effect particles and should not cause uncontrolled terrain damage. Make terrain damage configurable and default it to off.
Ability 2: Create a dark-blue circle of particles that launches players within 10 blocks away from the owner. Exclude the owner and trusted players.
ICE ASPECT
Colour: Light Blue. Default item: Light Blue Dye. Icon: Snowflake.
Ability 1: Shoot 3 ice spikes toward the targeted enemy, dealing 15 total damage. Prevent the three spikes from accidentally multiplying the intended damage unless that is explicitly configured.
Ability 2: Tell the owner: “Hit a player to freeze them”. Arm the ability, then freeze the next valid player the owner hits so the victim cannot move for 5 seconds. End the freeze automatically and safely. Do not freeze the owner or trusted players.
FAIRY ASPECT
Colour: Pink. Default item: Pink Dye. Icon: Pink Particles.
Ability 1: Heal the owner by 3 hearts (6 health points), without exceeding maximum health.
Ability 2: Charge for 3 seconds, then fire a beam toward the location/direction of the owner's crosshair and deal 32 damage to a valid target hit by the beam. Show charging and beam effects. Cancel if the owner is invalid/dead or the ability cannot be completed.
PSYCHIC ASPECT
Colour: Pink. Default item: Pink Dye. Icon: Pink Spiral.
Ability 1: Tell the owner: “Hit a player to control them”. Arm the ability; when the owner hits a valid player, apply a short, controlled effect that moves/steers the target toward the location the owner is looking at. Do not teleport the target through blocks or into unsafe locations. The original specification does not state a duration, so make it configurable and choose a sensible documented default.
Ability 2: Make players within 30 blocks glow. Do not make the owner a target of their own ability. Respect trust.
GRASS ASPECT
Colour: Lime. Default item: Lime Dye. Icon: Green Leaf/Clover.
Ability 1: Hit/knock an enemy back slightly and deal 17 damage.
Ability 2: Give the owner Strength II for 5 seconds.
Terrain Attack: Give all Grass Aspect players within 50 blocks Strength II for 30 seconds.
WATER ASPECT
Colour: Light Blue. Default item: Light Blue Dye. Icon: Water Drop.
Passive: Permanent Dolphin's Grace I. Also give Strength I while the owner is in water or when the weather is rainy.
Ability 1: Allow the owner to ride a generated water wave for 5 seconds. The wave disappears after 5 seconds. Clean up only blocks/entities/effects created by the ability; do not permanently destroy existing builds.
Ability 2 — “Rain Dance”: Change the world weather to rain and give all Water Aspect users Strength I. Make the affected worlds and duration configurable; document the default duration if one is required by the API.
COSMIC ASPECT
Colour: Black. Default item: Black Dye. Icon: Space.
Passive: None.
Ability 1: Pull the enemy toward the owner, but only if the enemy is in the owner's crosshair/target line of sight. Do not pull the owner or trusted players.
Ability 2: Create a circular particle shield around the owner that knocks enemies away. Exclude the owner and trusted players.
FIRE ASPECT
Colour: Orange. Default item: Orange Dye. Icon: Orange Fire.
Passive: Gain Strength while in the Nether and Weakness while standing in water. Use configurable effect levels; default to Strength I and Weakness I if levels were not otherwise specified.
Ability 1: Create a circle of orange particles and burn players within 10 blocks, excluding the owner and trusted players.
Ability 2: Shoot a fireball toward the direction of the owner's crosshair, dealing 19 damage to a valid target. Prevent unintended fire spread and terrain damage by default.
TITAN ASPECT
Colour: Brown. Default item: Brown Dye. Icon: Large Foot.
Ability 1: Set the owner's scale/size to 0.4 for 10 seconds, then restore their original scale. Use a compatible scale API if the server supports one; if it does not, explain the dependency or fallback needed instead of pretending the feature works.
Ability 2: Tell the owner: “Hit a player to Giant Curse them”. Arm the ability; when the owner hits a valid player, set the victim's scale/size to 3.0. Since the original duration is not specified, make the effect duration configurable and document its default. Restore the victim's previous scale when the effect expires or when required by the plugin's cleanup logic.
AIR ASPECT
Colour: White. Default item: White Dye. Icon: Wind.
Ability 1: Dash the owner forward 20 blocks, stopping safely if a wall or unsafe destination is encountered.
Ability 2: Spawn a tornado that pulls players within 20 blocks into the tornado, spins/lifts them upward, and throws them outward/upward. Avoid trapping players indefinitely and exclude the owner and trusted players.
GHOST ASPECT
Colour: Purple. Default item: Purple Dye. Icon: Ghost.
Ability 1: Play a dragon sound and apply Slowness IV to players within 20 blocks for 10 seconds. Exclude the owner and trusted players.
Ability 2: Tell the owner: “Hit a player to make a bond with them”. Arm the ability; when the owner hits a valid player, bond the two players. If the Aspect owner dies while the bond is active, the bonded player also dies. Prevent recursive death handling, clear expired/invalid bonds safely, and persist bond data if bonds are meant to survive restarts. If the bond duration is not specified, make it configurable and document its default.
STEEL ASPECT
Colour: Gray. Default item: Gray Dye. Icon: Steel.
Ability 1: Tell the owner: “Hit a player to steal a random item from their inventory”. Arm the ability; when the owner hits a valid player, select one random non-empty inventory slot and transfer that item stack to the owner. Do not delete items if the owner cannot carry them; drop leftovers safely or cancel with a clear message. Exclude trusted players.
Ability 2: Give the owner Resistance II for 20 seconds.
ABILITY UNLOCKS AND COOLDOWNS
All abilities are locked by default.
Ability 1 unlocks after the player reaches 5 kills.
Ability 2 unlocks after the player reaches 10 kills. This is the intended rule; use it consistently wherever unlocks are checked.
Terrain Attacks unlock when both regular abilities are unlocked (10 kills), unless this threshold is changed in the config.
Ability 1 cooldown: 5 minutes.
Ability 2 cooldown: 5 minutes.
Terrain Attack cooldown: 10 minutes.
Cooldowns must be saved as persistent timestamps and must not reset if the player disconnects, rejoins, or the server restarts.
Display clear locked/cooldown/ready status. Do not let commands or alternate activation paths bypass unlocks or cooldowns.
Make sure ability activation checks: player has an Aspect, ability is unlocked, cooldown is finished, player is alive, and the target is valid. Also check trust rules.
Abilities activated by a hit must arm correctly, expire after a configurable timeout, and be consumed only by a valid hit.
LIVES SYSTEM
Starting lives: 5 per player.
Maximum lives: 10.
Death penalty: lose 1 life.
When a player kills another player, the killer receives the victim's lost life, subject to the configured maximum of 10. Do not create lives from nothing if the killer is already at max; define a safe, documented rule for the excess life.
At 0 lives, put the player in spectator mode and keep them in spectator mode; they must not be able to move around in the void. Do not leave them falling endlessly. Make the spectator spawn/holding location configurable.
“Banned after: 0 lives” means the player is eliminated at zero lives. Do not permanently ban them automatically unless the config explicitly enables bans; the base behaviour should be spectator/elimination.
/aspect revive revives a player with 3 lives.
/revive must require the player to be holding a Revival Beacon. It opens a GUI listing eliminated/banned players by head. Clicking a player's head revives that player with 3 lives, consumes one Revival Beacon, closes the GUI, and gives confirmation messages. Validate the item and player state again when the GUI click occurs.
Prevent duplicate life loss/gain from one death event. Correctly handle PvP kills, non-player deaths, void deaths, disconnects, and server restarts.
Persist life values and elimination state.
CUSTOM ITEMS AND RECIPES Use exact shaped recipes with the ingredient counts below. If an ingredient layout is not specified, choose a sensible shaped layout and document it. Avoid recipe collisions and provide clear recipe names/keys.
Aspect Crown Template — craftable only 4 times per world/server lifetime in total:
4 Prismarine Shards
1 Heart of the Sea
4 Netherite Ingots Track the total number crafted persistently. Prevent crafting a fifth template even after restart. If crafting events can happen concurrently, protect the limit against duplicate crafting.
Aspect Crown — craftable only once in total:
4 Aspect Crown Templates
4 Netherite Blocks
1 Nether Star Track the total craft count persistently and prevent a second crown after restart.
Aspect Life — default item: Red Dye.
4 Red Dye
4 Ancient Debris
Centre slot empty. Implement the recipe in a valid 3×3 shaped grid, following this ingredient requirement and documenting the chosen pattern. Do not silently add another ingredient.
Revival Beacon — default item: Beacon.
4 Aspect Lives
4 Diamonds
1 Heart of the Sea. Create a shaped recipe and ensure “Aspect Life” custom items can be distinguished from ordinary Red Dye using persistent item metadata, not just display name/lore.
CUSTOM ITEM HANDLING
Custom items must have persistent identifiers so renamed or similar-looking vanilla items cannot spoof them.
/aspect customitem give - gives the requested supported custom item.
/aspect withdraw removes the player's current Aspect and gives them that Aspect's default dye item in their inventory. If inventory is full, safely drop the item or provide another documented safe behaviour.
/aspect set
assigns the chosen Aspect and removes/replaces previous Aspect effects and state correctly.
/aspect reroll assigns a random Aspect and removes the old Aspect's passive effects/state before applying the new one.
Reassigning or withdrawing an Aspect must clean up temporary effects, armed abilities, bonds, size changes, and any other Aspect-specific state belonging to the old Aspect.
Prevent duplicate active Aspects on one player unless the design explicitly permits it.
COMMANDS Implement all commands below with permissions, argument validation, clear messages, and tab completion.
Player commands:
/ability1 — use Ability 1 for the player's current Aspect.
/ability2 — use Ability 2 for the player's current Aspect.
/terrainattack — use the player's Aspect Terrain Attack if it has one and it is unlocked.
/aspect ability1 — same behaviour as /ability1.
/aspect ability2 — same behaviour as /ability2.
/aspect trust — trust a player. Aspect abilities cannot target that trusted player, and the owner cannot hit them while they remain trusted.
/aspect trust list — list trusted players.
/aspect untrust — remove a player from the trust list and allow normal PvP/Aspect targeting again.
/revive — use a held Revival Beacon and open the eliminated-player GUI.
Admin commands (permission-protected):
/aspect reroll — assign a random Aspect and clean up old Aspect state.
/aspect lives withdraw — withdraw the specified number of lives from the executing player's own life balance, unless the sender has an explicit admin permission to target another player. Validate that the result cannot go below zero.
/aspect revive — revive an eliminated player with 3 lives.
/aspect customitem give - — give a custom item.
/aspect set
— assign a specific Aspect.
/aspect withdraw — remove the sender's Aspect and give its default item.
/aspect gui — open an Aspect information GUI showing every Aspect, its abilities, passive, terrain attack (if any), colours, and related custom items. Ordinary players must not be able to take display items. Only operators or authorized admins may take items, and only when explicitly allowed by the admin GUI mode.
/aspect reload — reload configuration safely without wiping player data, recipe limits, lives, unlocks, or cooldowns.
/aspect start — begin the SMP start sequence and assign every eligible player a random Aspect. Prevent accidental repeated starts or duplicate assignment unless an authorized force option is used.
GUI AND VISUAL PRESENTATION
Every plugin message starts with the red/bold Aspect SMP prefix described above.
At server start/SMP start, play a custom totem-pop-style animation using the SMP logo texture if a logo image/resource pack is supplied. Use that logo as the custom totem/animation icon where technically supported. If the image is not available in the project, request it or provide exact resource-pack placement/instructions; do not invent a claim that the supplied logo was embedded.
/aspect gui must be an information-only GUI for regular players. Clicking an Aspect shows its description, passive, Ability 1, Ability 2, Terrain Attack (where applicable), unlock requirements, and cooldowns. Prevent taking items from the GUI, shift-click duplication, number-key swapping, dragging, and other inventory exploits.
/revive GUI lists only eligible eliminated players and uses their player heads. Clicking a head attempts revival safely and consumes the beacon only on successful revival.
Add tasteful particles and sounds without causing excessive entity/task load.
Keep the GUI layout clear and consistent with each Aspect's colour.
ACTION BAR Update the action bar without spamming chat. Use the player's Aspect icon/name and lives/unlock/cooldown information.
When abilities are locked, show a format similar to: Aspect | Ability 1: Locked 🔒 | Ability 2: Locked 🔒 | Aspectian Lives:
When unlocked, show: Aspect | Ability 1: | Ability 2: | Lives:
Use the real current state. Show terrain-attack status somewhere suitable if possible. Avoid displaying “Ready” when the ability is locked or cooling down. If a player has no Aspect, show a clear neutral message.
PERSISTENCE AND RELIABILITY
Save data when important state changes and use safe shutdown saving. Prefer a reliable storage format suited to the project (for example, SQLite or carefully managed YAML/JSON). Do not block the main server thread with heavy file operations.
Persist: Aspect assignments, kills/unlocks, lives, eliminated status, trusted players, cooldown end timestamps, global recipe craft counts, and any temporary states that must survive a restart.
On startup, validate stored data and recover gracefully from malformed/missing files. Never wipe all player data just because one record is invalid.
Clean up temporary blocks, tasks, potion effects, entity references, and player-size changes when effects expire, players leave, an Aspect changes, or the plugin disables.
Prevent duplicate listeners, repeated scheduled tasks
I’ll inspect the project setup first, then implement the plugin against its actual server/API target and address the compilation issue at its source.
I need the target Minecraft server/API version and Java version before creating the plugin; the project has no build files to identify them. If you’re fixing a specific compilation failure, paste the compiler error too—the attached prompt describes requirements but doesn’t include one.
No files in this session