Raghda Elmasry

make sure it is perfect including the packs all the files and everything I don't want you to miss out on any detail please make sure it is perfect and perfect and perfect to the inch

📎 1 file 42,982 chars
📄
Master Prompt .txt
txt 1226 lines
▶
CRESCENT SMP — COMPLETE MASTER DEVELOPMENT PROMPT

Paper 1.21.11 • Skript • Custom Resource Pack • Made By CryVux

1. PROJECT REQUIREMENTS

Build a complete, functional Minecraft SMP ability system named Crescent, designed primarily for Paper 1.21.11, implemented using Skript files and a compatible custom resource pack.

Critical requirements

• Do NOT implement the main system as a Java plugin or Minecraft mod.
• Implement gameplay systems using multiple organized ".sk" files.
• Use compatible Skript syntax and documented addon features only.
• If an addon is necessary, specify its exact purpose, supported version, installation instructions and required configuration.
• Use SkBee only where needed for custom item models, item components or other supported features.
• Do not invent Skript expressions, events, particle types, model properties or commands.
• Do not leave placeholder commands, fake GUIs, empty functions, unfinished abilities or comments saying "implement later."
• Do not claim that something works unless it has been implemented and tested.
• Target Paper 1.21.11, not 1.21.1.
• Organize the project into separate files for each major system.
• Preserve all previous functionality when adding new features.
• Include complete source code, assets, configuration, resource pack and documentation.
• Include a separate Fabric 1.21.11 compatibility folder only if a genuinely supported implementation is possible. Skript itself does not run on Fabric, so never falsely claim that Paper scripts work directly on Fabric.

Every container name, inventory title or custom item container where appropriate must include:

"Made By CryVux"

On player join, display:

"Crescent Plugin - Made By CryVux"

Use this prefix:

"&8[&bCrescent&8] &f"

The resource pack must include these moon font symbols:

• "E001": Cracked Moon
• "E002": New Moon
• "E003": Half Moon
• "E004": Full Moon

2. PROJECT STRUCTURE

Organize the project into multiple Skript files, for example:

• "00_Crescent_Core.sk"
• "01_Crescent_Commands.sk"
• "02_Crescent_GUIs.sk"
• "03_Crescent_Main_Abilities.sk"
• "04_Crescent_Sidekicks.sk"
• "05_Crescent_Mythics.sk"
• "06_Crescent_Forbidden_Abilities.sk"
• "07_Crescent_Weapons.sk"
• "08_Crescent_Items_Rerollers.sk"
• "09_Crescent_VFX.sk"
• "10_Crescent_Awakening_Synergies.sk"
• "11_Crescent_Eclipse_God_Armor.sk"
• "12_Crescent_Event_Manager.sk"
• "13_Crescent_Spawn.sk"
• "14_Crescent_Anti_Exploit.sk"
• "15_Crescent_ResourcePack_Integration.sk"

File names may change if necessary, but the final project must have clear modular separation.

Ensure cross-file functions are available and do not define duplicate commands or conflicting event handlers.

Include:

• Complete source files.
• Resource pack source assets.
• Item model definitions.
• Custom textures and animations.
• Sound assets or documented vanilla sound mappings.
• Resource-pack installation instructions.
• Required Skript addon list.
• Configuration and permissions documentation.
• Feature checklist and testing instructions.

3. SHARD ECONOMY

Implement a persistent shard-based progression system.

• Killing another player awards the killer 1 shard.
• Dying to another player removes 1 shard.
• Players start with 3 shards by default, configurable to 5.
• Minimum shard balance: -3.
• Maximum shard balance: 5 unless configured otherwise.
• Players below 0 shards cannot activate Crescent abilities.
• Players at 0 or above can activate abilities.
• Prevent duplicate kill rewards from repeated death events.
• Handle suicide, environmental deaths, disconnects and non-player kills safely.
• Prevent repeated shard farming from the same target if anti-farming protection is enabled.
• Save shard balances persistently using player UUIDs.
• Do not lose balances after server restart.

Moon progression

Show the player's moon phase and shard balance in the action bar using actual resource-pack symbols rather than written phase names.

• Negative shards: Cracked Moon.
• 0 shards: New Moon.
• 3 shards: Half Moon.
• 5 shards: Full Moon.
• Intermediate balances must have clearly defined phase rules.
• Ability levels increase at configured moon-phase thresholds.
• Maximum normal ability level is III.
• Display equipped main ability and Sidekick in the action bar alongside the moon symbol and shard balance.
• Update the display without excessive server load.

4. ABILITY ACTIVATION AND EQUIPMENT

Players must have:

• One main ability slot.
• One Sidekick slot.
• One optional event-only Mythic main ability.

A Mythic occupies the main slot and replaces the normal main ability. Never allow both simultaneously.

Player commands

• "/mainability": Activate the equipped main ability.
• "/sideability": Activate the equipped Sidekick.
• "/abilityrunswap": Switch between command activation and action activation.
• "/abilitywithdraw": Withdraw or unequip an equipped ability, with validation and clear confirmation.
• "/crescentabilities": Preview all main abilities, levels, Sidekicks, Mythics, custom weapons and custom items.
• "/crescentabilites": Optional backward-compatible alias for the earlier spelling.

Activation modes

1. Command mode: "/mainability" and "/sideability".
2. Action mode: sneak + right-click for the main ability.
3. Action mode: sneak + swap-hand for the Sidekick.
4. Swap-hand activation must not permanently interfere with normal inventory behavior when activation is not applicable.
5. Cooldowns, shard restrictions, immobilization and protection-region restrictions must be checked before activation.
6. Failed activation must not consume a one-use item or start its cooldown.

5. COMMANDS AND ADMINISTRATION

Implement real commands with permission checks, useful tab completion where supported, validation and clear feedback.

Player commands

