Create a Complete Minecraft DeckSMP Card Abilities Plugin
Build a complete, production-ready Minecraft Java plugin for a Paper server called DeckSMP. This plugin must be created from scratch. Do not require an existing JAR file or an existing source-code project.
- Main Objective
Create a custom card-based ability plugin for a Minecraft SMP server. Each card must have its own identity, original abilities, and additional new abilities.
Most important rule: Keep every card name exactly as listed below. Preserve all specified original abilities and add more abilities to those same cards. Never rename, remove, replace, or duplicate a card.
- Card Names and Ability System
Create a card system containing these cards:
- Blood Rush
- Frost
- Lightning Strike
- Ocean Critical
- Withering Curse
- Overdrive
- Glide
- Hop
- Spider
- Resurrection
- Lucky Dodge
- Health
- Alchemist
- Dismantle
- Dragon Egg
- Shadowstep
- Phase
- Spotlight
- Conductor
- Villager
- Vindicator
- Feather
- Shield
- Netherite
Keep these exact display names. Do not invent replacement names for these cards.
For each card, implement a unique set of abilities. Use the original abilities described in the next section as the starting point, and design additional abilities that match each card's theme.
- Preserve Original Abilities and Add More
Create the following baseline abilities. These establish the original mechanics that must remain available alongside any new abilities.
- Blood Rush: A blood-themed combat ability that boosts offensive power under defined conditions.
- Frost: Ice-based attacks and slowing effects.
- Lightning Strike: Lightning-themed attacks and electrical damage.
- Ocean Critical: Water-themed critical hits and combat bonuses.
- Withering Curse: Wither-based damage and debuffs.
- Overdrive: A temporary combat boost.
- Glide: Controlled gliding and aerial movement.
- Hop: Enhanced jumping.
- Spider: Spider-like climbing or web movement.
- Resurrection: A survival ability that activates under a defined lethal-damage condition.
- Lucky Dodge: A chance to evade incoming damage.
- Health: A health-related passive or active ability.
- Alchemist: Potion-based effects.
- Dismantle: An ability that disrupts or weakens an opponent under defined conditions.
- Dragon Egg: A dragon-themed special ability.
- Shadowstep: Short-range teleportation or evasive movement.
- Phase: Temporary phasing or defensive evasion, implemented safely within server mechanics.
- Spotlight: A targeted marking or reveal ability.
- Conductor: An ability that interacts with lightning or chains effects between targets.
- Villager: A trading, utility, or support ability.
- Vindicator: An axe-focused combat ability.
- Feather: A fall-damage or movement-related ability.
- Shield: Defensive protection and damage mitigation.
- Netherite: A durable, heavy-combat or defensive ability.
These descriptions define the baseline gameplay themes. Implement them as real, functional mechanics rather than placeholder messages.
Additional ability requirements
For every card:
- Keep its baseline abilities.
- Add at least two genuinely new abilities, where technically appropriate.
- Make the new abilities different from the original abilities.
- Support both passive and active abilities where suitable.
- Give each active ability a defined activation method and cooldown.
- Include appropriate particles, sounds, action-bar messages, and visual feedback.
- Balance the abilities for SMP PvP gameplay.
- Prevent infinite healing, damage loops, permanent invulnerability, and ability-spamming exploits.
Do not replace an old ability just to make room for a new one.
- Ability Activation
Implement a reliable ability activation system.
- Passive abilities activate automatically when their conditions are met.
- Active abilities use clearly documented player controls or commands.
- Prevent conflicts between different abilities.
- Avoid accidental activation multiple times from a single event.
- Display cooldowns and useful activation feedback.
- Support multiple cards being equipped only if the selected configuration permits it.
- Make sure equipped cards activate their abilities correctly.
Choose activation controls that do not conflict with normal Minecraft gameplay. Provide configurable controls or commands when appropriate.
- Card GUI
Create a polished inventory-based GUI.
- "/cards" opens the card collection.
- "/cardinfo" opens the card information showcase.
- "/card <name>" gives a card to an authorized player.
- "/withdraw <slot>" withdraws an equipped card according to the implemented slot system.
Every card must display its exact name, rarity if applicable, ability descriptions, and relevant cooldown information.
Use unique item metadata or persistent data identifiers so cards are recognized correctly even when players rename ordinary Minecraft items.
Prevent players from exploiting the GUI to duplicate cards, bypass permissions, or manipulate protected inventory items.
- Additional Commands
Implement these commands:
- "/challenges" — Open the challenges GUI.
- "/resetchallenges" — Reset challenges for authorized administrators.
- "/toggle" — Toggle supported abilities or plugin features.
- "/trust <add|remove|list> [player]" — Manage trusted players.
Include tab completion, argument validation, clear error messages, and appropriate permissions.
- Configuration and Administration
Create a configurable system that allows server administrators to adjust:
- Card abilities and their enabled states.
- Ability cooldowns.
- Ability durations and strengths.
- Damage and status-effect values.
- Card rarity and availability.
- Maximum equipped cards.
- Ability activation methods.
- Particle and sound effects.
- Player permissions and administrative access.
Store configuration and player data safely. Reloading configuration must not duplicate listeners or scheduled tasks.
- Technical Requirements
- Platform: Minecraft Java Edition.
- Server software: Paper.
- Use Java and Maven or Gradle.
- Target Minecraft 1.21.11, and verify API compatibility before delivery.
- Use an appropriate Java version supported by the target Paper release.
- Use the correct Paper API dependencies.
- Include "plugin.yml" or the appropriate plugin metadata.
- Use a clean, maintainable architecture with separate card definitions, ability implementations, cooldown management, GUI handling, and configuration.
- Handle player death, disconnection, world changes, and card unequipping correctly.
- Clean up temporary effects, entities, scheduled tasks, and player data.
- Avoid unnecessary dependencies and performance-heavy repeating tasks.
- Testing Requirements
Test the plugin for:
- Successful compilation.
- Successful startup on the target Paper version.
- Correct registration of every card and command.
- Correct activation of every baseline and new ability.
- Working cooldowns and passive abilities.
- GUI interaction and inventory security.
- Multiplayer PvP interactions.
- Player death, reconnecting, and card switching.
- Permissions and configuration changes.
- No duplication exploits, severe console errors, or memory leaks.
Do not claim that a test passed unless it was actually performed.
- Final Deliverables
Deliver a complete project that includes:
- Full Java source code.
- Build files and dependency configuration.
- Plugin metadata and default configuration.
- All 24 cards with their baseline and additional abilities.
- GUI, commands, permissions, and cooldown systems.
- Installation instructions.
- A compiled, working "DeckSMP.jar".
- Documentation listing every card, all its abilities, activation conditions, and cooldowns.
Do not return only a design, tutorial, or code snippets. Build the complete plugin project and provide the compiled JAR.
Final rule: Every card name must remain exactly as specified. Every baseline ability must be implemented and retained, with at least two additional abilities per card where appropriate. Create everything from scratch without requiring me to upload an existing plugin file.