Command| Function
"/mainability"| Activate equipped main ability
"/sideability"| Activate equipped Sidekick
"/abilityrunswap"| Switch activation modes
"/abilitywithdraw"| Withdraw or unequip equipped ability
"/crescentabilities"| Preview Crescent content
"/crescentabilites"| Backward-compatible spelling alias
"/awakening"| Activate eligible Awakening
"/shards"| View shard balance
"/shards top"| View shard leaderboard
"/withdrawshards"| Withdraw physical shards
"/trust "| Trust a player
"/untrust "| Remove trust
"/eventmanger"| Open the Event Manager
"/eventmanager"| Optional corrected alias

Administration commands

Command| Function
"/crescentadmin"| Display admin commands and open admin controls
"/crescentset"| Set a player's shards, main ability or Sidekick
"/crescentadd"| Add shards to a player
"/crescentselector"| Open the admin item and ability selector
"/crescentskip"| Skip a specified cooldown
"/crescentgiveawakening "| Give the Awakening item
"/crescentreload"| Safely reload Crescent configuration
"/crescentdebug"| Enable or disable debugging
"/crescentgive"| Give a specified Crescent custom item
"/crescentremove"| Remove specified Crescent custom items
"/crescentsetshards"| Set a player's shard balance
"/crescentaddshards"| Add shards to a player
"/crescentreset"| Reset a player's Crescent progression
"/crescentlock"| Lock a player's abilities
"/crescentunlock"| Unlock a player's abilities
"/crescentsetability"| Assign a main ability
"/crescentsetlevel"| Set a player's ability level
"/crescentsetcooldown"| Modify a cooldown
"/crescentcheck"| Inspect a player's Crescent data
"/crescentbackup"| Create a persistent data backup
"/forbidden spawn"| Spawn a Forbidden Structure
"/crescentspawn place"| Set Crescent Spawn
"/crescentspawn reset"| Reset Crescent Spawn configuration
"/crescentspawn delete"| Delete configured Crescent Spawn

The following earlier commands must also be supported:

• "/shards give"
• "/shards remove"
• "/shards set"
• "/shardsgive"
• "/ability"
• "/rollability"
• "/abilitiespreview"
• "/abilitygui enable"
• "/abilitygui disable"
• "/abilitygui toggle"
• "/abilitylock"
• "/abilityunlock"

Where commands overlap, implement backward-compatible aliases rather than duplicate command handlers.

Permissions

Use permission nodes such as:

• "crescent.admin"
• "crescent.selector"
• "crescent.cooldown.skip"
• "crescent.awakening.give"
• "crescent.abilities.use"
• "crescent.sidekick.use"
• "crescent.event.admin"
• "crescent.spawn.admin"
• "crescent.forbidden.admin"
• "crescent.debug"

Never rely only on hidden GUI buttons or client-side checks for permissions.

All administrative commands must validate arguments, check permissions and provide clear success or failure messages.

"/crescentskip" must log administrative use and must never grant items or reset unrelated player data.

6. ADMIN SELECTOR AND GUIS

Create functional, paginated inventories with consistent titles and branding.

The selector must include:

1. Main abilities.
2. Sidekick abilities.
3. Mythic abilities.
4. Custom items and relics.
5. Custom weapons.
6. Shard-related items and rerollers.
7. Awakening and Eclipse God Set administration.

The original request specified five pages but listed six categories. Resolve this by using five primary pages plus an additional shard-items section and an Awakening/God Set administration section.

Requirements:

• Every item must have a meaningful name, lore, model and correct item metadata.
• Correct click handling for left-click, right-click, shift-click and number-key swaps.
• Prevent players from taking decorative GUI items.
• Prevent duplication through GUI clicks, dragging, double-click collection and inventory closing.
• Only authorized administrators can obtain selector rewards.
• Player preview GUIs must not grant items.
• All pages must have working navigation.
• No empty buttons or decorative controls that pretend to perform actions.
• Include clear error messages and confirmations.
• Include a working preview of every category.
• Every GUI must display "Made By CryVux".

7. MAIN ABILITIES

All ten main abilities have levels I, II and III, scaling according to moon phase.

Implement actual mechanics, cooldowns, effects, damage, sounds and particle effects.

1. Blood Moon

Steal health from enemies through ability activation.

• Level I: Restore 1 health point.
• Level II: Restore 2 health points.
• Level III: Restore 3 health points.

Healing must respect maximum health and not exceed it.

2. Moonstep

Dash in the direction the player is looking, leaving a lunar trail.

• Level I: Up to 4 blocks.
• Level II: Up to 6 blocks.
• Level III: Up to 8 blocks.

Allow intended phasing behavior only where safe and explicitly configured. Do not teleport into solid blocks, voids or protected regions.

3. Lunar Guard

Activate a temporary shield that reduces incoming damage.

• Level I: 15% damage reduction for 3 seconds.
• Level II: 25% damage reduction for 4 seconds.
• Level III: 35% damage reduction for 5 seconds.

Implement damage reduction through damage-event handling, not merely a visual effect.

4. Eclipse Burst

Release a lunar shockwave.

• Level I: 3-block radius.
• Level II: 4-block radius.
• Level III: 5-block radius.

Increase knockback slightly with higher levels.

5. Gravity Well

Create a central pull that slows and pulls nearby enemies.

• Level I: 3-block radius.
• Level II: 4-block radius.
• Level III: 5-block radius.

Do not permanently freeze players. Exclude the caster, trusted players and protected targets. Avoid griefing and region bypasses.

6. Lunar Surge

Temporarily increase damage.

• Level I: +5% for 4 seconds.
• Level II: +8% for 5 seconds.
• Level III: +10% for 6 seconds.

Apply the configured multiplier consistently through damage-event handling.

7. Shadow Veil

Temporarily conceal the caster.

• Level I: 2 seconds.
• Level II: 3 seconds.
• Level III: 4 seconds.

Include dark particles and sounds. Prevent the effect from creating permanent invisibility or exploitable state.

8. Crescent Nova

Charge lunar energy and release an area burst.

• Level I: 3-block radius, 2 hearts of base damage.
• Level II: 4-block radius, 3 hearts.
• Level III: 5-block radius, 4 hearts.

Respect armor, protection, trusted players and friendly-fire rules.

9. Crescent Slash

Launch a crescent-shaped ranged strike.

• Level I: 2 hearts of base damage, maximum range 8 blocks.
• Level II: 3 hearts, maximum range 10 blocks.
• Level III: 4 hearts, maximum range 12 blocks.

Use a visible traveling projectile or particle trail with collision detection. Damage must pass through the server's normal damage system. Do not shoot through solid blocks.

10. Lunar Impact

Leap and slam into the landing point.

• Level I: 2 hearts of base damage, 3-block radius, 35-second cooldown.
• Level II: 3 hearts, 4-block radius, 30-second cooldown.
• Level III: 4 hearts, 5-block radius, 25-second cooldown.
• Charge-up: 1 second.

Create a lunar shockwave and knockback. Respect protection regions and friendly-fire settings. Cancel safely if the landing point is invalid.

8. SIDEKICK ABILITIES

Sidekicks have their own separate slot, color theme and scrolls. They do not have levels.

1. Flashstep

• Dash up to 10 blocks.
• Cooldown: 18 seconds.
• Rapid movement burst, not teleportation through walls.
• Leave a lunar trail.
• Cannot activate while immobilized.

2. Shadow Exchange

• Swap positions with a targeted player within 12 blocks.
• Cooldown: 45 seconds.
• Require a clear line of sight and safe destination for both players.
• Show a warning particle effect before swapping.
• Respect trust settings, regions and friendly-targeting rules.

3. Moonflight

• Launch upward approximately 8 blocks.
• Apply Slow Falling for 4 seconds.
• Cooldown: 35 seconds.
• No permanent flight.

4. Gravity Leap

• Launch forward and upward.
• Travel approximately 12 blocks horizontally.
• Apply short Slow Falling.
• Cooldown: 25 seconds.
• Cancel if there is no safe landing area.

5. Rift Surge

• Activation: Sneak + swap-hand in action mode.
• Charge for 1 second.
• Dash up to 16 blocks.
• Stop at walls and require a safe landing.
• Cooldown: 30 seconds.
• Use a purple rift trail.

9. MYTHIC ABILITIES

Mythics are event-only. Players may receive them through the authorized selector or a documented event reward. They must not be included in normal rolls.

Mythics replace the normal main ability slot and have their own red-themed scroll textures and dramatic VFX.

1. Eclipse Annihilation

• Level I: 8 hearts of base damage, 8-block radius.
• Level II: 12 hearts, 12-block radius.
• Level III: 16 hearts, 16-block radius.
• Cooldown: 180 seconds.
• Charge-up before detonation.
• Summon a giant crimson eclipse, mark enemies and create a red particle ring.
• Level III eclipse is visible across the world through supported effects.

2. Void Sovereign

• Level I: 6 hearts of base damage, 8-block radius.
• Level II: 10 hearts, 12-block radius.
• Level III: 14 hearts, 16-block radius.
• Cooldown: 150 seconds.
• Pull enemies inward before a final blast.
• Use a black-purple vortex effect.

3. Celestial Judgment

• Level I: 3 strikes, 3 hearts each.
• Level II: 5 strikes, 4 hearts each.
• Level III: 7 strikes, 5 hearts each.
• Radius: 8, 12 and 16 blocks by level.
• Cooldown: 200 seconds.
• Mark each impact location visibly so enemies can escape.
• Create impact particle bursts.

4. Blood Emperor

• Level I: +40% damage, heal 25% of damage dealt, 8-second duration.
• Level II: +70%, heal 40%, 12-second duration.
• Level III: +100%, heal 50%, 15-second duration.
• Cooldown: 180 seconds.
• Use crimson armor particles and energy trails.
• Respect maximum health and absorption rules.

5. Last Rebirth

• Prevent one normally fatal hit during the active window.
• Active window: 5 seconds.
• Level I: Restore 4 hearts.
• Level II: Restore 8 hearts and knock back nearby enemies.
• Level III: Restore 10 hearts and deal 8 hearts of base damage within a 6-block radius.
• Cooldown: 300 seconds.
• Use a crimson reformation burst.
• Ensure fatal-hit interception is reliable and does not trigger duplicate death events.

10. FORBIDDEN ABILITIES

Forbidden Abilities are separate from normal Main Abilities, Sidekicks and Mythics.

They must be obtained through special Forbidden Structures and authorized administration. They must not appear in ordinary ability rolls.

Create separate textures, models, scrolls, lore, sounds, VFX, rarity rules and acquisition mechanics.

1. The Fear Of Gods

A forbidden ability that reduces the user's size and increases their damage.

• Level I: Size 0.9, damage multiplier ×1.0.
• Level II: Size 0.8, damage multiplier ×1.5.
• Level III: Size 0.7, damage multiplier ×2.0.

Implement the exact size values and damage multipliers from this specification.

Size changes must use genuinely supported server functionality. Do not claim that unsupported player-size manipulation works.

Make the damage multiplier calculation explicit and configurable.

2. Power of The Devil

A forbidden ability with permanent fire resistance and a powerful fireball attack.

Passive:

• Permanent Fire Resistance while the ability is equipped.

Active:

• Summon a fireball that damages enemies and destroys blocks in its configured area.

Levels:

• Level I: 3 hearts of damage, 3×3 block destruction.
• Level II: 4 hearts of damage, 4×4 block destruction.
• Level III: 5 hearts of damage, 5×5 block destruction.

Requirements:

• Protect the caster and trusted players.
• Block destruction must be configurable.
• Respect protected regions and spawn protection.
• Disable destruction in protected areas.
• Never use unrestricted explosions or allow this ability to grief protected builds.
• Include appropriate fireball VFX, sounds and textures.

11. ABILITY SYNERGIES

Create real combinations between abilities, with configurable timing windows.

Examples:

• Moonstep followed by Crescent Slash creates an empowered ranged slash.
• Flashstep followed by Crescent Nova creates a wider burst.
• Gravity Well followed by Eclipse Burst increases the pull-and-knockback sequence.
• Lunar Surge followed by Crescent Slash increases its damage within the active buff window.

Requirements:

• Implement at least five balanced combinations.
• Prevent the same synergy from triggering repeatedly from one activation.
• Display the synergy name and effect.
• Apply separate cooldown and damage checks as appropriate.
• Do not permit a normal ability synergy to bypass Mythic slot restrictions.
• Document every combination, its trigger order, timing window, effect and cooldown.

12. AWAKENING SYSTEM

Implement a unique, extremely powerful one-use Awakening ability.

Command

"/awakening"

The player must possess the special Awakening item or meet a documented server-side eligibility condition.

Admins may issue the item using:

"/crescentgiveawakening "

Core rules

• One successful activation per player every 36 hours.
• Store the cooldown persistently using player UUIDs and timestamps.
• Consume the Awakening item only after activation succeeds.
• The consumed item disappears and cannot be reused through normal inventory actions.
• Failed activation must not consume the item.
• The ability lasts exactly 1 hour.
• Display the remaining duration and cooldown clearly.
• Do not allow death, reconnecting, inventory swapping, item dropping or server restart to reset the cooldown.
• Do not duplicate the item through death drops, containers or inventory manipulation.
• If an awakened player disconnects, save the remaining duration and resume correctly.

Awakening ability

Create an extremely powerful combat state intended to give the user a major temporary advantage.

Include:

• Strong but configurable damage amplification.
• Defensive buffs.
• Enhanced movement.
• Unique VFX and sounds.
• A dramatic activation sequence.
• Clear activation and expiration messages.
• Compatibility with the ordinary ability system without unintentionally stacking unlimited damage multipliers.

ECLIPSE: END OF EXISTENCE

The signature Awakening ability must include the following cinematic activation sequence.

Activation:

• Sneak + right-click.
• Duration: 15 seconds.
• Cooldown: 36 hours.
• Range: 32 blocks.

Phase 1: Worldfall, 0–3 seconds

• Darken the scene using supported particle and sound effects.
• Form a gigantic crimson eclipse above the caster.
• Mark enemies within 32 blocks.
• Show clear warning effects so opponents can react.
• Keep all effects server-compatible.
• Do not claim to control every player's screen.

Relationship between Awakening and Eclipse

Clarify and implement how the 15-second signature ability relates to the 1-hour Awakening state.

The two systems must share the intended 36-hour eligibility cooldown and must not accidentally produce two independent uses.

The 15-second signature ability must be a documented part of the Awakening system, not an unintended second Awakening.

13. CUSTOM WEAPONS

Every custom weapon must have a unique texture, model, passive, active ability, cooldown, sound and VFX.

1. Crescent Reaper

Rarity: Mythic.

• Passive: Consecutive hits build Lunar Charge.
• Every fourth successful hit releases a lunar slash dealing bonus damage.
• Active: Reaper's Mark, marking a target for a powerful follow-up hit.
• At maximum charge, emit red crescent particles.
• Cooldown: 20 seconds.
• Recipe: Nether Star, Netherite Sword and Moon Shards, using a documented custom crafting layout.

2. Voidfang

Rarity: Legendary.

• Every fifth successful hit releases a short-range void slash.
• Active: Voidstep, dash forward and strike enemies along the path.
• Purple afterimages.
• Cooldown: 18 seconds.
• Cannot pass through walls or bypass protection regions.

3. Bloodbound

Rarity: Legendary.

• Successful hits build Blood Charges.
• Maximum charges: 5.
• Active: Bloodquake, consuming charges to damage and knock back nearby enemies.
• Weapon visual intensity increases with charge.
• Cooldown: 25 seconds.
• Damage scales with charges spent.

One original description specifies activation at 3 charges, while another describes consuming up to 5. Make the activation threshold configurable, defaulting to 3, with a maximum capacity of 5.

4. Lunar Piercer

Default rarity: Epic.

• Passive: Hunter's Trace, briefly marking targets.
• Active: Piercing Rush, a forward spear thrust.
• Marked targets leave a lunar trail.
• Cooldown: 22 seconds.
• Do not bypass anti-cheat or protection checks.

The original descriptions conflict over whether this is Epic or Mythic. Use Epic by default and make rarity configurable.

5. Eclipse Bow

Default rarity: Epic.

• Fully drawing the bow empowers an arrow.
• Active: Eclipse Shot creates a small impact burst.
• Red-and-silver trail.
• Cooldown: 15 seconds between empowered shots.
• No automatic homing or shots through solid blocks.

The original descriptions conflict over whether this is Epic or Mythic. Use Epic by default and make rarity configurable.

Weapon rolling chances

Weapon / Outcome| Rarity| Chance
Crescent Reaper| Mythic| 1%
Voidfang| Legendary| 4%
Bloodbound| Legendary| 5%
Lunar Piercer| Epic| 15%
Eclipse Bow| Epic| 25%
Other weapons or duplicate compensation| Common–Rare| 50%

All probabilities must add to exactly 100%.

Clearly distinguish the custom weapon roll table from ordinary ability rolls and Mythic selectors.

Weapon mechanics

• Passive effects activate on valid hits or fully charged shots.
• Active effects activate through right-click or a documented configurable action.
• Cooldowns prevent spam.
• Hit counters and charges reset when a weapon is dropped or swapped only if that is the intended documented rule.
• Prevent charge duplication by copying or transferring the item.
• Identify custom weapons through persistent item metadata rather than display names alone.
• Ensure hit counters belong to the authentic weapon identity and cannot be copied.

14. CUSTOM ITEMS AND RELICS

Every item needs a unique texture, lore, cooldown, effect, activation handling and VFX.

1. Blood Catalyst

• +30% damage for 15 seconds.
• Grants Strength I while active.
• Cooldown: 90 seconds.
• Cannot stack with another Blood Catalyst.

2. Void Elixir

• Speed II and Jump Boost II for 12 seconds.
• Brief Slow Falling on activation.
• Cooldown: 75 seconds.
• Effects expire automatically.

3. Lunar Core

• Grants 4 absorption hearts for 10 seconds.
• Reduces incoming damage by 15%.
• Cooldown: 120 seconds.
• Remove only the absorption attributable to this effect when the duration ends.

4. Rune of Fury

• Grants Haste II for 8 seconds.
• Reduces configured Crescent ability cooldowns by 20% while active.
• Cooldown: 100 seconds.
• Does not reset an ability already on cooldown.

5. Eclipse Essence

• Empowers the equipped main ability for 10 seconds.
• +40% main ability damage.
• +20% range where applicable.
• Cooldown: 180 seconds.
• Does not boost Mythic damage.
• Does not stack with another Eclipse Essence.
• Does not affect Sidekick cooldowns.

15. REROLLERS

Create separate rerollers:

• Ability Reroller.
• Sidekick Reroller.
• Weapon Reroller.

Each must:

• Have a distinct texture and item identity.
• Open a confirmation GUI or clearly confirm the target.
• Reroll only the appropriate equipped slot or inventory item.
• Use the configured probability table.
• Prevent rerolling locked or event-only Mythics unless authorized.
• Prevent duplication, rerolling without consuming the item and accidental rerolling from repeated clicks.
• Show the result and rarity.
• Support duplicate handling through a configurable policy.

16. ECLIPSE GOD SET

Create exactly one unique server-wide Eclipse God Set, rarity Mythic+ / Divine.

The set contains four custom pieces.

Eclipse Crown

• Highlights nearby enemies through a supported visual effect.
• Grants immunity to Blindness and Slowness.
• Every 5 seconds, blocks one incoming negative status effect.
• Do not falsely claim actual entity wallhacks or client-side highlighting unless the implementation genuinely supports it.

Heart of the Eclipse

• Reduces incoming damage by 30%.
• Stores energy when the wearer takes damage.
• At maximum energy, releases a defensive shockwave that pushes enemies away.
• Show the energy state through lore, particles or another supported display.

Voidstride Greaves

• Grants increased movement speed.
• Reduces knockback.
• Every 8 seconds, can trigger a short automatic dash when struck.
• Prevent repeated dash triggering from a single damage event.

Godfall Treads

• Grants Slow Falling while airborne.
• Reduces fall damage to zero.
• Landing after a large fall creates a small shockwave.
• Avoid triggering the shockwave repeatedly from one landing.

Full-set ability: ECLIPSE: GOD'S DOMINION

Activation: Sneak + right-click while wearing all four authentic armor pieces.

• Duration: 12 seconds.
• Cooldown: 5 minutes, configurable.
• Absolute Dominion: 70% damage reduction.
• Void Overload: attacks deal 2× damage.
• Gravity Collapse: pull enemies within 12 blocks toward the wearer.
• Eclipse Strikes: every 2 seconds, create a slash effect that damages nearby enemies.
• Unstoppable: immunity to knockback and most movement-disabling effects.
• Final Judgment: on expiration, create a large shockwave that damages and launches enemies within 16 blocks.

Cinematic timeline

• 0 seconds: activation sequence, armor glow and eclipse effect.
• 1–10 seconds: purple-black particle spiral, pull effects and repeated slashes.
• 12 seconds: final circular shockwave, custom sound and particle burst.

Do not claim to darken every player's screen or shake the camera unless the required client support exists. Use server-supported visual effects as a fallback.

Global uniqueness and security

• Only one authentic set may exist across the entire server.
• Provide an admin-controlled claim or single crafting unlock.
• The four pieces must not be obtainable through ordinary weapon rolls.
• The ultimate only activates with all four authentic pieces equipped.
• Individual pieces provide their own bonuses.
• Full-set powers are unavailable when a piece is missing.
• Prevent cloning through anvils, smithing, crafting, containers, death drops and inventory manipulation.
• Use persistent item identifiers and a server-side unique-ownership registry.
• Include a safe administrative recovery procedure if the set is lost.
• The set must remain extremely powerful but counterable.
• Respect spawn protection, protected regions, trust settings and configured PvP rules.

17. EVENT MANAGER

Implement a functional Event Manager.

Command:

"/eventmanger"

Optional corrected alias:

"/eventmanager"

The command opens a branded GUI where authorized administrators can start and manage events.

The GUI must support:

• Selecting an event.
• Starting and ending an event.
• Cancelling an event.
• Selecting event rewards.
• Viewing participants.
• Configuring event settings.
• Tracking winners.
• Preventing incompatible events from running simultaneously.

Events can reward event-only Mythic abilities, custom weapons, custom items and relics.

Implement all six event types below.

1. FFA

Free-for-all combat.

• Every participant fights individually.
• The last surviving player wins.
• Award the configured event reward to the winner.

2. Ritual

• Players travel to the ritual location.
• A player must successfully maintain the ritual claim for 3 minutes.
• Interruptions and competing claims must be handled correctly.
• The successful player receives the selected reward.

3. Bounty Hunt

• Every participating player receives a bounty.
• Event duration: 2 hours.
• The player who earns the most bounty money wins.
• Track bounty earnings through the event.
• Do not trust player-submitted totals.

4. Purge

• Start a shrinking world border.
• Players eliminated during the event enter spectator mode.
• The last surviving player wins.
• At the end, return participants to survival mode at Crescent Spawn.
• Restore the original world-border settings.
• Handle disconnects, deaths and server restarts safely.

5. Capture the Flag

Implement a functional team-based Capture the Flag event.

Include:

• Configurable teams.
• Flag locations.
• Scoring.
• Flag pickup and return mechanics.
• Victory conditions.
• Reward distribution.
• Protection against flag duplication and invalid interactions.

6. Juggernaut

• Select one player as the Juggernaut.
• Give the Juggernaut the selected ability or item.
• Give them a full unbreakable Netherite armor set with Curse of Vanishing.
• Other participants compete under configurable victory conditions.
• If the Juggernaut dies, only the event ability or item drops.
• Prevent event equipment from being duplicated or retained after the event.

Event Manager requirements

• Functional GUI with working controls.
• Event creation, starting, ending and cancellation.
• Reward selection.
• Participant tracking.
• Automatic cleanup and restoration after each event.
• Prevent overlapping incompatible events.
• Save event state safely.
• Log administrator actions.
• Configurable event durations, rewards and rules.
• Ensure event rewards cannot be duplicated.
• Restore players' original game modes, inventories and relevant states when appropriate.
• Handle server shutdown and restart during an active event.

18. CRESCENT SPAWN

Implement a configurable Crescent Spawn build and protection system.

Commands

• "/crescentspawn place": Set the Crescent Spawn location and establish the configured spawn area.
• "/crescentspawn reset": Reset the spawn configuration to its saved default.
• "/crescentspawn delete": Remove the configured Crescent Spawn and its associated display.

These commands must be permission-protected.

Spawn protection

• No PvP.
• No building or block breaking.
• No ability activation.
• No use of restricted custom items.
• Players may move normally.
• Protection must apply to all Crescent abilities, weapons, relics, Mythics, Forbidden Abilities and special effects.

Spawn display

Show every:

• Normal Main Ability.
• Sidekick.
• Mythic.
• Custom item.
• Custom weapon.

Do not display Forbidden Abilities.

Requirements:

• Use actual custom models and textures.
• Displays must not give players free items.
• Prevent interaction exploits.
• Save display locations and entities.
• Restore displays after server restarts.
• Include safe administrative recovery and removal procedures.

19. COOLDOWN SYSTEM

Implement a shared cooldown framework for:

• Main abilities.
• Sidekicks.
• Mythics.
• Weapon actives.
• Relics.
• Awakening.
• Eclipse God Set powers.
• Forbidden Abilities.

"/crescentskip" must:

• Be admin-only.
• Skip a specified player's specified cooldown, or the admin's cooldown when using the documented shorthand.
• Validate target, ability and cooldown category.
• Never allow normal players to bypass cooldowns.
• Log administrative use.
• Never grant additional items or reset unrelated player data.

Persist long cooldowns such as the 36-hour Awakening cooldown across restarts.

Use a consistent cooldown framework so effects, cooldowns and state cannot accidentally duplicate after reloads.

20. ANTI-DUPLICATION AND EXPLOIT PROTECTION

Implement layered protection, not a single suspicious-click check.

• Identify unique custom items with persistent metadata and UUIDs where appropriate.
• Prevent duplication through GUIs, inventory clicks, dragging, number keys, double-click collection, crafting, anvils, smithing, death drops, disconnects and container transfers.
• Validate server-side state before awarding, consuming, equipping or rerolling items.
• Use atomic claim and consumption logic for one-time items.
• Prevent duplicate shard rewards from repeated death handling.
• Protect the unique Eclipse God Set through a global ownership registry.
• Protect event rewards and Forbidden Ability items.
• Log suspicious inventory changes and repeated invalid activations.
• Do not automatically ban players based on one false-positive event.
• Provide configurable warnings, logging and administrative review.
• Document which exploit vectors are covered and which require additional server-side protections.

21. TRUST, DAMAGE AND REGION SAFETY

Implement a configurable trust system or integrate with the existing Crescent trust mechanism.

• Trusted players must be excluded from damaging area effects where configured.
• Abilities must respect WorldGuard or equivalent protection regions if installed.
• No ability may bypass spawn protection.
• Prevent unwanted damage to the caster.
• Prevent friendly-fire violations.
• Damage must pass through the server's supported damage system and respect armor, protection and configured rules.
• Movement abilities must not teleport players through protected boundaries or into unsafe destinations.
• Power of The Devil must not destroy protected blocks.
• Event mechanics must respect configured region and PvP rules.
• Clearly document optional integrations and their dependencies.

22. VFX, MODELS AND RESOURCE PACK

Create a complete custom resource pack compatible with Minecraft Java 1.21.11.

Category colors

• Main abilities: individually distinct colors.
• Sidekicks: teal/cyan theme.
• Mythics: crimson-red theme.
• Forbidden Abilities: unique dark and dangerous theme.
• Weapons: individual weapon identities and palettes.
• Eclipse God Set: dark purple, black, crimson and silver.
• Awakening: dramatic eclipse-themed design.
• Shards, relics and rerollers: distinct identifiable icons.

Scroll textures

Each Main Ability, Sidekick, Mythic and Forbidden Ability gets its own scroll texture.

Requirements:

• The scroll artwork must depict what the ability does through its symbol.
• Keep the ability name written on the parchment as requested in the earlier text-enabled design.
• Do not put unrelated labels, watermarks or category titles onto the scroll itself.
• Preserve distinct symbols rather than recoloring identical artwork.
• Include the crescent moon motif where appropriate.

3D models

Create unique 3D item models for:

• Every custom weapon.
• All four Eclipse God Set armor pieces.
• Awakening item.
• Shards.
• Relics.
• Rerollers.
• Ability scrolls where supported.
• Forbidden Ability items.
• Event-related custom items.

For worn armor, distinguish between 3D inventory item models and actual 3D armor geometry.

If true custom worn armor geometry requires a client-side mod or specialized renderer, document the limitation. Do not claim ordinary resource-pack item models accomplish it.

VFX

Implement distinct visual effects for every:

• Main Ability.
• Sidekick.
• Mythic.
• Forbidden Ability.
• Weapon active.
• Relic.
• Reroller.
• Shard event.
• Awakening.
• Eclipse God Set ability.
• Event ability or event reward.

Use supported vanilla particles, sounds and animations where possible.

If custom particles require additional server-side or client-side support, include the required components or clearly document the limitation. Sprite sheets and JSON definitions alone do not automatically create spawnable custom particle types.

Include:

• Ability-specific trails.
• Charge-up effects.
• Impact bursts.
• Teleport effects.
• Red Mythic explosions.
• Teal Sidekick trails.
• Eclipse formations.
• Armor energy effects.
• Unique sounds or documented sound mappings.
• Animated textures where genuinely supported.
• Forbidden Ability effects.
• Event-specific visual effects.

23. PERFORMANCE AND PERSISTENCE

• Avoid constantly looping through every player and entity.
• Avoid unbounded particle loops and excessive asynchronous work.
• Use scheduled tasks only when needed and cancel them when the effect ends.
• Store persistent state by UUID.
• Save important state before shutdown.
• Avoid blocking the main thread with file operations.
• Clean expired temporary variables.
• Handle player disconnects, deaths, world changes and server restarts.
• Prevent cooldown and effect duplication after reload.
• Keep every feature configurable where sensible.
• Avoid unnecessary entity searches and repeated expensive region checks.
• Ensure event cleanup cannot leave players in spectator mode or with temporary equipment.
• Ensure Awakening, event and God Set state survives restarts correctly.

24. REQUIRED TESTING

Do not merely generate files and announce success.

Static checks

• Parse every JSON model and metadata file.
• Verify every referenced texture exists.
• Verify every custom model identifier matches its item definition.
• Check all Skript files for duplicated commands, functions, variables and incompatible syntax.
• Verify every required command is implemented.
• Verify every GUI click target has a working action.
• Verify all custom item IDs and persistent identifiers are consistent.
• Verify resource-pack paths and metadata for Minecraft 1.21.11.
• Verify all weapon probabilities add to exactly 100%.
• Verify all permissions are defined and applied.
• Verify all persistent variables and cooldown keys are consistent.
• Verify all event cleanup and restoration paths.

Server tests

On a disposable Paper 1.21.11 test server with the documented Skript and addons:

• Load every script and fix all syntax errors.
• Test every command with authorized and unauthorized users.
• Test every GUI page and button.
• Test each Main Ability at levels I, II and III.
• Test every Sidekick.
• Test every Mythic.
• Test every Forbidden Ability.
• Test shard progression, moon phases and negative-shard restrictions.
• Test all cooldowns and "/crescentskip".
• Test Awakening consumption, reconnects, server restarts and the 36-hour cooldown.
• Test the relationship between the one-hour Awakening and 15-second Eclipse signature ability.
• Test all weapon passives and active abilities.
• Test reroller probabilities and duplicate handling.
• Test all four armor pieces and full-set activation.
• Test uniqueness enforcement for the God Set.
• Test all six events and their victory conditions.
• Test event cleanup, disconnections and restarts.
• Test Crescent Spawn commands, protection and displays.
• Test protected regions and trusted players.
• Test GUI and inventory duplication attempts.
• Test resource-pack loading and every custom model in-game.
• Check console logs and fix all errors found.

Completion report

Provide a checklist with three distinct states:

• Implemented.
• Tested and passed.
• Not implemented or not testable in the current environment.

Never mark a feature as tested merely because its files exist. Do not claim a successful server test unless it actually ran.

25. FINAL DELIVERABLES

Return:

1. Full Crescent project ZIP.
2. All Skript source files in their normal directory structure.
3. Standalone resource-pack ZIP.
4. All custom texture and model source assets.
5. Installation instructions for Paper 1.21.11.
6. Required Skript and addon versions.
7. Commands and permission documentation.
8. Admin guide for the selector, Awakening, Forbidden Abilities, Event Manager, Crescent Spawn and God Set.
9. A backup of the previous version before modifications.
10. A testing report with honest results.
11. Configuration files with explanations for every important setting.
12. A list of supported integrations and their exact installation requirements.

26. FINAL IMPLEMENTATION RULES

Before implementation:

• Read the entire specification.
• Create a checklist of every feature, command, item, ability and system.
• Identify conflicting requirements.
• Preserve original requirements unless an explicit resolution is provided in this document.
• Document any unavoidable technical limitation.
• Do not silently remove features to simplify development.

During implementation:

• Build the modular Skript system.
• Build the resource pack and all custom assets.
• Connect every item, model, ability and GUI to the correct system.
• Implement persistent data and anti-duplication protection.
• Validate all commands and permissions.
• Test each system before moving to the next.
• Keep source code readable and organized.

When resolving conflicts:

• Bloodbound: Maximum 5 charges; default activation threshold 3, configurable.
• Lunar Piercer: Epic by default, rarity configurable.
• Eclipse Bow: Epic by default, rarity configurable.
• Power of The Devil: Use the level table of 3×3, 4×4 and 5×5 block destruction.
• Selector: Use all seven functional sections.
• Awakening: One shared 36-hour eligibility cooldown for the one-hour state and its 15-second signature ability.
• Shards: Default starting balance 3, configurable to 5; minimum -3 and maximum 5 by default.

Do not invent missing mechanics. If a detail is genuinely unspecified, make it configurable and document the chosen default.

FINAL PRIORITY

A smaller feature that genuinely works is better than a huge project full of fake buttons, broken commands and empty mechanics.

Implement, validate, fix, retest, then deliver.

The finished system must remain a modular Skript project for Paper 1.21.11, not a Java plugin or Minecraft mod.

Everything must be credited to Made By CryVux.
Kodari AI
KodariOct 30 at 11:03 pm 1
CrescentSMP
Build a complete modular Skript ability system for Paper 1.21.11 with 10 main abilities, 5 sidekicks, 5 mythics, 2 forbidden abilities, custom weapons, relics, rerollers, Awakening, Eclipse God Set, Event Manager, and Crescent Spawn. Includes persistent shard economy with moon phases, cooldown framework, anti-duplication, trust/region safety, custom resource pack with models and textures, and full admin commands. All branded "Made By CryVux".
  1. Build a no-addon Skript foundation for shard persistence, trust, commands, cooldowns, and the implemented combat abilities.

  2. Document installation, permissions, implemented scope, and what still requires Studio or a test server.

  3. Leave unsupported pack assets and unimplemented systems clearly identified rather than shipping broken placeholders.

Created the Skript foundation and setup guide. It implements persistent shard balances, basic trust handling, several main abilities, and a limited set of commands.

This is not the complete Crescent system requested: most abilities and commands, GUIs, events, protections, and anti-duplication features are not implemented. No resource pack, textures, models, or custom font glyphs are included; asset generation is disabled for this project.

Testing status: Not tested on a Paper 1.21.11 server. Check the Skript reload logs and test on a disposable server before use. The README lists installation steps, included features, permissions, and limitations.

Kodari can make mistakes. Review important code before using.
Files
00_Crescent_Core.sk
01_Crescent_Commands.sk
02_Crescent_Abilities.sk
README.md
Code
4 340
02_Crescent_Abilities.sk
options:
    prefix: &8[&bCrescent&8] &f

function crescentAbilityLevel(p: player) :: integer:
    set {_balance} to crescentBalance({_p})
    if {_balance} >= 5:
        return 3
    if {_balance} >= 3:
        return 2
    return 1

function crescentActivateMain(p: player, source: text):
    if {_source} is "command":
        if {crescent.mode::%uuid of {_p}%} is "action":
            send "{@prefix}&cYour activation mode is sneak + right-click." to {_p}
            stop
    else:
        if {crescent.mode::%uuid of {_p}%} is not "action":
            stop
    if {_p} does not have permission "crescent.abilities.use":
        send "{@prefix}&cYou do not have permission to use Crescent abilities." to {_p}
        stop
    if crescentBalance({_p}) < 0:
        send "{@prefix}&cYou need at least 0 shards to use an ability." to {_p}
        stop
    set {_ability} to {crescent.main::%uuid of {_p}%}
    if {_ability} is not set:
        send "{@prefix}&cYou do not have a main ability equipped." to {_p}
        stop
    if {crescent.cooldown::%uuid of {_p}%::%{_ability}%} is after now:
        send "{@prefix}&cThat ability is still on cooldown." to {_p}
        stop
    set {_level} to crescentAbilityLevel({_p})
    set {crescent.cooldown::%uuid of {_p}%::%{_ability}%} to now + 10 seconds

    if {_ability} is "blood_moon":
        set {_healing} to {_level}
        set {_hit} to false
        loop all living entities in radius 4 around {_p}:
            if loop-entity is not {_p}:
                if loop-entity is a player:
                    if crescentTrusted({_p}, loop-entity) is false:
                        damage loop-entity by {_healing}
                        set {_hit} to true
                else:
                    damage loop-entity by {_healing}
                    set {_hit} to true
        if {_hit} is true:
            heal {_p} by {_healing}
            send "{@prefix}&cBlood Moon restored %{_healing}% health points." to {_p}
        else:
            delete {crescent.cooldown::%uuid of {_p}%::%{_ability}%}
            send "{@prefix}&cNo valid target was in range; no cooldown was used." to {_p}
        stop

    if {_ability} is "lunar_guard":
        if {_level} is 1:
            set {crescent.guard.reduction::%uuid of {_p}%} to 0.15
        else if {_level} is 2:
            set {crescent.guard.reduction::%uuid of {_p}%} to 0.25
        else:
            set {crescent.guard.reduction::%uuid of {_p}%} to 0.35
        set {_duration} to {_level} + 2
        set {crescent.guard.until::%uuid of {_p}%} to now + {_duration} seconds
        send "{@prefix}&bLunar Guard active for %{_duration}% seconds." to {_p}
        stop

    if {_ability} is "eclipse_burst":
        set {_radius} to {_level} + 2
        crescentDamageNearby({_p}, {_radius}, 2)
        send "{@prefix}&bEclipse Burst struck nearby untrusted targets." to {_p}
        stop

    if {_ability} is "gravity_well":
        set {_radius} to {_level} + 2
        loop all living entities in radius {_radius} around {_p}:
            if loop-entity is not {_p}:
                if loop-entity is a player:
                    if crescentTrusted({_p}, loop-entity) is false:
                        apply potion of slowness 2 to loop-entity for 2 seconds
                else:
                    apply potion of slowness 2 to loop-entity for 2 seconds
        send "{@prefix}&5Gravity Well slowed nearby untrusted targets." to {_p}
        stop

    if {_ability} is "lunar_surge":
        if {_level} is 1:
            set {crescent.surge.multiplier::%uuid of {_p}%} to 1.05
        else if {_level} is 2:
            set {crescent.surge.multiplier::%uuid of {_p}%} to 1.08
        else:
            set {crescent.surge.multiplier::%uuid of {_p}%} to 1.1
        set {_duration} to {_level} + 3
        set {crescent.surge.until::%uuid of {_p}%} to now + {_duration} seconds
        send "{@prefix}&bLunar Surge active for %{_duration}% seconds." to {_p}
        stop

    if {_ability} is "shadow_veil":
        set {_duration} to {_level} + 1
        apply potion of invisibility 1 to {_p} for {_duration} seconds
        send "{@prefix}&8Shadow Veil active for %{_duration}% seconds." to {_p}
        stop

    if {_ability} is "crescent_nova":
        set {_radius} to {_level} + 2
        set {_damage} to ({_level} * 2) + 2
        crescentDamageNearby({_p}, {_radius}, {_damage})
        send "{@prefix}&bCrescent Nova released." to {_p}
        stop

    delete {crescent.cooldown::%uuid of {_p}%::%{_ability}%}
    send "{@prefix}&cThat ability is not implemented." to {_p}

on right click:
    if player is sneaking:
        if {crescent.mode::%uuid of player%} is "action":
            if {crescent.main::%uuid of player%} is set:
                cancel event
                crescentActivateMain(player, "action")

on damage:
    if victim is a player:
        if {crescent.guard.until::%uuid of victim%} is after now:
            set {_reduction} to {crescent.guard.reduction::%uuid of victim%}
            set {_damageMultiplier} to 1 - {_reduction}
            set damage to damage * {_damageMultiplier}
        else:
            delete {crescent.guard.until::%uuid of victim%}
            delete {crescent.guard.reduction::%uuid of victim%}
    if attacker is a player:
        if {crescent.surge.until::%uuid of attacker%} is after now:
            set {_multiplier} to {crescent.surge.multiplier::%uuid of attacker%}
            set damage to damage * {_multiplier}
        else:
            delete {crescent.surge.until::%uuid of attacker%}
            delete {crescent.surge.multiplier::%uuid of attacker%}